Closed Bug 2039630 Opened 1 month ago Closed 1 month ago

Perma /css/css-text-decor/text-emphasis-position-property-003.html | when Gecko 152 switches to Beta on 2026-05-18

Categories

(Core :: Layout, defect)

Product:
Core
Component:
Layout
Type:
defect

Tracking

()

Status:
VERIFIED FIXED
Milestone:
153 Branch
Tracking Flags:
Tracking Status
thunderbird_esr140 --- unaffected
firefox-esr115 --- unaffected
firefox-esr140 --- unaffected
firefox150 --- unaffected
firefox151 --- unaffected
firefox152 + fixed
firefox153 + verified

People

(Reporter: asilaghi, Assigned: jfkthame)

References

(Regression)

Details

(Keywords: regression)

Summary: Pemra /css/css-text-decor/text-emphasis-position-property-003.html | when Gecko 152 switches to Late Beta on 2026-05-29 → Perma /css/css-text-decor/text-emphasis-position-property-003.html | when Gecko 152 switches to Late Beta on 2026-05-29

:jjaschke, since you are the author of the regressor, bug 2017940, could you take a look? Also, could you set the severity field?

For more information, please visit BugBot documentation.

Flags: needinfo?(jjaschke)

Looking into it. It's unclear to me why that only shows up in Beta, not in Nightly?

Looking at wpt.fyi, it seems that all these failing tests also fail in Chrome and Safari.

If I understand correctly, my changes in bug 2017940 change the behavior of the reference file, not the test itself. The reftest analyzer results of the try push now show the inverse of Chrome's behavior on wpt.fyi. I don't know what the expected behavior should be here.

Jonathan, could you bring some light into this? How much value do these tests actually have?

Flags: needinfo?(jjaschke) → needinfo?(jfkthame)
Summary: Perma /css/css-text-decor/text-emphasis-position-property-003.html | when Gecko 152 switches to Late Beta on 2026-05-29 → Perma /css/css-text-decor/text-emphasis-position-property-003.html | when Gecko 152 switches to Beta on 2026-05-18

This is probably related to the layout.css.ruby.normalize-metrics-factor pref, which is currently only set to a non-zero value (100) by default on Nightly. I think we should ungate that and let it ride the train to Beta and Release.

Flags: needinfo?(jfkthame)
Depends on: 2040139
Assignee: nobody → jfkthame
Status: NEW → RESOLVED
Closed: 1 month ago
status-firefox152: affected → fixed
status-firefox153: --- → fixed
tracking-firefox153: --- → +
Resolution: --- → FIXED
Target Milestone: --- → 153 Branch

Verified fixed in today’s beta simulation push.

Status: RESOLVED → VERIFIED
status-firefox153: fixed → verified
You need to log in before you can comment on or make changes to this bug.