Closed Bug 2000531 Opened 2 months ago Closed 1 month ago

storage.googleapis.com - Incorrect movement triggered when tapping/clicking on maze

Categories

(Core :: SVG, defect, P1)

Desktop
Windows 10
defect

Tracking

()

VERIFIED FIXED
147 Branch
Webcompat Priority P2
Webcompat Score 5
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)

Environment:
Operating system: Linux and Windows 10
Firefox version: Firefox 140.0

Steps to reproduce:

  1. Navigate to: https://storage.googleapis.com/maze-playground/game.html
  2. 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

Attached video Chr vs ff

Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.

The code is here fwiw.

Set release status flags based on info from the regressing bug 1890198

:longsonr, since you are the author of the regressor, bug 1890198, could you take a look?

For more information, please visit BugBot documentation.

Flags: needinfo?(longsonr)
Severity: -- → S4
User Story: (updated)
Webcompat Priority: --- → P2
Webcompat Score: --- → 6
Priority: -- → P1
Webcompat Score: 6 → 5

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.

Flags: needinfo?(longsonr)
Assignee: nobody → longsonr
Status: NEW → ASSIGNED
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/56178 for changes under testing/web-platform/tests
Whiteboard: [webcompat-source:web-bugs] → [webcompat-source:web-bugs], [wptsync upstream]
Status: ASSIGNED → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
Target Milestone: --- → 147 Branch
Upstream PR merged by moz-wptsync-bot

The patch landed in nightly and beta is affected.
:longsonr, is this bug important enough to require an uplift?

For more information, please visit BugBot documentation.

Flags: needinfo?(longsonr)

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
Attachment #9528707 - Flags: approval-mozilla-beta?
Flags: qe-verify+
Flags: needinfo?(longsonr)
Attachment #9528707 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
QA Whiteboard: [uplift][qa-ver-needed-c147/b146]
QA Contact: pmagyari

Verified fixed using Nightly 147.0a1 (20251127213532) and Beta 146.0b8 (20251126090434) on MacOS 15, Windows 10 and Ubuntu 24.04.

QA Whiteboard: [uplift][qa-ver-needed-c147/b146] → [uplift][qa-ver-done-c147/b146]
Component: Site Reports → SVG
Product: Web Compatibility → Core

Should we uplift this to ESR140 also? Please nominate if yes.

Flags: in-testsuite+

(In reply to Ryan VanderMeulen [:RyanVM] from comment #19)

Should we uplift this to ESR140 also? Please nominate if yes.

Flags: needinfo?(longsonr)

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.

Flags: needinfo?(longsonr) → needinfo?(ryanvm)
Attachment #9534107 - Flags: approval-mozilla-esr140?

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.

Flags: needinfo?(ryanvm) → needinfo?(longsonr)

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
Flags: needinfo?(longsonr)
Attachment #9534107 - Flags: approval-mozilla-esr140? → approval-mozilla-esr140+

Verified fixed on ESR 140.7.0 (20251219025910).

Status: RESOLVED → VERIFIED
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: