Puppeteer-firefox headless mode does not support webgl. What can I do in linux to make it work?
I do not know if the selenium firefox has the same problem, I think this is firefox side error.
Thanks
Yes, it's a not yet solved issue in Firefox. You can find details about its implementation status at https://bugzilla.mozilla.org/show_bug.cgi?id=1375585.
And please don't use the puppeteer-firefox package anymore. It has been deprecated. Experimental support for Firefox is included in the official puppeteer package.
Related
Is possible to replace chromium with firefox inside an electron app?
I've done some researches and I was not able to found anything that use firefox to run cross platform desktop applications. If this is possible can anyone share the relative information please?
The only project I've found this old and not mantained from mozilla.
If this is not possible, is there any way to create a custom build of mozilla that integrate node.js? I want to experimet the electron flow that will open a browser window but in a simpler way. I'm reading the mozilla doc, but it's not clear if I can implement external library inside the build and no updated info about custom build creation is found online.
No, you cannot replace chromium inside Electron because the entirety of how Electron works is using chromium.
As far as if you could do something yourself - I'd say just use Electron. Chromium isn't that bad, although it is resource intensive.
I'm trying to get webgl running on my firefox (v37.0.2) via software acceleration with mesa. I tried following the steps that have been stated in this article:
http://www.binarytides.com/enable-webgl-firefox-ubuntu/
However, I am unable to find any parameter named 'webgl.osmesalib' in about:config section? Has this been removed (or renamed)? If yes, then how should I instruct firefox to use mesa's software acceleration for webGL?
Looks like support for OSMesa was removed in favour LLVMpipe.
Basically I'm going to distribute my Selenium program to a number of clients for automation purposes.
Rather than asking every customer to have FireFox installed (and risking possibly incompatible versions) I would prefer if I could have FireFox (or whatever browser) packaged in my program directory (perhaps a portable version).
All my customers will be using Windows btw.
Anyone tried this or have any suggestions to how this could be accomplished?
EDIT: I suppose I could use PhantomJS with selenium and just package my software with the phantomjs driver. That would not require any external browsers to work, would it?
You have also HTMLUnit headless browser option. Please note that it has own proprietary JavaScript rendering engine so need ensure that your test also will work with the "regular" browsers.
Another option is to use Selenoid and Docker for Windows. Your customers could download easily removable images with browsers (no need to clutter Windows with browser files) and run your test suite in multiple containers in parallel.
I have developed a web plugin for Safari. It works correctly in XCode (debug), but it can not be found by Safari. The web plugin was copied in /Library/Internet Plug-Ins/.
Does someone know the answer? Thanks!
Safari 5.1 and later no longer supports Webkit Plugins. (I assume you're talking about that and not an NPAPI plugin?)
I found the answer by myself.When using xcode for debuging, the 32-bit plugin can be compiled.but only use safari run plugin,the plugin must be compiled 64-bit.
I have recently developed the plugin for web browsers on Mac OS X.
Developed by XCode, my bundle located in /Library/Internet Plug-ins.
Chrome, Safari, Firefox catch this plugin but Opera doesn't.
How can my plugin be caught by Opera?
It’s difficult to answer your question without more information about your plug-in.
The plug-in must be located in “/Library/Internet Plug-ins” and the bundle must have a .plugin extension instead of .bundle. Is the plug-in listed in opera:plugins?
This Mozilla Developer Network article on plug-ins should be very useful.
Daniel, Mac Quality Assurance at Opera Software ASA.
How do you declare your plugin info (name, version, MIME types, etc.)? Most browsers support the new Info.plist method, but it may be that Opera requires that you also use the old resource-bassed approach.
Try creating a FireBreath Plugin and then look at what differs between how it works and how you built yours. Alternately, just use a FireBreath plugin -- it's a heck of a lot easier to deal with than making your NPAPI plugin from scratch and works around a lot of browser issues and inconsistencies.
FireBreath plugins work as NPAPI plugins on mac and have been reported to work in Opera.
I spent weeks looking for the solution, but it appeared incredibly simple: rename YourPlugin.bundle to YourPlugin.plugin !
Did not even require the .rsrc file as it was recommended elsewhere.
:)
You could try putting you plugin in /Library/Internet Plug-Ins/ When opera didn't load the plugin.
I do not know why this will happen since opera said it could be put # ~/Library/Internet Plug-ins/ Opera Document