Hrm, all my web stuff that uses camera access via MediaDevices.getUserMedia() are broken in Firefox (release and nightly) but work in Chrome... No errors in console, I am in a secure context, gave permissions, and the red icon is all glowing and throbbing like it should...
-
Show this thread
-
Aside: These errors do not seem to accurately describe what happens on page reload. "AbortError: The fetching process for the media resource was aborted by the user agent at the user's request." It was already fetched... Maybe it is related to the root cause.
2 replies 0 retweets 0 likesShow this thread -
onmetadataloaded fires on Chrome, but not Firefox...
2 replies 0 retweets 0 likesShow this thread -
Source code: https://glitch.com/edit/#!/economic-enquiry?path=index.html:1:0 … View: https://economic-enquiry.glitch.me/ Works in Chrome, but not Firefox(es), even when manually calling .play() and with a clean profile.
5 replies 0 retweets 0 likesShow this thread -
-
-
Strange. It works fine for me in Firefox Nightly on 10.15.1.
@jibrewery any ideas what could be going on here?1 reply 0 retweets 0 likes -
Sorry to hear! That's a playback error (NS_ERROR_DOM_MEDIA_ABORT_ERR) from http://video.play (). Please file a bug at https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=WebRTC%3A%20Audio%2FVideo … with platform and camera info. Also, performing a https://mozilla.github.io/mozregression/ if you can would go a long way to track this down!
1 reply 0 retweets 0 likes -
Thanks, will file bug re video not displaying at all. From the various replies I've gotten, nobody has tested on 10.14.6 yet, so no apples-to-apples un-confirmation scenario yet. That abort error seems to be unrelated - happens intermittently when I shift+reload.
1 reply 0 retweets 0 likes
Filed https://bugzilla.mozilla.org/show_bug.cgi?id=1593161 … I hesitate to sink time again into mozregression. Gone down that road a few times, the toolchain is the sarlaac pit: poorly documented, doesn't work for reasons nobody can answer. And so many bugs I've reported go nowhere. I'll always report tho!
-
-
Hmm in the bug tracker one colleague tested successfully with 10.14.6. So now it appears to be an issue specifically with your machine. Sorry :-(
1 reply 0 retweets 0 likes -
Works fine in Chrome, so it's an issue specifically with *Firefox*, not an OS level problem. I'm working to narrow it down and provide as much info in the bug as possible. The hard-learned lessons of telemetry in Firefox taught us these issues are rarely just one machine ;)
1 reply 0 retweets 0 likes - 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.