You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that Firefox (and maybe Chrome?) implement the initial value of text-underline-position in a way that's sensitive to the language, and interprets it as right for Japanese and Korean.
This is currently not allowed per spec; instead the spec has UA rules that set the behavior per language.
Do we want to
Update the definition of auto to match Firefox?
Or update implementations to match the spec?
The text was updated successfully, but these errors were encountered:
It seems that Firefox (and maybe Chrome?) implement the initial value of text-underline-position in a way that's sensitive to the language, and interprets it as right for Japanese and Korean.
This is currently not allowed per spec; instead the spec has UA rules that set the behavior per language.
It seems that Firefox (and maybe Chrome?) implement the initial value of
text-underline-position
in a way that's sensitive to the language, and interprets it asright
for Japanese and Korean.This is currently not allowed per spec; instead the spec has UA rules that set the behavior per language.
Do we want to
auto
to match Firefox?The text was updated successfully, but these errors were encountered: