interop
web-bugs
interop | web-bugs | |
---|---|---|
15 | 356 | |
247 | 718 | |
3.6% | 0.8% | |
7.0 | 0.0 | |
9 days ago | 11 months ago | |
- | Mozilla Public License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
interop
-
Still no love for JPEG XL: Browser maker love-in snubs next-gen image format
There is popular demand (including from Adobe https://github.com/web-platform-tests/interop/issues/430#iss... ), which is arguably evidence against (2).
-
AV1 video codec gains broader hardware support
Microsoft Edge does support AV1, but weirdly only through a Microsoft Store extension [1], even though Chrome has support built-in. This actually really sucks because in practice hardly any normal consumers would bother to install a strangely named extension, and so web developers have to assume it's largely unsupported in Edge. Safari ties support to a hardware decoder, which I suppose is understandable to avoid accidental battery drain from using a software codec, and means eventually in some year's time support can generally be relied upon when enough new hardware is in use. But that won't happen with Edge as things stand!
I think it's high time the web had a single audio and video codec choice that was widely supported, which is why I've proposed support for AV1 and Opus for the Interop 2024 effort [2] [3].
[1] https://apps.microsoft.com/detail/av1-video-extension/9MVZQV...
[2] https://github.com/web-platform-tests/interop/issues/485
[3] https://github.com/web-platform-tests/interop/issues/484
-
Adobe proposes JPEG XL for interop web platform tests
This is the comment to read:
https://github.com/web-platform-tests/interop/issues/430#iss...
It got me drooling for JPEG XL like I never did for WebP or HEIC.
- JPEG XL Proposed for Interop 2024
-
InterOp - what can we actually expect this year?
The Interop group describe this focus area as: "enable testing for font stack capabilities and enable additional expressiveness with vector color fonts. (Font feature detection and palettes)".
-
What new CSS and JavaScript features can we expect soon? Or is it all unexpected?
I would say that overall InterOp 2022 went well, they completed most of what they planned to do. Of the 15 focus areas, 13 focus areas had an InterOp score of over 80%.
-
Improvements that CSS could use in 2023
Interop 2023 is under development, the project timeline states that a public announcement will be made this week. 🤞
-
Pluralistic: Web apps could de-monopolize mobile devices (13 Dec 2022)
https://open-web-advocacy.org/walled-gardens-report/#ios-saf...
And
https://open-web-advocacy.org/walled-gardens-report/#evidenc...
Make sure you tap more comments to see the examples.
The number one issue for building native like apps is this https://github.com/web-platform-tests/interop/issues/84
It has been buggy for as long as I can remember and never been fixed.
Not to mention the 10 years of issues with indexeddb or the issues with WebRTC.
-
Apple's claim is that it bans other browsers for security
Open Web Advocacy has been very clear that they want competition on iOS, not Chrome specifically. The reason being that the absence of competition is currently allowing Apple to deteriorate the web experience on iOS, preventing the web and web apps from competing with native apps. Their objective is to lift these artificial limitations imposed by Apple and free the web.
OWA members have actually been actively reporting WebKit bugs and interacting with the Safari team to help prioritise features and bug fixes on Twitter and elsewhere, showing the goal is to improve the overall web experience on iOS, not let Chrome to become dominant. Here is one of their detailed bug report: https://github.com/web-platform-tests/interop-2022/issues/84.
-
Apple Is Not Defending Browser Engine Choice
Container Queries and Subgrid are only available in Safari Technology Preview, not stable, and Firefox has actually been supporting Subgrid for more than 2 years. Because CQ is not supported by either Chrome of Firefox, it will be at least 2 years before we can start actually using it.
It would have been much wiser for Safari to catch up on the dozens of features they don't support that both Chrome and Firefox do, or to focus on bug fixes for the most basic features that's been broken for years. Instead, they chose to ship shiny new ones to try and convince both regulators (from the EU, UK, US, etc) and web developers that they are leading the way in feature adoption. Unfortunately this seems to be working to some extent in the web devs community. Regulators are unlikely to fall for it though.
Here is the 7 years old scrolling bug I'm referring to, which prevents any decent implementation of modals in Safari on iOS: https://github.com/web-platform-tests/interop-2022/issues/84
Here you can see that Safari has 5 times more API failures (representative of both missing features and bugs) than Chrome, and 3 times more than Firefox: https://wpt.fyi/
web-bugs
-
Google breaks search for Firefox users because of bad UA string sniffing
The thread is very long, here is the relevant comment:
https://github.com/webcompat/web-bugs/issues/131916#issuecom...
-
Chrome's next weapon in the War on Ad Blockers: Slower extension updates
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.
-
"This video is either unavailable or not supported in this browser. (Error #4000) " on twitch with new laptop
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/
-
Hamrobazaar not opening in Firefox
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.
- Web-bugs: A repo used by the Web Compatibility community to track issues
-
Switching from Chrome to Firefox? Here Are Some Tips
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
-
Firefox: WhatsApp Web cannot paste text?
https://github.com/webcompat/web-bugs/issues/125920#issuecom...
- Copy-paste broken on WhatsApp on Firefox
- 🐛 O bug que "quebrou" o Whatsapp 🐛
-
Firefox Finally Outperforming Google Chrome in SunSpider
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
What are some alternatives?
totally-not-spyware - webkit; but pwned
firedragon-browser - A Floorp fork with custom branding 🐉 (mirrored from GitLab)
UrlChecker - Android app by TrianguloY: URLCheck
temp_librewolf_prefpane - temporary repository to share librewolf built with the prefpane
construct-stylesheets - API for constructing CSS stylesheet objects
privacytests.org - Source code for privacytests.org. Includes browser testing code and site rendering.
standards-positions - WebKit's positions on emerging web specifications
icecat-win64
uBlock-Safari - uBlock Origin - An efficient blocker for Chromium, Firefox, and Safari. Fast and lean.
stealth - :rocket: Stealth - Secure, Peer-to-Peer, Private and Automateable Web Browser/Scraper/Proxy
postcss-nesting - Nest style rules inside each other
Fenix - ⚠️ Fenix (Firefox for Android) moved to a new repository. It is now developed and maintained as part of: https://github.com/mozilla-mobile/firefox-android