mozregression VS web-bugs

It seems broken for me too on 122.0a1 nightly. Can you use mozregression to narrow down when it happened? That would greatly help narrow down what part broke, and help to file an informative bug.

If you think it is a regression in Firefox, you can try mozregression: https://mozilla.github.io/mozregression/

If you want to find the bug, you can run a mozregression to find what broke it.

In my experience it's always Mutter, but it seems the type of issue where mozregression can help you find the exact problem.

If this is a regression on Firefox's side, eventually even the ESR will have the same issue. If you can, use mozregression to find the offending changeset and file a bug. Share the link to your report if you do.

That could be an issue with the site's media format that Firefox doesn't workaround, or a bug. Test in safe mode, and Nightly. If you can reproduce it on Nightly and this is a recent issue, find the regression window using mozregression and file a bug. Share a link to your report.

I'm not sure what black line you see, but these issues are usually resolved by updating one's GPU's drivers. If you end up filing a bug, and you can reproduce the issue consistently, try to find the offending commit with mozregression.

I've used Firefox, for free, for over 15 years. Reporting bugs is the least I can do. Mozregression makes finding a regression bug an easier job.

Go try the mozregression tool. It's basically a program meant for debugging problems on Firefox. You can use it to download and temporarily run any version of Firefox (all the way back to version 1 I think), including nightly releases. You just pick a version of Firefox, enter a web address, it then downloads that version of Firefox and starts running it. You can use it for however long you need for testing. It's not meant for normal usage as it doesn't save any user profile stuff.

Nightly? Use mozregression: https://mozilla.github.io/mozregression/

The thread is very long, here is the relevant comment:

https://github.com/webcompat/web-bugs/issues/131916#issuecom...

https://github.com/webcompat/web-bugs/issues?q=is%3Aopen+is%...

Microsoft Teams (which I don't think many people use voluntarily) in particular breaks in stupid ways - and then in others if you spoof your user agent.

a link to the video would help with troubleshooting, seems like another case of "this site or this particular feature doesn't support firefox" otherwise report to https://webcompat.com/

Have any of you faced this? If the website is made to open only in chromium-based browsers, I am planning to report to Webcompat. But before that, I thought I would make sure from others. Any experience or quick fix would be appreciated.

Teams was a classic hellhole for me when I was using Linux. Nowadays it lets you in but Firefox genuinely doesn't support all of the features the Teams site uses. This means certain features are made unavailable to Firefox users. Forcing the user agent makes some of these partially work but they are also still broken so Mozilla doesn't want to enable a user agent override by default and Microsoft doesn't want to enable a feature that only half works.

This GitHub WebCompat issue serves as a good example history https://github.com/webcompat/web-bugs/issues/77892

https://github.com/webcompat/web-bugs/issues/125920#issuecom...

having recently looked at a firefox performance regression for filing a bugreport, tooling that tracks performance (quite publicly) sees attention, easy upload to share tracing profiles also helps: https://firefox-source-docs.mozilla.org/testing/perfdocs/ind...

Their dedicated blog keeps you posted if firefox perf is your interest https://blog.mozilla.org/performance/

If you have a particular website you notice chromium being significantly faster with, for an easy report, there's https://webcompat.com/ - though bugzilla is better than it seems when coming from github issues