MSEdgeExplainers/WebInstall/explainer_same_domain.md at main · MicrosoftEdge/MSEdgeExplainers
This proposal is exactly what I was asking for!
C’mon browsers, let’s make this happen!
First Experiments with View Transitions for Multi-page Apps
Some great ideas for view transitionts in here! Also:
If you look at any of the examples on a browser that does not support them, the pages still function just fine. The transitions are an extra that’s layered on top if and when your browser supports them. Another concrete example of progressive enhancement in practice.
Related links
12 Modern CSS One-Line Upgrades | Modern CSS Solutions
I love how straightforward these bits of CSS are—time to rip out some of those old complicated hacks and workarounds!
Stop supporting Internet Explorer!
The headline is clickbaity, but the advice is solid. Use progressive enhancement and don’t worry about polyfilling.
When I say ‘Stop supporting IE’ it means to me that I won’t go the extra mile to get unsupported features working in Internet Explorer, but still make sure Internet Explorer users get the basics, and can use the site.
How we think about browsers | The GitHub Blog
JavaScript doesn’t get executed on very old browsers when native syntax for new language features is encountered. However, thanks to GitHub being built following the principle of progressive enhancement, users of older browsers still get to interact with basic features of GitHub, while users with more capable browsers get a faster experience.
That’s the way to do it!
Concepts like progressive enhancement allow us to deliver the best experience possible to the majority of customers, while delivering a useful experience to those using older browsers.
Read on for the nitty-gritty details…
Be the browser’s mentor, not its micromanager. - Build Excellent Websites
This one-page site that Andy has made to illustrate his talk at All Day Hey is exactly what I was talking about with declarative design.
Give the browser some solid rules and hints, then let it make the right decisions for the people that visit it, based on their device, connection quality and capabilities. This is how they will get a genuinely great user experience, rather than a fragmented, broken one.
Related posts
Browser support
Here’s Clearleft’s approach to browser support. You can use it too (it’s CC-licensed).
Displaying HTML web components
You might want to use `display: contents` …maybe.
Upgrades and polyfills
Apple’s policy of locking browser updates to operating system updates is bad for the web and bad for the planet.
Continuous partial browser support
Treat every browser feature like an experimental feature.
The Web Share API in Safari on iOS
Unexpected behaviour in the clipboard.