Ladybird passes the Apple 90% threshold on web-platform-tests

https://twitter.com/awesomekling/status/1974781722953953601

by sergiotapia • 10 months ago

950 233 10 months ago

dotancohen• 10 months ago

The linked tweet notes that this is an important milestone in getting Ladybird considered as an alternative browser engine in iOS.

jonny_eh• 10 months ago

Good context for why "Apple" is in the headline

jsheard• 10 months ago

...in the EU at least, anywhere else Apple is going to say "no" regardless of how good your engine is.

andrewl-hn• 10 months ago

How does it work for the likes of Google and Mozilla? Do they use their own engines for iOS versions in the EU and wrap WebKit for other areas?

zb3• 10 months ago

So was there any app with an alternative browser engine already approved by Apple?

ActionHank• 10 months ago

IRC I think the roadblock isn't that they need to be approved, but that they can only distribute in the EU.

mcny• 10 months ago

Is distribution the only problem? If Mozilla or Google were to make their code freely available on some git forge like GitHub and I cloned the repo and built it myself, would I be able to run it for seven days or something in the US?

pizlonator2• 10 months ago

Super impressive that an independent, non-corpo project has gotten this far this quickly.

tracker1• 10 months ago

Definitely... IF they keep this up, they will be a real contender by the end of 2027. I keep saying I'd like to see a similar push for Servo though... since it's probably the next most feature-rich engine option. It really needs a corresponding browser project to go along side it though, since FF/Mozilla isn't that interested.

radlad• 10 months ago

I believe this would be Verso: https://github.com/versotile-org/verso

fabrice_d3• 10 months ago

It looks like Amazon has people looking at Servo integration in GTK: https://blogs.gnome.org/nacho/2025/10/01/servo-gtk/

nicce3• 10 months ago

But how to pass tests securely, is completely different problem. This is conformance testing. But impressive regardless.

nonethewiser• 10 months ago

Can you elaborate? What do you mean by how to pass tests securely? It doesn't read like you mean security tests but otherwise I have no idea what you're talking about.

ericmcer• 10 months ago

It is nuts, when you think about how much a browser does, it is a crazy feat.

Just building a good html/css renderer and a JS engine is crazy, but now you are hooked into the ecosystem and at the mercy of whatever comes next. Chrome can push back against proposals but little browsers either use chromium or are basically in a riptide trying to make sure they keep up.

echelon4• 10 months ago

The government(s) need to force Google to obey web standards that are set by an industry consortium. One that also has small player participation as a requirement.

If Google is strong arming or pushing ahead their own agenda, the standards body should have plenty enough votes to veto.

And for teeth, compliance should be a requirement for Google to even be allowed to have its own browser. If they break it, no more browser for Google.

troupo7• 10 months ago

Chrome can push back against proposals

The problem isn't Chrome pushing back proposals. The problem is Chrome pushing ahead with its own proposals regardless of anyone: https://news.ycombinator.com/item?id=45371575

ksec• 10 months ago

It is nuts, when you think about how much a browser does, it is a crazy feat

At this point a modern browser is basically an operating system.

ur-whale• 10 months ago

Super impressive that an independent, non-corpo project has gotten this far this quickly.

Well, it could be that AI actually speeds up development, who knows.

Valodim• 10 months ago

Data so far says that it doesn't https://mikelovesrobots.substack.com/p/wheres-the-shovelware...

didibus2• 10 months ago

Are they really non-corpo? I remember seeing some corpos bankrolling it?

And in that sense, is it better than Gecko with firefox, which is non-profit?

gpvos2• 10 months ago

I don't remember that; maybe you can look it up?

Ladybird is still far from usable or fast enough to even start comparing it to Gecko.

xaxaxa123• 10 months ago

cloudflare is sponsoring. says it all.

EgregiousCube• 10 months ago

What does that say?

ac292• 10 months ago

I know what you meant by "non corpo", but the Ladybird organization is literally a corporation: https://ladybird.org/assets/documents/public-records/2024-03...

culi3• 10 months ago

A nonprofit corporation

X0nic• 10 months ago

I wonder how hard the last 10% will be? If its a typical software project its going to be 90% more effort for the last 10%.

nicce3• 10 months ago

Browsers have been historically the biggest and most difficult projects, so hard to say why it wouldn’t be. When they can start promising 20k bounties for segfaults, they are getting close.

9cb14c1ec02• 10 months ago

They are pretty far way from that. I still think it is one of the most exciting open source projects in recent years.

tredre32• 10 months ago

Browsers have been historically the biggest and most difficult projects

That's just a tired thrope that keeps being repeated by people who don't know any better.

al_borland2• 10 months ago

And the last 1% will be constantly changing, and never really “done” as a result.

90% is Apple’s standard. I wonder what the general public requires.

ndriscoll• 10 months ago

The general public probably just needs basic HTML/CSS/JS support along with gzip, zstd, and common image and video formats. Stuff like beacons, accelerometers, bluetooth, device memory, webusb, battery status, etc. (so basically all of the "platform" part of the "web platform") are either extremely niche or actively harmful.

stronglikedan• 10 months ago

OT, but I really like the name Ladybird for a silly reason - it's the name of Hank Hill's dog. Whenever I hear it I think of her and smile. That's right, the thought of a cartoon dog makes me happy. I told you it was silly.

tonyedgecombe• 10 months ago

In the UK a ladybird is what Americans call a ladybug.

beepbooptheory• 10 months ago

Well and knowing Hank, the dog is surely named after Lady Bird Johnson.

https://en.wikipedia.org/wiki/Lady_Bird_Johnson

dylan6042• 10 months ago

You seem to totally be overlooking who Hank was paying homage to with that name. Thanks to Ladybird, spring time in Texas provides a colorful palette of wildflowers, especially the bluebonnet, to travelers along the highways.

lioeters• 10 months ago

I heard the story of Lady Bird Johnson and the bluebonnets on a sunny spring day, on a passenger seat of a pickup truck driving through the Hill Country, among endless fields and hills covered in wildflowers. We were probably listening to Merle Haggard or Willie Nelson, one of them outlaw country boys. That's how I know America the Beautiful does exist, though it may be hard to believe from the darkness that covers the land today.

scosman• 10 months ago

Me as engineer: it's wild a big corporation dictates a quality bar and limit API access for 3rd party software.

Me as customer: oh man I'm sure glad stuff is reviewed to some quality bar and the OS limits API access.

isodev2• 10 months ago

Me as customer: having trouble using the likes of GitHub and Threads using the "OS sanctioned browser"

cosmic_cheese• 10 months ago

That's on nobody except Microsoft and Meta for testing against Chromium only.

concinds2• 10 months ago

Me as a consumer:

- browsers having to go through Apple means slower updates (including for bugs or security), not needed on Mac or any other platform

- Apple forces every alternative-engine browser to use a pretty broken framework that Safari does not use, not needed on Mac or any other platform

- Apple's restrictions on alternative engines in the EU are a vast list of malicious compliance[0], making those engines a theoretical academic exercise, so they're definitely still fucking you as a consumer.

[0] https://open-web-advocacy.org/blog/apples-browser-engine-ban...

ryandrake• 10 months ago

Those views are "you as a developer." Very few actual end users think about or care about any of these things.

echelon4• 10 months ago

Me as a consumer:

- Companies forking over more margin and control to Apple mean they have to make up for it in other ways.

- Apple and Google wielding so much control removes overall choice and competition from the market.

- I sure hope Apple and Google only ever have my interests at heart because they have all the keys to the kingdom and could really screw me over.

- I wish I could do XYZ with my phone. Too bad...

- I wish there were more diverse phone SKUs. It used to be wildly competitive and we used to have all kinds of innovation because it wasn't so winner-take-all. Where's my eink low power open source phone with gpio and thermal sensors, etc.

- My car and phone feel like frenemies.

- There's still no good alternative OS for phones. Probably because it'd be impossible to make money and compete against titans.

- The company that removed manifest V2 is now forcing app signing? I wonder if they'll limit web browsing options and ad blocking soon.

- Why do I have to de-Google my phone with every update? They have tyranny of defaults (that lay people can't adjust) and just reset the defaults back to themselves every time you upgrade. Or give you scare walls and alerts asking to be default again. Lay people are probably stuck with this.

- "Google News" legitimately has half page ads and popups and that's the default experience. It is physically impossible to even read the news.

mmis10006• 10 months ago

Me as engineer: does apple even pass the bar by their own? I hit shit tons of safari only bug that is 100% non web-compliment. Some are so stupid that as a normal person writing web pages must have ran into it already.

luxuryballs• 10 months ago

also me as an engineer:

I hope it’s the correct 90%!

SilverElfin• 10 months ago

It’s not wild, it is anti-competitive and entirely about maintaining control in unfair ways

beeflet• 10 months ago

You couldn't figure out by yourself not to use a dysfunctional browser?

daft_pink• 10 months ago

I think it’s just fantastic that the Ladybird browser is close to being usable. I was under the impression this was going to take many years before it became competitive.

skywal_l• 10 months ago

Don't hold your breath though. Looking at the September progress report[0] there are many many things to iron out. It's great progress but there are still several years of development for LB to be ready.

[0] https://www.youtube.com/watch?v=6vsjIIiODhY

potwinkle2• 10 months ago

I've started using it for some websites. It's surprisingly very capable already.

mrweasel• 10 months ago

While I haven't tried it myself, I've seen a few of the monthly summaries videos. Passing the tests and being fast enough for daily usage is two very different things and right now Ladybird doesn't appear to be all that speedy.

Still an amazing feat of development from the entire team.

bangaladore• 10 months ago

I was going to say the same thing.

Why are the tests so disconnected from the usability? My assumption is the tests are closer to a unit test, while browsing a page is essentially an E2E test, and if anything in the pipeline goes wrong (especially given that we use complex JS everywhere) the result is essentially useless.

MatthiasPortzel• 10 months ago

Three years ago I was very skeptical of Ladybird. But two things have changed. First, they have funding for 8 full time engineers, which I definitely wasn’t expecting. Second, it’s been three years. So given that, I am more optimistic.

There’s still a very long way before they can compete with Chrome, of course. And I’m not sure I ever understood the value proposition compared to forking an existing engine.

rhdunn2• 10 months ago

The value proposition is not having vendor lockin and having WebKit/Blink be the defacto behaviour. For example the Ladybird team have found and raised spec issues in the different specs.

Another example is around ad blockers -- if Blink is the only option, they can make it hard for ad blockers to function whereas having other engines allows different choices to be made.

zaphirplane• 10 months ago

Who is backing it ? That’s a bit of money Nm can see the list, wonder what’s in it for those companies

_flux• 10 months ago

I do wonder if it's the case of "90% of completeness takes 90% of time; the remaining 10% takes another 90%".

Though, I suppose even if true, it would still be a pretty good timeframe.

InsideOutSanta• 10 months ago

I'll guess that the remaining 10% will take more than another 90%, and also that it will keep growing as time goes on. Web standards are becoming more complex every day.

IshKebab• 10 months ago

Yeah definitely. For the web it's more like the last 0.1% takes 99.9% of the time. And it's not like you can skip it either. Nobody is going to use a browser that is missing 0.1% of the web platform - that probably means something like 1% of websites are broke in some way and that's a terrible experience.

They are decades of work away from having a browser that would be competitive with Chrome or Firefox.

GalaxyNova• 10 months ago

It really goes to show what a dedicated team can accomplish. Before Ladybird it was taken for granted that building an entirely new browser engine would take decades and people would laugh at you for even bringing it up.

typpilol• 10 months ago

To be fair. They have a really long way to go.

serial_dev• 10 months ago

Well, it is going to take decades…

It’s a valuable, ambitious project, but it is going to take a while before it can be used for anything real.

badsectoracula• 10 months ago

Before Ladybird every time someone brought up about making a new web engine, pretty much every top voted comment here on HN was about how that was impossible to do, often bringing up how even a giant like Microsoft had to abandon their engine.

At least now the cynical pessimistic takes changed from "impossible, not even MS with their giant teams can do it" to "it may take decades for this small team to do it".

ChrisRR• 10 months ago

Don't worry. If the web browser ever becomes fast enough to be usable, even more javascript crap will be dumped on every website to slow it back down again

flakiness• 10 months ago

There is a big jump in the graph! I wonder what contributed to that big improvement.

apetresc• 10 months ago

Someone asked Andreas on that Twitter thread - it was the merging of the CSS Typed Object Model API spec.

cupofjoakim• 10 months ago

This PR added ~6400 passes for some css stuff. That's not enough to warrant the spike I think, but surely helped: https://github.com/LadybirdBrowser/ladybird/pull/6370

foxglacier• 10 months ago

You can't tell if it's a big jump because the graph doesn't show the axes. Maybe it went from 89% to 90.2%. The jump may also be no more than typical previous increases not shown off the left-hand edge.

jerf2• 10 months ago

Thank you for the belly-laugh. It's Goodhart's Law in graph form.

"Oh, is this metric important? Let me get right on that."

No shade intended towards the Ladybird team. You were given the terms and you're behaving rationally in response to them. More power to you. It's just a fantastic demonstration of what it looks like to very suddenly be developing against a very specific metric.

xmprt• 10 months ago

Have you tried using Ladybird recently? Admittedly I haven't but I've seen the rapid progress they've made over the last year. They might just be targeting this arbitrary metric but I'm inclined to believe that they've made real progress towards building a usable browser.

pizlonator2• 10 months ago

I think that this metric correlates well with the browser being usable on real websites

Also, I don't think that the Ladybird folks are just doing the bare minimum to only increase their score on WPT. They're implementing each feature in such a way that basic browsing seems to work better and that their WPT score improves.

fabrice_d3• 10 months ago

The wpt score is not that well balanced. Look at https://staging.wpt.fyi/results/?product=servo&product=ladyb... : out of about 2 million tests, more than half are for the "encoding" category. Good encoding support is needed for sure, but likely not at that level of prevalence.

fragmede• 10 months ago

I mean, sure, but can you point to any work that you think they should be doing that they're not doing because they're chasing this benchmark instead of doing whatever it is you think they should be doing?

dzaima• 10 months ago

While it is kinda unfortunate to have one unbalanced test suite as the major external progress indicator, there are.. like no other good options that don't involve someone manually going through like the top 1000 sites or something and checking whether they look good. That leaves having no progress indication whatsoever, which is also pretty bad.

And, in any case, implementing more of the standards is just simply good, and would need to be done at some point anyway.

XCSme3• 10 months ago

What JS engine does it run on?

Fuzzwah• 10 months ago

It's own, LibJS

https://github.com/LadybirdBrowser/ladybird/tree/master/Libr...

XCSme3• 10 months ago

Wow, how does it compare to V8 ? They spent many years optimising it.

austin-cheney• 10 months ago

It is all original code.

XCSme3• 10 months ago

That's really impressive

liquid_thyme7• 10 months ago

I wish them well, but browsers are very much pay-to-play. Google had to pay their way to their current dominant position.

mouse_2• 10 months ago

Don't forget, Firefox didn't succeed because Firefox was good, it succeeded because IE was bad. People don't like having to choose between Google Chrome and Google Firefox.

npteljes2• 10 months ago

Ad blockers were another huge draw, in my experience.

postepowanieadm• 10 months ago

I'm not sure about it - there were other contestants: Opera, Netscape, even the big Mozilla Suite.

lenerdenator2• 10 months ago

Depends on what you mean by "pay-to-play".

Google's business model was to take FLOSS software, ostensibly make it work without them being involved, but make it obvious that if you wanted things to be as simple as possible, you needed to use their version of it. Can you use Chromium as your daily driver? Sure, but it's not as simple as just using Chrome. Android is even more like this. And of course, the simplest way to use this software also just happens to give Google a ton of your data, which enabled them as an ad-serving company.

They wouldn't have given the browser away for free if they weren't making at least the cost of the browser development back in the take from ad revenues.

I guess you could argue that the moves to buy services like YouTube and other big pillars of the web and have that reflected in Chrome development cost money.

liquid_thyme7• 10 months ago

I meant paying for distribution via the usual channels (toolbar vector, s/w bundling, etc) and paying for their browser as a default with system integrators.

They also had a good browser (before it became spyware), but there is no conceivable way to get a billion people to care about javascript performance and memory usage.

lofaszvanitt2• 10 months ago

Pay? You mean putting the "you are using X, why not try chrome" adtext everywhere for every search result?

gkbrk2• 10 months ago

And paying money to software vendors to bundle Chrome with "Set Chrome as default browser" ticked by default. This is exactly the same thing all the malware browsers and toolbars did in the time period too.

nicoburns3• 10 months ago

More like having a team of between 1000 and 1500 full time software engineers working on it over a period of more than a decade.

liquid_thyme7• 10 months ago

Yes, but also paying for distribution and paying for it to be the default browser.

dmix• 10 months ago

That plus making the best browser on the market for 15yrs

liquid_thyme7• 10 months ago

A browser spying on users for marketing purposes is a disqualifier for me.

lenerdenator2• 10 months ago

If nothing else, having an alternative engine with any amount of viability at all that isn't Blink is great news. I'll be interested to see how this progresses.

bbminner• 10 months ago

Now that 90% of the work is done, it is only 90% of the work that remains :)

guywithahat• 10 months ago

It's always struct me as interesting that ladybird is built with C++. I like C++, and prefer it to languages like Rust, but it's not uncommon to see new OSS projects using weird languages and the newest tools. Lots of languages offer improvements in regards to threading models, development speed, or cross-platform support which we don't get in C++.

I suppose their success is likely directly related to the fact they made reasonable, practical development choices, but still.

zrm2• 10 months ago

It's the same language most of the code in Chrome and Firefox is written in.

It's also not clear what you're looking for in terms of cross-platform support. Some languages provide better standard library support for UI elements, but that's the part a browser will be implementing for itself regardless.

timeon• 10 months ago

Sure but those browsers started long time ago and are implementing some of newer stack in Rust.

miloignis• 10 months ago

I believe they are or will be transitioning to Swift: https://x.com/awesomekling/status/1822236888188498031

hamandcheese2• 10 months ago

This is often cited, but it seems like there has been very little movement toward swift since this tweet.

drnick1• 10 months ago

I don't think this will ever happen. They may starting using Swift or some other newfangled language like Rust for some components, but it's almost never a good idea to rewrite something in a different language, and C++ is still the gold standard for this type of project.

BirAdam• 10 months ago

LadyBird grew out of the SerenityOS project which was originally written in C++ (they've since moved to Jakt). All software for Serenity had to be written natively for the OS, and C++ was the language originally supported there. Andreas had worked on browsers previously (notable Safari), and was already a seasoned C/C++/ObjC developer. While one can cite many valid reasons for using a C language for a browser (and OS), I think his experience and preferences were likely a large part of it.

zelphirkalt3• 10 months ago

The language is actually something that makes me look elsewhere. We already have enough sufficiently vulnerable browsers and other network related software. Choosing C/C++ as language may work to make something that works, and it may be in the realm of experience the people building it have. However, it does not make this browser stand out in terms of security/safety. While they may deliver tremendous work, that work is still "just" another Cee thingy. Experience tells us, that even elite C/C++ hackers will make mistakes regarding memory management. Mozilla slowly using more and more Rust in Firefox seems better from that perspective, if they are actually still trying to do so.

jgraham• 10 months ago

As someone who's been quite heavily involved with web-platform-tests, I'd caution against any use of the test pass rate as a metric for anything.

That's not to belittle the considerable achievements of Ladybird; their progress is really impressive, and if web-platform-tests are helping their engineering efforts I consider that a win. New implementations of the web platform, including Ladybird, Servo, and Flow, are exciting to see.

However, web-platform-tests specifically decided to optimise for being a useful engineering tool rather than being a good metric. That means there's no real attempt to balance the testsuite across the platform; for example a surprising fraction of the overall test count is encoding tests because they're easy to generate, not because it's an especially hard problem in browser development.

We've also consciously wanted to ensure that contributing tests is low friction, both technically and socially, in order that people don't feel inclined to withhold useful tests. Again that's not the tradeoff you make for a good metric, but is the right one for a good engineering resource.

The Interop Project is designed with different tradeoffs in mind, and overcomes some of these problems by selecting a subsets of tests which are broadly agreed to represent a useful level of coverage of an important feature. But unfortunately the current setup is designed for engines that are already implementing enough feature to be usable as general purpose web-browsers.

sleepybrett• 10 months ago

Then talk to apple. They are the ones who put this bar in place.

manmal2• 10 months ago

Why are you bringing this up, when it’s not been implemented as a metric here, but because Apple requires it for iOS.

hamandcheese2• 10 months ago

but because Apple requires it for iOS

Therefore it is a metric used by Apple.

Klonoar5• 10 months ago

This is a headline that is very easy to misread and or misunderstand. I don’t find their comment to be that out of place at all.

tssva• 10 months ago

The tweet mentions that this is an arbitrary metric thrust upon them by Apple, so I don’t think they would necessarily disagree with you. During the monthly updates they do also show the passing number of tests without including the encoding tests because of how much they skew things.

troupo7• 10 months ago

The problem is, there's no other good metric. We used to have Acid tests for CSS, but in absence of that, it's as good metric as any.

munchlax• 10 months ago

Ladybird will be faster than anything with an arbitrary metric thrust

koolala• 10 months ago

Could a hand-picked subset be selected to make that metric?

culi3• 10 months ago

Everything you said sounds very reasonable, yet the "Browser-Specific Failures" graph on the main page of the wpt.fyi website explicitly misleads us into thinking

PS I'm a big fan of the work and appreciate what you do. I check the interop page about once a week!

jebronie• 10 months ago

As someone who's been quite heavily involved with having a brain, I'd advocate for using of the test pass rate as a metric for how many tests are passed.

lossolo• 10 months ago

What's the security story in Ladybird? Do they use sandboxes etc? I'm a bit concerned that hundreds of thousands of lines of C++ browser code written in just three years could be a minefield, but I hope I'm wrong.

pilaf• 10 months ago

Last I heard they were planning to move to Swift [1] partly because of the safety features. Apparently there are still some blockers [2] preventing that move though.

1: https://x.com/awesomekling/status/1822236888188498031

2: https://github.com/LadybirdBrowser/ladybird/issues/933

fsflover• 10 months ago

If you care about security, consider using Qubes OS, which runs everything in hardware-isolated virtual machines. My daily driver, can't recommend it enough. Ladybird can already be safely used on Qubes.

d33• 10 months ago

I just tried building and running it. Surprisingly many websites already load fine, though Youtube doesn't and Vimeo/Reddit comment section crashed it. Still, the results are quite encouraging! It takes ~6GB of HDD to build it.

everyone• 10 months ago

Oh yes cus Apple really care about the web.

logicallee2• 10 months ago

Along the same lines, the State of Utopia will be building a free web browser for everyone, once AI is strong enough to do so. Please feel free to vote on feature ideas here: https://pollunit.com/polls/ahysed74t8gaktvqno100g

skulk• 10 months ago

teleports the founder and his wife to the same location so they can be together in person holding hands - they're already in the same same city and want to meet immediately, so they are 99.98% of the way there! They're both working 10 hours a day to bridge the remaining 0.02%. Following this proof of concept, other people will also be allowed to date, however at the moment all dating is prohibited until the founder and his wife meet successfully.

Uhh.... I.... ok.

logicallee2• 10 months ago

I didn't originally include this text in the browser feature vote, but I showed my wife the feature vote and she insisted that I need to include this part until it's solved. I can't wait for this to be done.

I didn't see any feature suggestions from you, please feel free to suggest a browser feature for AI to build once it is powerful enough to do so, you can do so at the bottom of the page. It only takes a few seconds. Thank you.

sn0n• 10 months ago

How's the ladybird gtk stuff coming along?

DeepYogurt• 10 months ago

You love to see it

Vipsy2• 10 months ago

The real test isn't passing 90%—it's whether they can keep pace as the web platform adds new APIs faster than any independent team can implement them. Browser engine development has become a regulatory moat, and breaking it requires either massive funding or accepting permanent incompatibility with the "modern web."

Still rooting for them. Browser monoculture is worse than metric gaming.

Vipsy2• 10 months ago

The WPT score is a flawed metric (encoding tests are overweighted), but it's one of the few objective yardsticks we have. What matters more is that Ladybird is finding spec ambiguities by implementing from scratch rather than cargo-culting Chrome's behavior. The real test isn't passing 90%—it's whether they can keep pace as the web platform adds new APIs faster than any independent team can implement them. Browser engine development has become a regulatory moat, and breaking it requires either massive funding or accepting permanent incompatibility with the "modern web." Still rooting for them. Browser monoculture is worse than metric gaming.

LeFantome2• 10 months ago

Implementing a web browser is running to stand still for sure. But it is clear that Ladybird is implementing the spec faster than it is evolving.

I am not saying they do not have A LOT left to do. But your comment almost makes it sound like they are falling behind and that is most certainly not the case.

The team is quite pragmatic and many perfectly modern websites work already. Again, A LOT to do. But it is looking very doable. They still expect a "usable" release sometime next year.

Ladybird passes the Apple 90% threshold on web-platform-tests

Related Stories