storage.googleapis.com - Incorrect movement triggered when tapping/clicking on maze
Categories
(Core :: SVG, defect, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr140 | --- | verified |
| firefox145 | --- | wontfix |
| firefox146 | --- | verified |
| firefox147 | --- | verified |
People
(Reporter: rbucata, Assigned: longsonr)
References
(Regression, )
Details
(Keywords: regression, webcompat:platform-bug, webcompat:site-report, Whiteboard: [webcompat-source:web-bugs], [wptsync upstream])
User Story
platform:windows,mac,linux,android impact:site-broken configuration:general affects:few branch:release diagnosis-team:dom user-impact-score:200
Attachments
(4 files)
|
546.19 KB,
video/mp4
|
Details | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-esr140+
|
Details | Review |
Environment:
Operating system: Linux and Windows 10
Firefox version: Firefox 140.0
Steps to reproduce:
- Navigate to: https://storage.googleapis.com/maze-playground/game.html
- Click on a maze direction and observe
Expected Behavior:
The move is correctly interpreted
Actual Behavior:
The move returned is only up facing direction
Notes:
- Reproduces regardless of the status of ETP
- Reproduces in firefox-nightly, and firefox-release
- Does not reproduce in chrome
Created from https://github.com/webcompat/web-bugs/issues/189202
| Reporter | ||
Updated•2 months ago
|
| Reporter | ||
Comment 1•2 months ago
|
||
Comment 2•2 months ago
|
||
Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.
Comment 3•2 months ago
•
|
||
Regression window:
https://hg-edge.mozilla.org/integration/autoland/pushloghtml?fromchange=f31868a8422c30fcae5963a72cf8ba9ea9b3816a&tochange=afa1bd505415fcb1854f5198fc29ee834c105482
Comment 5•2 months ago
|
||
Set release status flags based on info from the regressing bug 1890198
Comment 6•2 months ago
|
||
:longsonr, since you are the author of the regressor, bug 1890198, could you take a look?
For more information, please visit BugBot documentation.
Updated•2 months ago
|
Updated•2 months ago
|
Updated•2 months ago
|
| Assignee | ||
Comment 7•2 months ago
|
||
The outer frames transform-box is viewBox
xOffset and yOffset are 16 (bp is 960 in all values)
tm is 83, 0, 0, 83, 150, 10 (approx)
There's no rotation here, just scale and translate.
tm.PreTranslate is 83, 0, 0, 83, 1489, 1348
tm.PostTranslate is 83, 0, 0, 83, 166, 26
I think the right thing is probably to go back to the earlier patch I had in bug 1890198. That seems to work in this case.
| Assignee | ||
Comment 8•2 months ago
|
||
Updated•2 months ago
|
| Assignee | ||
Comment 9•2 months ago
|
||
Comment 10•1 month ago
|
||
Comment 12•1 month ago
|
||
| bugherder | ||
Comment 14•1 month 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.
- See https://wiki.mozilla.org/Release_Management/Requesting_an_Uplift for documentation on how to request an uplift.
- If no, please set
status-firefox146towontfix.
For more information, please visit BugBot documentation.
Comment 15•1 month ago
|
||
firefox-beta Uplift Approval Request
- User impact if declined: at least one website doesn't work - see comment 0 in the bug.
- Code covered by automated testing: yes
- Fix verified in Nightly: yes
- Needs manual QE test: yes
- Steps to reproduce for manual QE testing: follow the steps in comment 0 in the bug.
- Risk associated with taking this patch: low
- Explanation of risk level: more closely matches Chrome's behaviour.
- String changes made/needed: none
- Is Android affected?: yes
| Assignee | ||
Comment 16•1 month ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D273465
| Assignee | ||
Updated•1 month ago
|
Updated•1 month ago
|
Updated•1 month ago
|
Updated•1 month ago
|
Comment 17•1 month ago
|
||
| uplift | ||
Updated•1 month ago
|
Updated•1 month ago
|
Comment 18•1 month ago
|
||
Verified fixed using Nightly 147.0a1 (20251127213532) and Beta 146.0b8 (20251126090434) on MacOS 15, Windows 10 and Ubuntu 24.04.
Updated•1 month ago
|
Updated•1 month ago
|
Comment 19•1 month ago
|
||
Should we uplift this to ESR140 also? Please nominate if yes.
Comment 20•1 month ago
|
||
(In reply to Ryan VanderMeulen [:RyanVM] from comment #19)
Should we uplift this to ESR140 also? Please nominate if yes.
| Assignee | ||
Comment 21•1 month ago
|
||
My uplift request failed. I'm afraid I don't know why, or how to fix it. I don't have the ESR cloned and with my current connection it would likely take hours or days to do so.
Comment 22•1 month ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D273465
Updated•1 month ago
|
Comment 23•1 month ago
|
||
I did the esr140 cherry-pick locally and submitted it to Phab. Not sure what happened with the Lando request there. You should be able to link it to the uplift request you already did for Beta by going to https://lando.moz.tools/D277121/ and clicking on the "Link Existing Assessment" button.
Comment 24•1 month ago
|
||
firefox-esr140 Uplift Approval Request
- User impact if declined: website in comment 0 is broken.
- Code covered by automated testing: yes
- Fix verified in Nightly: yes
- Needs manual QE test: yes
- Steps to reproduce for manual QE testing: checkout the website in comment 0 and follow the instructions.
- Risk associated with taking this patch: low
- Explanation of risk level: should get us closer to Chrome's behaviour.
- String changes made/needed: none
- Is Android affected?: yes
| Assignee | ||
Updated•1 month ago
|
Updated•1 month ago
|
Updated•1 month ago
|
Comment 25•1 month ago
|
||
| uplift | ||
Comment 26•11 days ago
|
||
Verified fixed on ESR 140.7.0 (20251219025910).
Description
•