1982904 - wpt reftest: css/css-fonts/font-variation-settings-descriptor-04.html fails on new android 14 emulator

Status: NEW

(Core :: Layout: Text and Fonts, defect)

Description

[Joel Maher ( :jmaher ) (UTC -8)]

as seen here on try:
https://treeherder.mozilla.org/jobs?repo=try&selectedTaskRun=fT3bkaCfRCWsvDxmU12J2g.0&tier=1%2C2%2C3&revision=fdea14904f15d8fe3a01e1277a1ad60054bf5e8e&test_paths=%2Fcss%2Fcss-fonts&searchStr=wr1

you can look at the reftest compare and the text is bolder on the reference image, but not on the test image.

Comment 1

[Joel Maher ( :jmaher ) (UTC -8)]

in addition (same try link/job):

• css/css-fonts/system-ui-mixed.html (the left characters are bolded on the reference image. also the entire line seems shifted down)

Comment 2

[Joel Maher ( :jmaher ) (UTC -8)]

related to this same component is

• css/css-text-decor/text-emphasis-style-002.html
• css/css-text-decor/text-emphasis-style-016.html

both of these render fine, but there is a row of . and the ending . has some fuzzy issues.

you can see this in:
https://treeherder.mozilla.org/jobs?repo=try&tier=1%2C2%2C3&revision=fdea14904f15d8fe3a01e1277a1ad60054bf5e8e&test_paths=%2Fcss%2Fcss-text-decor&searchStr=wr4&selectedTaskRun=SNqjjN_XR1CN32UpLQTU1A.0

and the reftest-compare:
https://hg-edge.mozilla.org/mozilla-central/raw-file/default/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/SNqjjN_XR1CN32UpLQTU1A/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1

Comment 3

[Jamie Nicol [:jnicol]]

Jonathan, re system-ui-mixed.html:

I looked into this last week and it appeared to regress sometime between android 7 and 11.

I notice the test has font-family: serif; whereas the reference has font-family: sans-serif;. Is that deliberate?

On Android 7, we end up using NotoSansCJK-Regular.ttc for both cases. Whereas on Android 11 we use NotoSerifCJK-Regular.ttc and NotoSansCJK-Regular.ttc respectively.

So somewhere between android 7 and 11 the a serif CJK font was added, causing the test to fail? Should we be using either consistently serif or sans-serif in both the test and reference?

Comment 4

[Jonathan Kew [:jfkthame]]

No, IIRC this was quite deliberate: the idea being that if system-ui works appropriately for all the content, the fallback (serif or sans-serif) will not be used at all, and so the test and reference files will match. If they're not matching, that implies that system-ui didn't handle everything as expected.

It looks like our implementation of system-ui on Android doesn't cover the CJK characters, so in a sense we've always been "failing" that, but the test didn't catch it because we also didn't have distinct serif vs sans-serif mappings. Now that those exist, the test is revealing the limitations of system-ui as it was intended to do.

So I think it'd be appropriate to annotate this as an expected failure, and file a bug to the effect that system-ui on Android doesn't support CJK content. (We already fail similarly on other platforms, fwiw.)

Comment 5

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:jwatt, could you have a look please?

For more information, please visit BugBot documentation.