Interop 2022 did a lot to advance consistent, standards-compliant behavior among browsers. Check out this post for Safari/WebKit results on Interop 2022 (we went from last place to a near-perfect) and looks forward to the even more ambitious Interop 2023. https://webkit.org/blog/13706/interop-2023/
I’m so curious what web designers and developers think about Interop 2023!
What do you think of the new dashboard?
What do you think of the technology that was selected?
What do you think of how Interop 2022 worked out?
Press release: "W3C re-launched as a public-interest non-profit organization"
We continue our core process and mission to shepherd the web, developing open web standards with contributions from W3C Members, staff, and the international community
More at: https://www.w3.org/blog/news/archives/9823
Have you ever heard of `:nth-child(n of <selector>)`?
It’s cool. It lets you count through `:nth` children for items with a particular class (or other selector). Here’s a demo: https://codepen.io/jensimmons/pen/mdjGmem/850199eb0f72fc70492fcfecea6867c9?editors=1100
And you can use `:nth-last-child(n of <selector>)` to count up from the bottom.
It’s been supported in Safari since 2015!
What might you use it for?
Trying out @ivory. Using Mastodon through the web has, UI-wise, felt like using Linux. Crowded layout, too many options. So I haven’t switched from Twitter as much as I’d like. After a few minutes of use, Ivory is much more the experience I’m looking for.
To be clear, I think the problem is in the Mastodon web UI, not the web itself. I happily use Twitter via the web.
Did you know every year on Jan 28 is Data Privacy Day?
To mark the occasion this year, Apple created this video: https://www.youtube.com/watch?v=1HWUjMjaBJI 🤣
Was yesterday’s news about Safari Technology Preview 161 not exciting enough?
Well, now Safari Technology Preview 162 is available!
• CSS Nesting
• CSS Margin Trim
• CSS Relative Color Syntax
• Declarative Shadow DOM
• Form-associated Custom Elements
• Default ARIA for Custom Elements
Look at what Safari Technology Preview 161 includes!
• RegExp lookbehind
• OffscreenCanvas (2D)
• WASM SIMD on x64
• unprefixed Fullscreen API
• CSS Custom Properties (@property)
• CSS Typed OM
• more pseudo-classes work inside :has()
• :user-invalid & :user-valid
• Web Animations improvements
And a *lot* more. Click through to read the whole list!
(Shipped Jan 12; original release notes didn’t list everything.)
Still, it's great that we have such a significant shared body for principles on how the web platform should evolve. And on a higher level, I'd also cite the Ethical Web Principles: https://w3ctag.github.io/ethical-web-principles/
And the Privacy Principles: https://w3ctag.github.io/privacy-principles/
Some of these directly inspired the W3C Technical Architecture Group's Web Platform Design Principles, which are applied when the TAG reviews proposed web standards.
It's more comprehensive, but IMO less well-written - a bit too verbose & bureaucratic.
HTML Design Principles is one of the things I'm most proud of writing (along with co-editor
and its other contributors). Some of these principles have so won the day in web standards that it's hard to believe they were once controversial. For example, there used to be a major constituency _against_ supporting existing web content.
Sometimes I see people making confident claims about the decision-making process inside companies I’ve never worked at, and I have no way to know better so I assume they are right.
Then I see them making confident and totally wrong assertions about how Apple works and make decisions. And I wonder if I should put any stock in the rest of it.
The World Wide Web Consortium (#w3c) is now a real legal entity. https://www.w3.org/blog/2023/01/2023-a-new-era-for-w3c/
engineering at Apple. Also networking APIs. Opinions are personal unless stated otherwise.
QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.