interop
dom-examples
interop | dom-examples | |
---|---|---|
15 | 87 | |
246 | 3,173 | |
3.3% | 2.5% | |
7.0 | 7.7 | |
9 days ago | 16 days ago | |
JavaScript | ||
- | Creative Commons Zero v1.0 Universal |
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/
dom-examples
-
Comparing Hattip vs. Express.js for modern app development
This is a problem! Ideally, your backend application should be platform-independent by following the standardized Web API. This way, you could run it across most JavaScript platforms.
- Web APIs
-
9 Web API's que fazem mΓ‘gica β‘π§π»ββοΈπ§πΎββοΈβ¨
Fonte: MDN web docs
-
Web OTP Api - One byte Explainer
References MDN Chrome Docs
-
The Ladybird Browser Project
> if writing a browser today is in fact easier than both writing AND maintaining a browser a decade back.
Probably not. Yeah we have web standards and some idea of how to architect it, but the total set of APIs and HTML/CSS/JS features a browser supports is probably changing faster than the Ladybird team can actively implement it. The API surface is just impossibly large compared to 10 or 15 years ago. Look at all of these: https://developer.mozilla.org/en-US/docs/Web/API
-
SSR React in Go
I added polyfills for the Web APIs used in the React code.
-
At Least Skim The Manual
In addition to pure JavaScript, there are hundreds of Web APIs documented at MDN. These APIs cover everything from the DOM to Web Workers with great detail.
-
Help me understand Web APIs (specifications and interfaces)
I'm reading MDN Web Docs on Web APIs. There are two basic sections, specifications and interfaces.
-
Can you make your own JavaScript by implementing ECMAScript standard?
The biggest difference is usually found in what non-ECMAscript standard JS web apis or features are implemented in different browsers. Here's a list of typical web APIs, and for many of them there is a compatibility table at the bottom detailing which browser do or do not support it. https://developer.mozilla.org/en-US/docs/Web/API
-
Using Web APIs to Create a Camera Application
Documentation of Web APIs and interfaces is located on the MDN (Mozilla Developer Network) website. The term "Web API" can refer to browser or server APIs. In this article, it refers to Browser APIs.
What are some alternatives?
totally-not-spyware - webkit; but pwned
wa-automate-nodejs - π¬ π€ The most reliable tool for chatbots with advanced features. Be sure to π this repository for updates!
UrlChecker - Android app by TrianguloY: URLCheck
just - A library of dependency-free JavaScript utilities that do just one thing.
construct-stylesheets - API for constructing CSS stylesheet objects
WHATWG HTML Standard - HTML Standard
standards-positions - WebKit's positions on emerging web specifications
public-apis - A collective list of free APIs
uBlock-Safari - uBlock Origin - An efficient blocker for Chromium, Firefox, and Safari. Fast and lean.
fuse - Multiplayer Online Standard
postcss-nesting - Nest style rules inside each other
vimium - The hacker's browser.