If anybody moves a #webCompat ticket to backlog because they claim you don't need to support low market share clients, remind them about Amazon Chime.
https://techcrunch.com/2025/02/20/amazon-shuts-down-chime-its-zoom-alternative/
Yes, the probability that Chime supported a particular client was high - but what really matters is for the power users who organize multiple meetings per day, what is the chance that some attendee has a rare client?
And for an IT department supporting lots of meeting organizers, how many rare client issues per day?
I just found the weirdest bug in Safari @webkit
When swapping the class name of two DOM nodes, it tells JavaScript that attribute changed, but the "real" DOM and painted screen don't change, permanently out of sync.
https://treasure21.timotijhof.net/play.html
* Press up twice.
* Press down once.
In Firefox/Chrome, the orange box moves. In Safari, a ghost clone is created!
Isolated test:
https://codepen.io/Krinkle/pen/WbeMPvw?editors=0010
This is quite cool. The Firefox profiler is a very useful tool for diagnosis.
Introducing the Chrome Extension for the Firefox Profiler
https://blog.mozilla.org/performance/2024/12/12/introducing-the-chrome-extension-for-the-firefox-profiler/
I've been toying with #SVG filters a lot lately. If you like this stuff, please vote for them to get more from browsers
https://github.com/web-platform-tests/interop/issues/756
While CSS has progressed a lot lately, SVG got left behind. Filter perf can be abysmal & there are bugs in all browsers, some opened in the 2000s.
Friday Morning.
Last Day at the #w3cTPAC event.
Going back to Tokyo tonight, head full of ideas and cooperation across browsers and websites to advance #webcompat and improve interoperability.
That was great and useful.
Also thanks to the @w3c staff to be, as always, helpful, diligent and kind. Much Love.
The @webkit team you rock too.
NHL broken website on Safari iOS.
If you know someone working on the nhl.com website, please put them in contact with me or point them to https://github.com/webcompat/web-bugs/issues/141887
Does anyone actually use the HTML5 `<time>` tag? Well, I do, and I’ve noticed that Safari’s Reader mode strips this semantic tag entirely.
For example, if you code `<p>iOS 18 was released in <time datetime=“2024-09-16”>2024</time>.</p>`, Reader Mode will render it as, “iOS 18 was released on .”
User agents don’t need to do anything with this tag. The expected behavior is to ignore it and render it as plain text, as if it were never there. Safari handles it correctly, but turn on Reader and you’ll have some missing dates and confused readers.
I filed a bug report. If anyone out there can get Apple’s attention on this super-easy fix, that’d be great. https://feedbackassistant.apple.com/feedback/15162044
This is an opportunity to improve #interop and #webcompat across browsers.
Read carefully the blog post and specifically the section "What Makes a Great Proposal?"
PS: Si vous êtes francophone et que vous aimeriez contribuer mais que vous avez du mal avec l'anglais, je peux vous aider.
https://webkit.org/blog/15942/get-ready-for-interop-2025-your-chance-to-shape-the-web/
`background-clip: text` is now supported cross-browser, unprefixed, in the shorthand.
But there are still bugs/ compat problems.
`p` and `a` within both have `background-clip: text`. Firefox & Chrome produce different results if `a` has a stacking context trigger property
Everybody forgot Internet Explorer. Chrome is the new Internet Explorer. Exhibit
Firefox will support macOS’s text replacement feature and the non-standard `autocorrect` attribute and events soon, probably v130.
Yet another #webcompat day… Outreach or Quirk?
Outreach:
Real fix. Need to find the site owners/engineers. Explain the issue. Hope they care. And wait… wait… wait for the fix (which sometimes never comes). webdevs have their business priorities too. In the meantime the user is having a bad experience.
Quirk:
Hotfixing the website with a hack in the browser engine. The user has right away a better experience.
Usually the right answer is
Quirk and Outreach at the same time!
The first thing I think about is having `position: relative` working on table rows in Safari.
That would help us so much in our work.
if your website is doing content negotiation on JPEG format, do test your website on Safari Technology Preview 192.
JPEG 2000 is being deprecated to align with other browsers.
So sites sending JPEG 2000 to Safari will break in the future.
Example: Safari Release vs STP 192.
Also if you know someone working on #nhl website, please send them to https://github.com/webcompat/web-bugs/issues/135984