#webcompat — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #webcompat, aggregated by home.social.
-
@drdelle
Direktlink zum Issue im Issue Tracker für #Firefox btw hier: https://bugzilla.mozilla.org/show_bug.cgi?id=2042169Wer den Tech-Lingo nicht versteht: einfach gesagt, man kann die Entwickelnden von Firefox da auf das Problem hinweisen und Tipps/Infos geben und es wird als Problem bearbeitet. Zum Projekt und was das ist, siehe auch: https://webcompat.com/
-
@drdelle
Direktlink zum Issue im Issue Tracker für #Firefox btw hier: https://bugzilla.mozilla.org/show_bug.cgi?id=2042169Wer den Tech-Lingo nicht versteht: einfach gesagt, man kann die Entwickelnden von Firefox da auf das Problem hinweisen und Tipps/Infos geben und es wird als Problem bearbeitet. Zum Projekt und was das ist, siehe auch: https://webcompat.com/
-
Is #Webcompat dead? They have 18k open issues on GitHub. I'm refusing to think that these will be triaged in this lifetime. https://github.com/webcompat/web-bugs/issues
-
Is #Webcompat dead? They have 18k open issues on GitHub. I'm refusing to think that these will be triaged in this lifetime. https://github.com/webcompat/web-bugs/issues
-
Again, unfortunately, I go to use a feature that is apparently now supported in Safari/WebKit (and considered baseline on #MDN), only to discover that one of the features isn’t implemented.
Today’s example? The <dialog> element.
After messing around with it and wondering why clicking the backdrop wasn’t closing it even though closedby="any" was set, I find the closedby attribute isn’t implemented at all 😶
Now I have to add some JS that shouldn’t be needed.
-
Again, unfortunately, I go to use a feature that is apparently now supported in Safari/WebKit (and considered baseline on #MDN), only to discover that one of the features isn’t implemented.
Today’s example? The <dialog> element.
After messing around with it and wondering why clicking the backdrop wasn’t closing it even though closedby="any" was set, I find the closedby attribute isn’t implemented at all 😶
Now I have to add some JS that shouldn’t be needed.
-
Similarly… foiled again.
Me, earlier:
Oh cool, the @ page size descriptor is supported by Chrome, Firefox and Safari! I’ll use it for this print and PDF layout that needs to be A4 landscape.
Me, now, actually trying it:
Wait, why isn’t it working? Oh. Oh no. It does not work at all in Safari. And MDN/caniuse.com say it does, but they are wrong (and there is an open issue about it).
The WebKit bug 63575 is from… 14.5 years ago.
*dies* 💀
-
Similarly… foiled again.
Me, earlier:
Oh cool, the @ page size descriptor is supported by Chrome, Firefox and Safari! I’ll use it for this print and PDF layout that needs to be A4 landscape.
Me, now, actually trying it:
Wait, why isn’t it working? Oh. Oh no. It does not work at all in Safari. And MDN/caniuse.com say it does, but they are wrong (and there is an open issue about it).
The WebKit bug 63575 is from… 14.5 years ago.
*dies* 💀
-
The year is 2026 and again, today, I still need to use a prefixed version of user-select because WebKit still requires it (-webkit-user-select)…
https://bugs.webkit.org/show_bug.cgi?id=208677
There’s a proposal for it in Interop 2026 and I really hope it was selected (the proposal selection process has already been completed, but the results aren’t expected to be published until next month).
-
The year is 2026 and again, today, I still need to use a prefixed version of user-select because WebKit still requires it (-webkit-user-select)…
https://bugs.webkit.org/show_bug.cgi?id=208677
There’s a proposal for it in Interop 2026 and I really hope it was selected (the proposal selection process has already been completed, but the results aren’t expected to be published until next month).
-
Another great new CSS feature that is starting to be available in more browsers is field-sizing, which allows you to size an input to fit its value with:
field-sizing: content;
Great for UI like tags, where you want to be able to type directly into them and have them automatically resize to fit the text.
(#CanIUse shows the feature as not being available in Safari Technology Preview, even though all the individual child features show that it is available)
-
Another great new CSS feature that is starting to be available in more browsers is field-sizing, which allows you to size an input to fit its value with:
field-sizing: content;
Great for UI like tags, where you want to be able to type directly into them and have them automatically resize to fit the text.
(#CanIUse shows the feature as not being available in Safari Technology Preview, even though all the individual child features show that it is available)
-
If you haven’t used it before, image-set() is used in CSS in any place where you’d normally use an image. Here’s a simple example where the browser will use JPEG XL if it supports it, or JPEG if it doesn’t:
background-image: image-set(
url("bg.jxl") type("image/jxl"),
url("bg.jpg") type("image/jpeg")
);( you can also specify resolutions, e.g. url() 2x type() )
-
If you haven’t used it before, image-set() is used in CSS in any place where you’d normally use an image. Here’s a simple example where the browser will use JPEG XL if it supports it, or JPEG if it doesn’t:
background-image: image-set(
url("bg.jxl") type("image/jxl"),
url("bg.jpg") type("image/jpeg")
);( you can also specify resolutions, e.g. url() 2x type() )
-
It’s really nice that we now have wide support for image-set() in browsers so that it’s possible to use JPEG XL in browsers that support it (with automatic fallback to other formats for browsers that don’t), even for cases like background images, which used to be a pain point when all we had was <picture>.
This is an example of the kinds of big wins that can be achieved through the #Interop Project.
-
It’s really nice that we now have wide support for image-set() in browsers so that it’s possible to use JPEG XL in browsers that support it (with automatic fallback to other formats for browsers that don’t), even for cases like background images, which used to be a pain point when all we had was <picture>.
This is an example of the kinds of big wins that can be achieved through the #Interop Project.
-
So we have tel: and mailto: but we don’t have a good cross-platform way to provide address/map links that will use the platform/browser’s preferred maps app/site.
geo: isn’t supported in enough places and probably needs extra features anyway.
It’s obnoxious to have to send everyone to Google Maps, or do sniffing to rewrite links (which is also full of bad assumptions, e.g. change links to Apple Maps on Apple devices, but what if they have the Google Maps app installed?)
-
I wonder if it’s in any way related to this other issue I have with repeating backgrounds and P3 colour on macOS:
-
Here you go, #WebKit people:
https://firewave.com.au/temp/webkit_imagerendering/
image-rendering: pixelated isn’t correctly applied if the element is large enough that the background-image repeats.
-
#gpn23 signup to #micropoc has some kind of web compatibility problem.
When I try to paste my password in Firefox the link popup opens so I effectively cannot register… 🫠🫣
-
#gpn23 signup to #micropoc has some kind of web compatibility problem.
When I try to paste my password in Firefox the link popup opens so I effectively cannot register… 🫠🫣
-
Oh great, the hospital I went for a check-up has a patient portal that was not tested with #Firefox: I cannot open the Doctor's report.
What's the bug? The front-end downloads the PDF as a base64-encoded string and then instructs the browser to navigate to a data: URI.
Problem: Firefox has been blocking this behavior since late 2017: https://blog.mozilla.org/security/2017/11/27/blocking-top-level-navigations-data-urls-firefox-59/
-
Oh great, the hospital I went for a check-up has a patient portal that was not tested with #Firefox: I cannot open the Doctor's report.
What's the bug? The front-end downloads the PDF as a base64-encoded string and then instructs the browser to navigate to a data: URI.
Problem: Firefox has been blocking this behavior since late 2017: https://blog.mozilla.org/security/2017/11/27/blocking-top-level-navigations-data-urls-firefox-59/
-
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?
-
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?
-
JPEG XL didn’t make the cut for this year’s Interop.
It has the most developer interest of any of the proposals for a second year running, but that’s not the way Interop works of course (the vendors decide what’s included and the voting is secret, so we’ll never even know if it had a chance).
Plenty of other great things did make it into Interop 2025 and just because JPEG XL isn’t there it doesn’t mean it won’t be supported (it’s just not a focus area of Interop).
-
I really hope this is the year that JPEG XL makes it into web #Interop
https://github.com/web-platform-tests/interop/issues/700
Given how fundamental image display is for the web, it seems like such an obvious win for websites to have a more bandwidth efficient format, with the killer feature of being able to transcode existing JPEGs with *no quality loss*.
It’s already supported and deployed in #WebKit, and the Rust decoder seems to be progressing well so hopefully it’ll be coming to #Firefox this year.
-
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'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.
#filter #svgFilter #code #coding #web #dev #webCompat #interop #webDev #frontend #webDevelopment
-
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.
#filter #svgFilter #code #coding #web #dev #webCompat #interop #webDev #frontend #webDevelopment
-
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
#Apple #iOS #iOS17 #iOS18 #Safari #HTML5 #SemanticWeb #browsers #bugs #WebCompat
-
`background-clip: text` is now supported cross-browser, unprefixed, in the shorthand.
But there are still bugs/ compat problems.
1️⃣ `p` and `a` within both have `background-clip: text`. Firefox & Chrome produce different results if `a` has a stacking context trigger property‼️
#Firefox #Chrome #webCompat #CSS #code #coding #frontend #web #webDev #webDevelopment #dev
-
😃 Firefox will support macOS’s text replacement feature and the non-standard `autocorrect` attribute and events soon, probably v130.
-
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.
-
@CenturyAvocado The UI / #XUL application frontendof #PaleMoon is based on #Firefox 28 (before #Australis)
The #UXP platform/backend Pale Moon is built to work on is hard forked from the ESR 52 branch of the #Mozilla platform (which is erroneously referred to as the "Firefox platform" no thanks to Mozilla focusing so much on the browser to the detriment of building a sustainable XUL platform for other desktop app developers to use), and has since come a long way when it comes to #webcompat
So "really ancient" can be pretty misleading on the surface.
