I need to prevent my FF extension from closing when using a button with type="file".
In the past there were several workarounds and the last reported one was using the extension SDK but it has been discontinued since 2017 leaving only WebExtension API's as the only tool available to build extensions.
There was this previous post which is referenced basically everywhere but the extension SDK has since been discontinued as mentioned above.
There's also this thread on bugzilla but the latest activity was a couple months ago and prior to that 4 years ago.
Does anybody know a workaround?
Context:
Happens only on Firefox, Chrome works as it should
Extension I'm working on uses min version 57
Bug happens on desktop versions
Been developing on Windows, haven't tried any other OS's but this seems to happen on all of them
Steps to reproduce:
Setup a basic firefox extension
Add a button with type="file"
Click it to load a file and set any kind of code afterwards
The extension will open the file select (as it should) but will close the extension on the background so after confirming the selection the extension will be closed and any code that should run afterwards won't work.
Any ideas or workarounds known?
After updating Firefox (Firefox 72.0) an error appeared: "The buffer passed to decodeAudioData contains invalid content which cannot be decoded successfully." Apps don't work, because of this problem with audio playback. Has anyone encountered such a problem? Thanks.
Got the exact same problem but here's a bit more info for anyone working on a solution. The latest updates of firefox work fine on IOS and Android, the problem is on windows 10. Here are a couple of educational resources that several of our school's reported as broken by the recent update (they work fine in chrome, safari and edge):
https://www.echalk.co.uk/Science/physics/spacecadet/SpaceCadet.htm
https://www.echalk.co.uk/ComputerScience/ComputerSystems/Memory/Moonlander/memoryMoonlander.html
For comparison, here is a rource that still works in Firefox:
https://www.echalk.co.uk/Maths/estimation/fractions/estimationFractions.html
All resource were built using the same libraries, notably createJS.
I am testing push notifications from different browsers and devices. I cannot find a solution to the problem when Chrome notifications are received in the Windows 10 Notifications Centre. When I send 3 notifications in a row, clicking only at the top one results in opening the browser with specified URL. The other two after being clicked disappear, cursor seems to have a loader for a short moment (as in the case of the first working one) but nothing happens - browser does not react in any way.
Firefox handles opening URLs correctly - all three notifications result in redirecting to the specified website. Same situation happens on mobile version of Chrome (tested on Android), so there is most likely an issue with Windows 10 Notifications Centre or Chrome on desktop devices.
I would be grateful for any kind of advice. Please let me know if any other information would be useful to resolve this issue, I will provide it at the earliest convenience.
I'm currently using Oculus Rift + Touch in A-Frame (0.6.1). I haven't found any online forum on where to ask. I've tried using Firefox 55 (Which comes with WebVR), but it doesn't detect the Rift.
I can use Firefox Nightly, but it's very unstable, and it comes with different problems. My most recent one, is that the whole screen goes blank whenever I try to enter VR mode. The display is seen in the headset, and the app is able to work flawlessly. But I can't go back to Firefox and check the devtools (which is annoying).
How can I troubleshoot the Oculus Rift so I can connect it to a stable version of Firefox, such as 55?
Tried checking this:
WebVR supported, but no VRDisplays found, suddnly
But it didn't help.
Check about:config in Firefox and make sure the VR flags are enabled (specifically the Oculus one). Sometimes it may be disabled for some reason.
What are the differences from a developer point of view between Safari for Mac and Safari for Windows?
I think it boils down to evaluate differences between (if I missed something, please correct):
- Layout rendering
- Javascript behavior
The final decision to be made being:
Can developers test only on Safari Windows (knowing that we can't afford to miss important bugs)?
Thanks,
JB
As far as rendering and JavaScript are concerned, there is no difference. What is different is underlaying UI library used for browser itself, but page render is the same.
Font rendering can be different between Mac and Windows Safari as the systems typically have different fonts. As long as your page can gracefully handle missing fonts or different font sizes it should be fine.
Style sheet rendering is significantly different between Safari and Windows. To see this, try creating a page that has an element with a z-index of -1. The windows version will function without issue, the Mac version will not allow you to select the elements. Trust me, I wasted about three hours trying to figure out by trial and error why a page would work in one system but not the other. The worst bit is that when Safari doesn't render something properly, it does so without any indication. You have to debug line for line, a dreadful experience.
I have also seen problems in Safari for Windows that don't exist in Safari for Mac on CSS heavy websites. Can't remember the specifics, but they were there.
I am currently experiencing an issue where floating images in a blog with text wrapping around the image do not properly pad themselves in OS X; works fine in windows. Basically I've added padding to make the image align flush left or right such that the edge of the image is at the same offset as the edge of the text of the post; on OS X the image sticks out past the edge of the text.
A site I am working on now has a problem in safari for mac that isn't in safari 3 or 4 for windows. I cant figure it out for the life of me.
A call to java from javascript throws:
java.net.MalformedURLException: no protocol:
at java.net.URL.(Unknown Source)
at java.net.URL.(Unknown Source)
at java.net.URL.(Unknown Source)
at sun.plugin.liveconnect.SecureInvocation.checkLiveConnectCaller(Unknown Source)
at sun.plugin.liveconnect.SecureInvocation.access$000(Unknown Source)
at sun.plugin.liveconnect.SecureInvocation$2.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.plugin.liveconnect.SecureInvocation.CallMethod(Unknown Source)
on Safari windows but not safari mac.
Just wanted to add this experience I came across for Safari. Our devs are still going to look into this but not high priority for us since Windows Safari isn't much of our user base unlike Mac. But I think it relates to either (or both) - actual browser low level implementation of Safari by Apple, and/or javascript differences.
Our website recently implemented an HTML5 multiple file uploader. Single file uploads work fine on both versions of Safari. But when uploading multiple files, it fails on Windows. We had two different upload clients & endpoints for the uploader (think A/B testing flow), and one of them provided more details that may or may not point at the cause of the problem. On one of the client & endpoints, the client would send details of the filenames & filesizes of files to upload (as JSON array object) to the server endpoint (as seen via web inspector). On Mac where it worked, filesizes were valid, on Windows, they were 0 bytes.
I think the uploader is JQuery based or some other JS library. But I'm not the dev, so can't be sure. But I have a hunch this issue goes beyond JS libraries...
I had an issue with the popup blocker in Safari in Windows XP. I guess the blocker didn't accept that the user clicked a link an Flash that then triggered a JavaScript that opened the Window. The did work in the other major browsers and Safari in OS X, though. Chrome also blocked my window in XP, but not in OS X or Ubuntu.
In Mac Safari I'm able to do cross script ajax with file:/// protocol, but in Windows Mac I'm unable to do this.
I am working on a website that has pretty standard layout. I have a box that contains other divs. It works on all major browsers, from IE6+, FF3+, etc. On Safari 5 on OSX, the box is totally to the left, outside the borders of my website. On the same safari version in windows, no problem.
I am going crazy over this.