Running Firefox 51 on my mac and would like to use icedtea web applet plugin. The instructions provided in https://icedtea.classpath.org/wiki/IcedTea-Web#Plugin is not clear for mac.
Is there anyway to use icedteaweb applet plugin for firefox running on Mac?
The support of plugins to run Applets has been removed from most browser.
It is no longer recommended to embed Applets into webpages.
See also: https://support.google.com/accounts/thread/11809182?hl=en
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
I have an extension which talks to a native application. This application only works on macOS or Windows. But when I add the extension to my browser, it is also synchronized automatically to platforms where it does not make sense such as Linux or Chrome OS.
I'd figured there would be an option in the manifest.json to limit the app to specific platforms but I can't find anything like that. Am I correct? Or is there a solution?
Extensions will be installed based on chrome login. So it will be installed on all devices with chrome login.
You can programmatically enable/disable your scripts after checking for supported platform OS.
Use this API in background script to collect platform details - API Link.
Related question: Detect operating system from Google Chrome Extension
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 used Microsoft XP as operation system for web design and development for 1 year. But now I am switching to Ubuntu (linux).
For Windows OS we have Microsoft’s SuperPreview for testing compatibility in different versions of IE.
Please specify the list of such utilities or tools which provide such support in Linux, specifically for Ubuntu.
If you want to test IE compatibility on Linux, you have a few options:
Windows on a Virtual Machine (eg: VirtualBox) with multiple IEs installed
IEs4Linux
Wine + Winetricks
In order of personal preference (VM is my favorite option).
Other than that, you can use install Firefox, Opera and Chrome on Ubuntu. There's no native version of Safari, but you should be fine since it uses the same rendering engine as Chrome (WebKit).
I am running windows 7 which won't even allow me to use the latest IE version for testing.
I currently use google crome and firefox. Is there a program or easy way to test a site with multiple browsers, and not just
the way they might look but everything like javascript and ajax just as if I were using that particular browser?
http://www.xenocode.com/Browsers/ has some great online browser virtualizations.
They take a bit to load but are perfect for testing. Javascript and such will work like normal and you can try out all the versions of IE from the same computer without installing anything.
I should note that these launch fully functional browser windows- It is not an in browser preview type thing.
They used to have multiple IE versions, Firefox, Opera and safari available to download as portable software but I can't find them anymore :(
Install a virtual machine manager - OpenBox from Sun is free and works OK - and install a copy of Windows / Linux / whatever in each of a bunch of virtual machines. Then in each Windows either keep the installed browser (ie IE 6, hahah, in XP) or upgrade it to IE 7 or IE 8. Also install whatever versions of FF and Opera and so on.
It's not perfect, but I get by using IETester for different versions of IE. The author claims it works on Windows 7.
You can check out the TestSwarm, by John Resig. His blog article on here is at:
http://ejohn.org/blog/javascript-testing-does-not-scale/