Example Design Is Broken Issue 124448 Webcompat Web Bugs Url: example browser version: firefox 116.0 operating system: mac os x 10.15 tested another browser: yes safari problem type: design is broken. Do you have a screenshot of the issue you would like to share? a web compatibility issue occurs when a website behaves differently across browsers. sometimes a website will load on one browser and crash or render in a strange way on another. sometimes websites have bugs that prevent them from working in all browsers.
Issue Closed Issue 124156 Webcompat Web Bugs Github To successfully diagnose each issue, you will generally want to start with a fresh user profile for the browser you are testing. this helps minimize the potential for unrelated issues to complicate the diagnosis or make the reported issue irreproducible (especially from browser extensions and other customizations). Open source community for web compatibility. report bugs from websites or for browsers and help us move the web forward. Problem type: design is broken description: items not fully visible steps to reproduce: i was resolving warnings in github, as owner of a repo. (only as owner of repo, can i see the button to resolve warnings). when i press the button to dismiss the warning, it gives me three options, "false positive", "used in tests", "won't fix". Mozilla tries to tackle this in three ways: a bug tracker for the web webcompat where anybody can report any bug for sites that work only in one browser. implement non standard features like things with webkit prefixes. firefox 49 had more than 60 non standard webkit features added, and that is only one release.
Archive Is See Bug Description Issue 32903 Webcompat Web Bugs Problem type: design is broken description: items not fully visible steps to reproduce: i was resolving warnings in github, as owner of a repo. (only as owner of repo, can i see the button to resolve warnings). when i press the button to dismiss the warning, it gives me three options, "false positive", "used in tests", "won't fix". Mozilla tries to tackle this in three ways: a bug tracker for the web webcompat where anybody can report any bug for sites that work only in one browser. implement non standard features like things with webkit prefixes. firefox 49 had more than 60 non standard webkit features added, and that is only one release. Web compatibility. a place to move bugs for sites or content that does not work in firefox, but works in other browsers. file new bugs at webcompat issues new. this component was previously called tech evangelism. watch. Url: example browser version: firefox mobile 115.0 operating system: android 14 tested another browser: yes chrome problem type: design is broken description: items not fully visible steps to reproduce: some problems vmcant. You could quickly identify if a site sends the same design content to firefox android, safari ios or a blink browser on android. this is less and less meaningful, as many websites in the last ten years have switched to responsive design where the content automatically adjusts depending on the size of the screen. I suspect that the bulk of the issues are related to firefox using
tags on the edited content where chrome does not, and similar types of differences. basically the kinds of stuff you can find if you look at the sub bugs in bugzilla.mozilla.org show bug.cgi?id=1341152.
Webcompat Design Is Broken Issue 37781 Webcompat Web Bugs Web compatibility. a place to move bugs for sites or content that does not work in firefox, but works in other browsers. file new bugs at webcompat issues new. this component was previously called tech evangelism. watch. Url: example browser version: firefox mobile 115.0 operating system: android 14 tested another browser: yes chrome problem type: design is broken description: items not fully visible steps to reproduce: some problems vmcant. You could quickly identify if a site sends the same design content to firefox android, safari ios or a blink browser on android. this is less and less meaningful, as many websites in the last ten years have switched to responsive design where the content automatically adjusts depending on the size of the screen. I suspect that the bulk of the issues are related to firefox using
tags on the edited content where chrome does not, and similar types of differences. basically the kinds of stuff you can find if you look at the sub bugs in bugzilla.mozilla.org show bug.cgi?id=1341152.