I seemed to have lost the ability to set a breakpoint in a chrome app. I tested with a chrome-app-sample and my old app in both canary and stable chrome with both chrome versions open simultaneously on a mac as well as only one open at a time.
Whether I try to set a breakpoint programmatically with debugger; or set the breakpoint in the sources tab of the Developer Tools app, I can not seem to stop on code that I am 100% confident is executed.
Version 41.0.2258.2 canary (64-bit)
Related
I have written some HTML/JS page and if I open the page on different machines (laptop vs. PC) with the very same version of Chrome, one browser has the navigator.wakeLock property but the other one has not.
Debugger shows wakeLock property
Debugger shows no wakeLock
Chrome current version
I'm puzzled.
As far as I know Chrome supports wakeLock. And does obviously on the laptop.
But why not on my PC?
Both run Windows 10.
Long story short I'm looking to create a Chrome extension that will run within a site that only wants to run Internet Explorer (Oracle EBS). So far my only option has been to run IE Tab, which works fine when visiting the site. My new extension right now just runs alert("foo"); once a page loads and that works fine as well.
The new extension does not run in IE Tab though. Using IE Tab changes the URL to:
chrome-extension://IE_Tab's_extension_ID/nhc.htm#url=site_url
and nothing happens. Is there a way to run the extension within the IE tab extension? If anyone has an alternative idea as well I'm open to suggestions.
FYI, I ended up not doing much with IE tab or chrome. Placing a script into it's nhc.htm worked but ended up being slower and clunkier than my solution.
Instead I resorted to just using the old version of Chromium 44 (make sure it's Chromium, not chrome) and enabling the NPAPI in the chrome://flags/#enable-npapi. It's outdated tech, but really it's just there to occasionally run specific Java apps along with the new chrome extension, not replace their current browser.
I'm trying to test my extension in Firefox 44+ as I got a compatibility warning about it using files that have been moved in newer versions. I have Firefox 43 which works, and I have Firefox Developer Edition, in which I can't seem to set it to enable.
I temporarily enable Developer Debugging Preferences , so I can immediately see my changes (addon installed in regular Fx and Dev edition). I have my addon directory set in profile .dev-edition-default/extensions.ini file same in both of them, but it doesn't show up in Firefox Developer Edition. - not when I put it under [ExtensionDirs], or [MultiprocessIncompatibleExtensions]
So how do I test my addon in Firefox Developer edition?
Load it as a temporary addon - https://blog.mozilla.org/addons/2015/12/23/loading-temporary-add-ons/
I used to be able to debug javascript from webstorm with no problem at all.
Thanks to the jetbrains chrome extension, it simply opened a new tab in chrome and launched my site in there with no problem whatsoever.
But recently I had to reboot my computer (with a beloved windows update) and now this is not working anymore.
When I start the debugging from webstorm chromes opens a new tab and I see the following in the address bar and then nothing...
data:text/html;base64,PCFET0NUWVBFIGh0bWw+PHRpdGxlPkxvYWRpbmcgaHR0cDovL3ZtLnNob3RndW4ubG9jYWwvPC90aXRsZT4=
My site is not opened and the page remains blank in chrome.
Most probably this is a result of Chrome update: some Chrome API changes introduced in v.37 break js debugger. WEB-12418 is fixed in WebStorm 9 EAP
I am using Firefox 28.0 on Mac OS 10.6.8. Sometimes during web development, probably after my application crashes, Firefox suddenly disables Javascript in one particular tab. So my application would be all weird and not work until I restart Firefox. The script panel would say that the page has no scripts, and if I open another page with Javascript in the same tab, it would not work either.
Is it some kind of safety feature? Is it documented anywhere? Note that I also have Firebug installed, and I managed to crash Firefox by profiling my app in Firebug on more than one occasion.
I checked about.config; javascript.enabled is set to true.