Distortion while a checkbox animates on https://farbvelo.elastiq.ch/
Categories
(Core :: SVG, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox-esr128 | --- | unaffected |
firefox128 | --- | unaffected |
firefox129 | + | wontfix |
firefox130 | + | wontfix |
firefox131 | + | fixed |
People
(Reporter: mayankleoboy1, Assigned: longsonr)
References
(Regression, )
Details
(Keywords: regression)
Attachments
(3 files)
Go to https://farbvelo.elastiq.ch/
Click on the gear icon on the bottom
A settings pane will open.
Scroll down a bit on this pane. There will be some options with checkboxes
Click on a checkbox
AR: While the checkbox animates, there is a distortion in the rendering
ER: Not so
Suspects: bug 1714763 and bug 1836693
cc :tnikkel
Reporter | ||
Comment 1•2 months ago
|
||
Reporter | ||
Comment 2•2 months ago
|
||
Comment 3•2 months ago
|
||
I have a cached build of https://hg.mozilla.org/mozilla-central/rev/d588d40904f7880592d27c083cb64d31864340cb that I tested that was "good", so that probably means it was my bug in that range.
Interestingly, I can reproduce on nightly, but not on beta builds. Can you reproduce on any non-nightly build? I wonder if some differences on nightly that expose this?
Comment 4•2 months ago
•
|
||
I can reproduce the issue on Firefox129.0rc1 Windows11.
Click on the disabled checkbox Color Bleed
. then black rectangle is rendered until mouse move over color bar.
Regression window in mozilla-beta:
https://hg.mozilla.org/releases/mozilla-beta/pushloghtml?fromchange=69f421f0aa2c1c8241d09309b4950a94ba2faec7&tochange=556215a082ccfb6f6b7c35c0e263e9fe585c318c
Regression window in mozilla-central:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=e3cdd7bcd89ea80b3b400729e3a89b103e3c464c&tochange=a11e8418e383e89972a8546e6400f424b84a2ac5
Regressed by: Bug 1903546 - fix non-scaling-stroke
Reporter | ||
Comment 5•2 months ago
|
||
Maybe there are 2 bugs here?
Comment 6•2 months ago
|
||
(In reply to Mayank Bansal from comment #5)
Maybe there are 2 bugs here?
That is what I am also thinking might be happening here.
Comment 7•2 months ago
|
||
Set release status flags based on info from the regressing bug 1903546
:longsonr, since you are the author of the regressor, bug 1903546, could you take a look?
For more information, please visit BugBot documentation.
Comment hidden (obsolete) |
Assignee | ||
Comment 9•2 months ago
|
||
actually mozregression shows Firefox 115 is OK.
Comment 10•2 months ago
|
||
The first regression was caused by Bug 1714763 and Bug 1836693. It was then fixed by Bug 1898409.
However, a second regression was again caused by Bug 1903546.
(In reply to Robert Longson [:longsonr] from comment #9)
actually mozregression shows Firefox 115 is OK.
Yes, Firefox 115 is OK, works fine for me.
Comment 11•2 months ago
|
||
(In reply to Alice0775 White from comment #10)
The first regression was caused by Bug 1714763 and Bug 1836693. It was then fixed by Bug 1898409.
However, a second regression was again caused by Bug 1903546.
So sounds like the root cause is probably bug 1714763 then?
Assignee | ||
Comment 12•2 months ago
|
||
Assignee | ||
Updated•2 months ago
|
Assignee | ||
Comment 13•2 months ago
|
||
Assignee | ||
Comment 14•2 months ago
|
||
Comment 15•2 months ago
|
||
Comment 17•2 months ago
|
||
Backed out for causing dt failures on browser_inspector_highlighter-cssshape_offset-path.js
Reporter | ||
Comment 18•2 months ago
|
||
Can confirm that the autoland build fixes this bug for me.
Comment 20•2 months ago
|
||
Set release status flags based on info from the regressing bug 1903546
Comment 21•2 months ago
|
||
Tentatively triaging as S2 given this is a recent regression that we shouldn't lose track of (particularly given that we've got a patch that was just backed out for regressing one automated test; hopefully it's not too hairy to untangle that).
Assignee | ||
Comment 22•2 months ago
|
||
Unfortunately the patch doesn't make us compatible with Chrome.
- Chrome (and Firefox without this patch) takes the outer svg viewBox into account with non-scaling-stroke. The current patch would exclude it.
<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" viewBox="-20 -20 50 50" width="100%" height="100%">
<rect width="10" height="10" stroke="lime" stroke-width="10" vector-effect="non-scaling-stroke" />
</svg>
The above SVG displays the same in Chrome and Firefox currently but would display all lime with the current patch.
What Chrome seems to do is ignore any transform on the outer SVG element.
Updated•2 months ago
|
Assignee | ||
Comment 23•2 months ago
|
||
Assignee | ||
Comment 24•2 months ago
|
||
Looks like that makes the existing test pass too.
Comment 25•2 months ago
|
||
Comment 26•2 months ago
|
||
bugherder |
Comment 28•2 months ago
|
||
The patch landed in nightly and beta is affected.
:longsonr, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox130
towontfix
.
For more information, please visit BugBot documentation.
Assignee | ||
Updated•2 months ago
|
Comment 29•2 months ago
|
||
I'm a bit confused about this being set to wontfix for 130 given it being rated S2 severity and tracking+ for Fx130. Is it your opinion that this bug isn't as severe as originally thought to be?
Comment 30•2 months ago
•
|
||
I may've been off slightly by rating it S2; mostly wanted to be sure it didn't fall off the radar, since it was a regression with a nearly-landable patch.
Given that this bug was cosmetic (not site breaking), and we shipped the bug already in 129, and automated test coverage is somewhat lacking for non-scaling-stroke edge cases (meaning there's nonzero risk of regressions): I think wontfix for beta130 is the right call.
Assignee | ||
Comment 31•2 months ago
•
|
||
We've not had any duplicates as far as I can tell. You need a non-scaling-stroke on a shape where there is an outer <svg> element that has a transform so it's not going to be that common. Until recently neither Chrome nor Safari supported transforms on <svg> elements so that's why such content is pretty rare.
Description
•