I am developing a chrome extension with Manifest version 3 and due to bug https://crbug.com/1271154, the service worker broken once you reload or allow it work in incognito mode. Is there any quick fix that I may run my extension properly in incognito mode?
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 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.
How to run active x control in chrome browser for hamster device.
activa x control not support in chrome browser.
You don't. You might try an extension that runs IE engine in chrome, but activeX is actually a Microsoft product
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.