Apple isn't the problem.

Apple was the first to ship :has(), which developers wanted for 20 years but was thought to be essentially impossible to implement [1].

Apple pushed to get consensus on how to implement masonry layouts in CSS [2].

And they were first to ship the new specification in a browser you can use right now [3].

This dashboard shows Apple slightly ahead in terms of new CSS features being implemented and interoperable with Firefox and Chrome [4].

[1]: https://webkit.org/blog/13096/css-has-pseudo-class/

[2]: https://webkit.org/blog/16026/css-masonry-syntax/

[3]: https://webkit.org/blog/17660/introducing-css-grid-lanes/

[4]: https://wpt.fyi/interop-2025?stable

That may have been true 5 years ago and I get developers have long memories—but that's no longer the case.

> Sure they implemented some stuff before other who cares of changes that don't disrupt their apple store model?

The conspiracy theory Apple, whose revenue was $391 billion last fiscal year sees PWAs as a "threat" is nonsensical. Also, new features for the web platform gives developers another reason to create web apps instead of a native app.

In reality, Safari's PWA support is really good; it has implemented 89% of supported PWA features vs 96% for Chrome according to the PWA scorecard [1].

> It's considered by many the new IE holding back innovation

As someone who lived through the '90s and early 2000s doing web stuff, I can assure you anyone who believes "Safari is the new IE" literally has no idea what they're talking about; they're just repeating a meme they don't understand.

I commented about this on HN recently [2].

[1]: https://pwascore.com

[2]: https://news.ycombinator.com/item?id=46338575

I remember, I was like, ohh sounds great! So I tirelessly looked for an "add to home screen" button but couldn't find it.

I had to search google to find the answer, you hve to share it!?

weird but okay, so I open the share menu. No such option there.

Again I search, ahh so you have to first edit the sharing options!

The only thing missing from the experience was a warning dialog.

Moral of the story, it doesn't matter if it works if people cant find it.

The 3rd class experience was funny but then they announced they were going to get rid of pwa's entirely.

> The need to remove the capability was informed by the complex security and privacy concerns...

When a 4T company says such things you know it must be hard.... lmfao....

I've never had to explain to an android user how to "Add to home screen". Explaining it to iphone users honestly sounded like I was trying to hack them. It drifts so far from apples usually polished UI that I cant blame them.

You could provide multiple image versions for zooming to get to the TB scale.

Computers are really good, performance is astonishing, no reason why we should never be able to use a TB size image. Never is a really long time.

Have epic panoramas, detailed scans from paintings, extremely easy game design and maps that just work.

I believe the lowest hanging fruit would be <div src="article.html">

I think formData should also be available as interactive JSON but perhaps it is possible to also populate a form with fields from a json with something like:

   <form src="mydata.json">
     <table>
       <input name="baz" type="number">
     </table>
   </form>

   {"foo" : "bar", "baz" : "42"}

   <form><table>
     <tr>
       <td><label for="foo">foo</label></td>
       <td><input type="text" name="foo" value="bar"></td>
     </tr>
     <tr>
       <td><label for="baz">baz</label></td>
       <td><input type="number" name="baz" value="42"></td>
     </tr>
   </table>
   </form>

   <datalist json="search.php?q=toyota+corolla">

Static could be better too. When search engines first started building these auto complete dropdowns the multi word input was really the killer feature. To have something like "green toyota" you would have to generate an element for all color and brand combinations? And the you want it to work for "green toyota corolla" and you get an abc kind of list length.

Perhaps a wildcard would have been fun or regex options.

  <option value="* days"></option>
  <option value="* weeks"></option>
  <option value="* years"></option>

On a different note, trying to use an accordion this simplistic is quite terrible.

https://jsfiddle.net/8m0t5af6/

Or this?

https://jsfiddle.net/8m0t5af6/1/

Not very nice.