#interop2025 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #interop2025, aggregated by home.social.
-
Interop 2025 : les navigateurs web progressent main dans la main http://dlvr.it/TQrc7F #Interop2025 #NavigateursWeb
-
Interop 2025 : les navigateurs web progressent main dans la main http://dlvr.it/TQrc7F #Interop2025 #NavigateursWeb
-
Interop 2025 : les navigateurs web progressent main dans la main http://dlvr.it/TQrc7F #Interop2025 #NavigateursWeb
-
Interop 2025 : les navigateurs web progressent main dans la main http://dlvr.it/TQrc7F #Interop2025 #NavigateursWeb
-
Interop 2025 : les navigateurs web progressent main dans la main http://dlvr.it/TQrc7F #Interop2025 #NavigateursWeb
-
#Chrome and #Firefox need to support margin-trim, like… yesterday.
It makes things sooooo much easier. A single property applied to the container, rather than stuffing around with multiple :first-child and :last-child rules to try to create the right behaviour.
It’s a shame it didn't make it into #Interop2025 because it’s such a useful property and elegantly deals with a layout situation that occurs all the time.
-
Pleased to be sneaking some #ProgressiveEnhancement into the #DesignSystem we're building at Investec.
Currently making an Accordion component using #HTML <details> & < summary>, which requires zero client-side #JS. Until #interop2025 brings ::details-content support to Firefox & Safari, the opening / closing won't be animated in those browsers. But, we're cool with that. It's still perfectly usable without animations.
-
Mal wieder Neues aus dem #Frontend
Im Chrome Canary gibt's eine erste Umsetzung der #CSS Mixins Spec – CSS Custom Functions:
https://www.bram.us/2025/02/09/css-custom-functions-teaser/Die Fokus-Bereiche für #interop2025 stehen fest und es sind einige spannende Dinge dabei, z.B. #CoreWebVitals , Anchor Positioning, das <details>-Element und Flexbox & Grid/Subgrid:
https://www.webkit.org/blog/16458/announcing-interop-2025/CSS text-box-trim findet Verbreitung: Chromium 133+ und Safari 18.2 sind jetzt dabei:
https://developer.chrome.com/blog/css-text-box-trim -
#CSS things I'm excited about re: #interop2025 — https://github.com/web-platform-tests/interop/blob/main/2025/README.md
- Anchor Positioning!
- `@scope`!
- `text-decoration`! Although… It is a bit sad that this focus area contains only 16 tests with 169 subtests out of… 309 tests and 1201 subtests in the css-text-decor folder: https://wpt.fyi/results/css/css-text-decor — ok, maybe we could exclude text-emphasis for now, but there are much more text-decoration-… tests, and the interop of text-underline-… is not there yet as well. -
Happy #Interop2025 day to all who celebrate!
-
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 -
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 -
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 -
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 -
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 -
Folowing on from @sil talk at #SotB2024 check out these github issues an vote for them if you feel inclined #OWA #interop2025
https://open-web-advocacy.org/blog/interop-2025-must-drop-secret-vetos/
-
I strongly recommend you review the Interop 2025 focus area proposals [1] but go beyond that and follow the raised bugs on each platform’s tracker and engage with them as they develop.
Even if they don’t make the cut, you can help them garner extra interest and support their direction outside of Interop.
[1]: https://github.com/web-platform-tests/interop/labels/focus-area-proposal
-
I submitted a proposal for Responsive Tables to the Interop 2025 project: https://github.com/web-platform-tests/interop/issues/741
Maybe that’s not the best place for it, and maybe it’s out of scope for Interop, but maybe it can start a conversation for what is imo a needed feature.
-
**Submit your proposals for Interop 2025**
https://web.dev/blog/interop2025-proposals?hl=en
My favs so far:
• Navigation API: https://github.com/web-platform-tests/interop/issues/709
• Web Share API: https://github.com/web-platform-tests/interop/issues/711
• Vibration API: https://github.com/web-platform-tests/interop/issues/718
• Fullscreen API: https://github.com/web-platform-tests/interop/issues/732
• Notifications API: https://github.com/web-platform-tests/interop/issues/737 ** shameless self-promotion :)
-
@Meyerweb @kizu I should add that to #Interop2025 because partial support is harmful.
-
If no one else would submit `::first-letter` and `initial-letter` to #Interop2025, I will.
-
Browsers still haven’t fixed the CSS overscroll-behavior property
https://github.com/whatwg/html/issues/7732#issuecomment-2154195226
-
We really need to gather various #typography related #CSS properties that are scattered across different browsers without full support (or with just partial support) and make it into an #interop2025 focus area.
Like `ascent-override` (please, Safari!)
Or `font-size-adjust` (come on, Chrome!)
Or… `initial-letter` (hey, Firefox!), though, there are also so many `::first-letter` issues!
Or `text-box-trim` & `text-box-edge` (ok, these are only there in Safari TP)
And so on, and so forth.
-
CSS text-underline-offset and text-decoration-thickness #Interop2025
-
@brucelawson This fixes it for me in Firefox:
#logo a {
display: block;
width: fit-content;
}#logo img {
display: block;
} -
@simevidas @db
Also, `document.activeElement` is handy but doesn't always tell the truth. In Chrome, even though it says focus is on the <body>, if you press Tab, you'll likely find that focus does not move to the first focusable element (your Skip link) but to the next focusable element after the link you had clicked.Regardless, I'd like to see correctly moving focus to the destination of in-page links without having to add tabindex="-1" to those destinations in #Interop2025
-
> Safari. The DPR is fixed
So if the website provides ultra-high-density image sources, and the user zooms the page, Safari won’t use those sources, even after page reload. In other words, at high page zoom levels, images on some websites will be noticeably blurrier in Safari than in Chrome and Firefox. That sounds like a bug to me.
-
@AmeliaBR @boldewyn @sarajw We should probably propose it for #Interop2025, so that we don’t have to wait five years for it to be implemented in all browsers.
-
While focusing on keyboard navigation in our design system, i keep noticing that Safari often behaves quite differently from Chrome.
For example Safari skips all the links in the "Top Repositories" on the GitHub main page, while Chrome doesn’t. Or on a repositories' PR page, Safari skips the tabs at the top while Chrome doesn’t.
Is there a reason for this? Or a good example for #interop2025 ? #safari #webkit -
@bkardell I’ve been posting my biggest wishes under the #Interop2025 hashtag
-
@kizu There is a proposal at https://github.com/web-platform-tests/interop/issues/520. If it’s not chosen for 2024, and for all other multicol issues, we have to remember to submit if for #Interop2025.
