Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] "text-decoration-thickness" wrongly labeled as not supported by Firefox for Android. #5723

Open
Bauda opened this issue Nov 17, 2023 · 1 comment
Labels

Comments

@Bauda
Copy link

Bauda commented Nov 17, 2023

🐞 Bug report

Description

Hello, using the CSS property "text-decoration-thickness" results in a warning about it not being supported by Firefox for Android, which in reality does support it since Jul 2020 (see here).

Details

Here is the complete warning message:

'text-decoration-thickness' is not supported by Firefox for Android.Microsoft Edge Toolscompat-api/css
The text-decoration-thickness CSS property sets the thickness, or width, of the decoration line that is used on text in an element, such as a line-through, underline, or overline.

(Edge 89, Firefox 70, Safari 12, Chrome 89, Opera 75)

Syntax: auto | from-font | |

MDN Reference

@Bauda Bauda added the type:bug label Nov 17, 2023
@Bauda Bauda changed the title [Bug] "text-decoration-thickness" warning as not supported in Firefox for Android. Nov 17, 2023
@bliutech
Copy link

Ditto on this bug. Still experiencing it in v2.1.13.

I did a bit of investigation and it seems that browser compatibility is handled by the package mdn/browser-compat-data. This exact issue with text-decoration-thickness compatibility was fixed in that project by this pull request and was added in v5.5.14. Currently, the latest version of this project uses two versions of the mdn/browser-compat-data library due to an indirect dependency in the package addon-linters. On the latest version of addon-linters, they use the latest version of mdn/browser-compat-data. It is a little bit unclear where in the hint package each dependency version is being used. However, to resolve this issue, I think it is easiest just to bump the version of addon-linters to latest if possible so this updates this indirect dependency.

Not sure if one of the maintainers can comment on whether or not it is possible to get a quick fix to this small issue. Thanks in advance!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2 participants