Jeremy Keith – Of Time And The Web – border:none 2023 - YouTube
Here’s the video of the talk I gave in Nuremberg recently.
Analysing what the web is. It’s not the technology stack.
To count as being part of the web, your app or page must:
- Be linkable, and
- Allow any client to access it.
I think that’s a pretty good definition.
Mind you, I think this is a bit rich in an article published on The Verge:
The HTML web may be slow and annoying and processor intensive, but before we rush too fast into replacing it, let’s not lose what’s good about it.
Excuse me? Slow, annoying, processor-intensive web pages have nothing to do with the technology, and everything to do with publishers like The Verge shoving bucketloads of intrusive JavaScript trackers into every page view.
Still, we can agree on this:
Preserving the web, or more specifically the open principles behind it, means protecting one of the few paths for innovation left in the modern tech world that doesn’t have a giant company acting as a gatekeeper.
Here’s the video of the talk I gave in Nuremberg recently.
Some thoughts—and kind words—prompted by my recent talk, In And Out Of Style.
It’s great to see browsers working together to collectively implement a range of much-needed features.
These scores represent how browser engines are doing in 15 focus areas and 3 joint investigation efforts.
I’ve been having some really interesting chats with Brian about tabs, markup, progressive enhancement and accessibility. Here’s a braindump of his current thinking which is well worth perusing.
I’m very taken with Github’s tab-container element—this is exactly how I think web components should be designed!
You might want to use `display: contents` …maybe.
The joy of getting hands-on with HTML and CSS.
If the JavaScript API requires a user gesture, maybe it’s time for a new button type.
Pushing for a share button type—the story so far…
It’s not because it’s declarative—it’s because it’s robust.