android: tjoy.jp - Zoom does not work correctly on seat reservation
Categories
(Web Compatibility :: Site Reports, defect, P1)
Tracking
(Webcompat Priority:P3, Webcompat Score:1)
People
(Reporter: canalun, Assigned: canalun)
References
()
Details
(4 keywords, Whiteboard: [webcompat:japan])
User Story
user-impact-score:0 platform:android impact:workflow-broken configuration:general affects:all branch:release diagnosis-team:layout
Attachments
(1 file)
Environment
147.0a1 (Build #2016129823), 9336a9aece4
GV: 147.0a1-20251203092053
AS: 147.20251202050421
OS: Android 16
Step To Reproduce:
- Access to https://tjoy.jp/shinjuku_wald9#schedule-content
- Scroll down to the list of movies and extend one of them.
- Click any time slot's red button. (It will lead you to the reservation page)
- Tap a right bottom seat.
AR
Zoomed in to the top seat in the left column.
ER
Zoomed in to the tapped seat.
FYI: It's very similar to bug1975653, which is already resolved.
| Assignee | ||
Updated•5 months ago
|
Updated•5 months ago
|
| Assignee | ||
Comment 1•5 months ago
|
||
I'll take a look on it.
| Assignee | ||
Updated•5 months ago
|
Updated•5 months ago
|
Comment 2•5 months ago
|
||
It's unclear if you can actually finish a reservation or not. Let's triage this as workflow-broken for now, but if you can scroll down, it would just be a notable annoyance.
Comment 3•5 months ago
|
||
This is almost certainly caused by:
// Zoom map
$('div.js-map').css({
'zoom': 3,
'-moz-transform': 'scale(3,3)',
'-webkit-transition': 'scale(3,3)',
'transform-origin': 'left top',
});
Emilio/Tom what's the recommended solution to zoom + -moz-transform these days?
Updated•5 months ago
|
Updated•5 months ago
|
Comment 4•5 months ago
|
||
An intervention with .js-map { -moz-transform: none !important } seems like it'd do.
| Assignee | ||
Comment 5•5 months ago
•
|
||
Sorry I couldn't take time. Thank you all for investigation.
I confirmed Emilio's solution worked by injecting the style sheet via devtools on Android :)
Is it alright for me to implement the intervention?
Updated•5 months ago
|
| Assignee | ||
Comment 6•5 months ago
•
|
||
to [:denschub]
It's unclear if you can actually finish a reservation or not. Let's triage this as workflow-broken for now, but if you can scroll down, it would just be a notable annoyance.
A reservation can be finished, so it's a notable annoyance.
And I wrote a site-patch and test. Could you please review it? If alright, I will submit the patch.
| Assignee | ||
Comment 7•5 months ago
|
||
Comment 8•5 months ago
|
||
Tom reviewed this, canceling my ni? Thanks for your work! :)
Comment 10•5 months ago
|
||
Was this canalun's patch that got landed? Maybe the author got clobbered when it was rebased?
Comment 11•5 months ago
|
||
Ouch, yes, it might have been because I had to rebase the patch to my stack, to spare canalun the effort. Apologies, I fully intend to give canalun the credit here! (It seems weird that I reviewed my own patch, after all).
Comment 12•5 months ago
•
|
||
Thanks, that's understandable. Not sure if we normally do a backout and relanding for an incorrect author like we do for an incorrect bug number.
| Assignee | ||
Comment 13•5 months ago
|
||
Thank you, Thomas and Brian. I'd really appreciate it if we could correct the author info if possible :)
If there is anything I can do to help, please let me know.
Comment 14•5 months ago
|
||
Sounds like all we can do is back it out, and let canalun land it himself. I've asked for the patch to be backed out so canalun can alter it to add a version number, and re-land it when he's back.
Comment 15•5 months ago
|
||
Updated•5 months ago
|
Comment 16•5 months ago
|
||
:canalun, I'm afraid I'll have to ask you to rebase your patch once the rest of my stack lands, as it will need to bump the version number of the addon's manifest (which ought to be 148.2.0 after my stack lands, and you can bump it to 148.3.0 and land your final patch).
Sorry for the mix-up!
Comment 17•5 months ago
|
||
I mean, lando preserves committer information so another option is to just pull the patch, git amend it with the right author info, and re-land...
Comment 18•5 months ago
|
||
We still should bump the version number, or the addon might not be updated properly in the next nightly.
| Assignee | ||
Comment 19•5 months ago
|
||
:twisniewski
no problem, thank you so much for reverting the patch :)
I got it. I'd appreciate it if you could kindly let me know when your stack lands and everything gets ready.
Comment 20•5 months ago
|
||
The rest of the stack has landed, so feel free to rebase and bump to 148.3.0 and re-land yours :)
| Assignee | ||
Comment 21•4 months ago
|
||
:twisniewski
Thanks! I bumped the version to 148.3.0 and the author has been successfully changed.
But I noticed I don't have the permission to land the patch.
So, could you please kindly land it when you have time?
Comment 23•4 months ago
|
||
Comment 24•4 months ago
|
||
| bugherder | ||
Updated•4 months ago
|
Updated•4 months ago
|
Updated•3 months ago
|
Description
•