#webcompat — Public Fediverse posts

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

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

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.

#WebKit #CSS #WebCompat #Interop

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.

#WebKit #CSS #WebCompat #Interop

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.

#WebKit #CSS #WebCompat #Interop

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.

#WebKit #CSS #WebCompat #Interop

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* 💀

#WebKit #CSS #WebCompat #Interop #MDN #CanIUse

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* 💀

#WebKit #CSS #WebCompat #Interop #MDN #CanIUse

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* 💀

#WebKit #CSS #WebCompat #Interop #MDN #CanIUse

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* 💀

#WebKit #CSS #WebCompat #Interop #MDN #CanIUse

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).

#WebKit #CSS #WebCompat #Interop

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).

#WebKit #CSS #WebCompat #Interop

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).

#WebKit #CSS #WebCompat #Interop

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).

#WebKit #CSS #WebCompat #Interop

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)

#Interop #WebCompat #CSS

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)

#Interop #WebCompat #CSS

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)

#Interop #WebCompat #CSS

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)

#Interop #WebCompat #CSS

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)

#Interop #WebCompat #CSS

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() )

#Interop #WebCompat #JPEGXL

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() )

#Interop #WebCompat #JPEGXL

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() )

#Interop #WebCompat #JPEGXL

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() )

#Interop #WebCompat #JPEGXL

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() )

#Interop #WebCompat #JPEGXL

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.

#WebCompat #JPEGXL

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.

#WebCompat #JPEGXL

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.

#WebCompat #JPEGXL

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.

#WebCompat #JPEGXL

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.

#WebCompat #JPEGXL

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?)

#WebCompat #Interop

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?)

#WebCompat #Interop

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?)

#WebCompat #Interop

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?)

#WebCompat #Interop

I wonder if it’s in any way related to this other issue I have with repeating backgrounds and P3 colour on macOS:

https://firewave.com.au/temp/webkit_svg_p3/

#WebKit #WebCompat

I wonder if it’s in any way related to this other issue I have with repeating backgrounds and P3 colour on macOS:

https://firewave.com.au/temp/webkit_svg_p3/

#WebKit #WebCompat

I wonder if it’s in any way related to this other issue I have with repeating backgrounds and P3 colour on macOS:

https://firewave.com.au/temp/webkit_svg_p3/

#WebKit #WebCompat

I wonder if it’s in any way related to this other issue I have with repeating backgrounds and P3 colour on macOS:

https://firewave.com.au/temp/webkit_svg_p3/

#WebKit #WebCompat

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.

#WebCompat

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.

#WebCompat

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.

#WebCompat

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.

#WebCompat

#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… 🫠🫣

https://github.com/webcompat/web-bugs/issues/162701

@gpn_info #webcompat #webcompatibility

#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… 🫠🫣

https://github.com/webcompat/web-bugs/issues/162701

@gpn_info #webcompat #webcompatibility

#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… 🫠🫣

https://github.com/webcompat/web-bugs/issues/162701

@gpn_info #webcompat #webcompatibility

#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… 🫠🫣

https://github.com/webcompat/web-bugs/issues/162701

@gpn_info #webcompat #webcompatibility

#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… 🫠🫣

https://github.com/webcompat/web-bugs/issues/162701

@gpn_info #webcompat #webcompatibility

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/

#WebDev #Testing #WebCompat