I think filing bugs on browsers is one of the most useful things a web developer can do.
Agreed!
Grrr…
Chrome, Edge and Firefox updates usually reach 95% of users within three months. But Safari updates are tied to a new release of the underlying operating system, so they take around 19 months to reach the same usage, and some updates may even need a new device.
This is so shameful. And glad as I am to see new features landing in Safari, as long as they hobble updates like this it’s all just pissing in the wind.
This looks interesting. On the hand, it’s yet another proprietary creation by one browser vendor (boo!), but on the other hand it’s a declarative API with no JavaScript required (yay!).
Even if this particular feature doesn’t work out, I hope that this is the start of a trend for declarative access to browser features.
Finally! View transitions for multi-page apps (AKA websites) will be landing in Chrome soon—here’s hoping other browsers follow suit. Mozilla are up for it. Apple are, as usual, silent on their intentions.
Nice to see a blog post of mine referenced to show that this is a highly-requested feature. Blogging gets results, folks!
I know that the number one cause of jank and breakage is another developer having messed with the browser’s default way of doing things.
THIS!!! A thousand times, THIS!
‘Sfunny, I’d been meaning to write a blog post on exactly this topic, but Tyler says it all …and that’s before Apple’s scandalous shenanigans.
Mobile Safari doesn’t support the min and max attributes on date inputs.
You can launch web apps as standalone apps on Mac now.
Using the CSS trinity of feature queries, logical properties, and unset.
Opening an external link in a web view appears to trigger a reload of the parent page without credentials.
My response to the Competition and Markets Authority’s mobile ecosystems market study interim report.