I have developed a chrome extension that i have tested successfully in two different computers (Linux and Windows systems) with Chrome version 76.0. The first line of this extension is a console.log("test") which is obviously showing in the developer console every time i start chrome. The problem I face now is that when testing the extension in a MAC computer (which should not make a difference?) with Chrome 76.0, it is installed successfully but it never starts. Not a single log is shown (yes, i checked that logs are being shown) and it is not working at all. No error are shown in the console and no errors in the extension settings tab. I have no idea what is going on here.
Related
PhpStorm 2021.2.2 on Ubuntu 20.04. I set up a Run Configuration as follow:
But when I launch this Run Configuration I get:
I don't understand why it look for Google Chrome if I selected Firefox as a browser.
Sadly that is correct / no error here.
JavaScript debug is done with Chrome-based browsers only (has been like that for quite some time now).
https://www.jetbrains.com/help/phpstorm/2021.2/run-debug-configuration-javascript-debug.html
https://www.jetbrains.com/help/phpstorm/2021.2/debugging-javascript-in-chrome.html
Debugging of JavaScript code is only supported in Google Chrome and in other Chromium-based browsers.
To debug JavaScript using Firefox you need to use Firefox Remote type of Run/Debug Configuration (need to manually create and use it) and enable Remote Debugging in Firefox in advance. https://www.jetbrains.com/help/phpstorm/2021.1/debugging-javascript-in-firefox.html has all the info.
A ticket to watch after: https://youtrack.jetbrains.com/issue/WEB-14987
NOTE: the aforementioned Firefox Remote type of Run/Debug Configuration is no longer present in current 2021.2 version. The last version that has it is 2021.1.
In addition to the above, from https://intellij-support.jetbrains.com/hc/en-us/community/posts/360010846880/comments/360003174860
Unfortunately, there's nothing we can offer for debugging in Firefox now :(
We used to support Firefox Remote Debugging (but without source maps) through the Firefox Remote run configuration, but our solution doesn't work in the latest Firefox versions due to changes in the protocol, and there doesn't seem to be an easy way to fix it. We've made some progress recently, but there are still some blocking issues.
Related tickets:
https://youtrack.jetbrains.com/issue/WEB-45986
https://youtrack.jetbrains.com/issue/WEB-48076
https://youtrack.jetbrains.com/issue/WEB-2337
Can no longer get any feature of Google Maps to work on my desktop in Chrome and Firefox (works in Edge). Happened once and returned to normal when I re-installed Chrome. What am I doing wrong?
I have pgAdmin v4 installed, my default browser is Firefox, but I would like to open pgAdmin as a standalone app on Chrome. I fixed that problem following the procedure described in various Stackoverflow answers such as Launch pgAdmin 4 as a standalone app using chrome browser commands and pgAdmin 4 v3.1 How can I use another browser? (Win 7), i.e. configuring the "Browser command" option of pgAdmin to use Chrome.
That worked till sometime ago, but with the latest versions (at least 4.24 an 4.25) there is a problem: when I launch pgAdmin it still opens the default browser and not Chrome, as I configured. However, if I right click on the icon of the system tray and select "New pgAdmin 4 window..." it correctly opens Chrome.
I thought it was just me, but I found that there is at least another user with the same problem.
As pointed out by a developer of EnterpriseDB (the company behind pgAdmin) in this answer, that is a bug in the QT library that happens on Windows platform; it has already been reported and developers are working on that.
I have been finding the way to get the urls of opened tabs of the browsers of Firefox and Chrome using Accessibiltiy.
I found that Firefox can get the urls using at-spi, but Chrome can get the url of focused tab a few months ago.
I have gotten a new result recently during the test. It is that I cannot access the child of Chrome using Accessibility, so I don't even know the url of focused tab.
"atspi_accessible_get_child_count" returns 0.
But as I said earlier, it worked on Chrome 31 version.
According to Assistive technology support, there are not tools to test accessibility in Linux.
Chrome does not support Accessibility anymore?
There is the answer in Chrome Accessibility.
That says accessibility of Chromium on desktop Linux is not really supported currently.
You need to start Chrome like this:
ACCESSIBILITY_ENABLED=1 chrome --force-renderer-accessibility
Both of these are necessary. For electron apps, ACCESSIBILITY_ENABLED=1 seems to be enough, at least that was the case with VSCodium and Signal Desktop.
On Windows, this is not necessary because a11y enables itself once a known screen reader is detected (afaik), but Orca under Linux is apparently not known.
I have Chrome for Mac on my mini-mac running OS 1 10.6.8 and starting to learn how to write Chrome extensions.
Followed the sample tutorial for the browser-action pop-up.
Does NOT pop-up on my mini-mac, but the same code works just fine on my Macbook Pro running OS X 10.9.2
The only obvious difference is that my mini-mac cannot be upgraded to Mavericks, etc. nor to Java 7.x, however, there are other published extensions that I am able to load that work just fine on both Macs and both OS X.
I have not found any answers surfing -- any help is appreciated.
Chrome extensions do not depend on OS X Mavericks, and they do not require Java 7, and as you have mentioned, others are working well on your Mac Mini. (They run on my Mac Mini too.)
You can check to see if you have developer mode enabled by going to chrome://extensions and making sure the "Developer Mode" checkbox near the top of the page is enabled.
Another potential problem is if you are running a very old version of chrome, say older than about 6 months.
See if other tutorial apps work. It might be good to start with this one:
https://developer.chrome.com/apps/first_app