Closed Bug 1895896 Opened 24 days ago Closed 23 days ago

Perma /css/css-content/parsing/content-computed.html | Property content value 'open-quote / "alt text"' - assert_true: 'open-quote / "alt text"' is a supported value for content. expected true got false when Gecko 127 merges to beta on 2024-05-13

Categories

(Core :: CSS Parsing and Computation, defect)

defect

Tracking

()

VERIFIED FIXED
127 Branch
Tracking Status
firefox-esr115 --- unaffected
firefox125 --- unaffected
firefox126 --- unaffected
firefox127 + verified

People

(Reporter: acseh, Assigned: emilio)

References

(Regression)

Details

(Keywords: regression)

Central-as-beta simulation
How to run these simulations
Failure log:

[task 2024-05-09T12:20:25.486Z] 12:20:25     INFO - TEST-PASS | /css/css-content/parsing/content-computed.html | Property content value 'open-quote' 
[task 2024-05-09T12:20:25.486Z] 12:20:25     INFO - TEST-UNEXPECTED-FAIL | /css/css-content/parsing/content-computed.html | Property content value 'open-quote / "alt text"' - assert_true: 'open-quote / "alt text"' is a supported value for content. expected true got false
[task 2024-05-09T12:20:25.486Z] 12:20:25     INFO - test_computed_value/<@http://web-platform.test:8000/css/support/computed-testcommon.js:25:16
[task 2024-05-09T12:20:25.486Z] 12:20:25     INFO - Test.prototype.step@http://web-platform.test:8000/resources/testharness.js:2622:25
[task 2024-05-09T12:20:25.486Z] 12:20:25     INFO - test@http://web-platform.test:8000/resources/testharness.js:633:30
[task 2024-05-09T12:20:25.486Z] 12:20:25     INFO - test_computed_value@http://web-platform.test:8000/css/support/computed-testcommon.js:22:7
[task 2024-05-09T12:20:25.486Z] 12:20:25     INFO - test_computed_value_combinations@http://web-platform.test:8000/css/css-content/parsing/content-computed.html:21:24
[task 2024-05-09T12:20:25.486Z] 12:20:25     INFO - @http://web-platform.test:8000/css/css-content/parsing/content-computed.html:24:33
[task 2024-05-09T12:20:25.487Z] 12:20:25     INFO - 
[task 2024-05-09T12:20:25.487Z] 12:20:25     INFO - TEST-PASS | /css/css-content/parsing/content-computed.html | Property content value 'close-quote' 
Flags: needinfo?(emilio.alvarez96)

Wrong Emilio?

Flags: needinfo?(emilio.alvarez96) → needinfo?(emilio)
Pushed by emilio@crisal.io:
https://hg.mozilla.org/integration/autoland/rev/5318a409a162
Turn on content alt text pref on css-content tests.
Flags: needinfo?(emilio)

The patch was tested in today's central as early beta simulation and it seems to be working.

Type: task → defect
Type: task → defect

(Odd; I tried to reclassify this as a task since this is just a test manifest tweak with no user-facing impact, but Bugzilla seems to reject that change, and confusingly shows me as having made the opposite change. I'm going to try one more time, for the benefit of a screencast that I can attach to a bug report that I'll submit for b.m.o, and then I'll stop poking here; sorry for the noise. :) ) [edit: filed this as bug 1896204]

Type: task → defect

(In reply to Daniel Holbert [:dholbert] from comment #4)

(Odd; I tried to reclassify this as a task since this is just a test manifest tweak with no user-facing impact, but Bugzilla seems to reject that change, and confusingly shows me as having made the opposite change. I'm going to try one more time, for the benefit of a screencast that I can attach to a bug report that I'll submit for b.m.o, and then I'll stop poking here; sorry for the noise. :) )

It's flagged as a regression, bugzilla won't allow regressions to be tasks.
The only way to convert to a task is to clear the regressor and the regression keyword (though that would lose tracking so it's not recommended)

(In reply to Donal Meehan [:dmeehan] from comment #5)

It's flagged as a regression, bugzilla won't allow regressions to be tasks.

Thanks - I suspected that might be it. The way-it-doesn't-allow-this could definitely be made less perplexing; hence, filed bug 1896204. :)

The only way to convert to a task is to clear the regressor and the regression keyword (though that would lose tracking so it's not recommended)

Yeah. I'm not sure what the right solution is, but ideally we'd have some way to let bugdash not-include bugs like this in its lists of "real" user-facing regressions, to avoid adding noise to what are otherwise high-signal bug lists. (I happened to notice this bug since it was (for the moment) on bugdash under "127 (Nightly) New Regressions" in the "Important" tab. Definitely worth getting this addressed [and we did, hooray!] to avoid perma-orange when 127 hits beta -- but it feels like it's in a different category from "real" regressions where users are potentially hitting site breakage.)

Status: NEW → RESOLVED
Closed: 23 days ago
Resolution: --- → FIXED
Target Milestone: --- → 127 Branch
Assignee: nobody → emilio
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.