Closed Bug 729149 Opened 12 years ago Closed 12 years ago
Browser Quest: Double clicking with canvas causes zooming
When trying to play the game, clicking quickly leads to a double quick that does reflow/zoom behavior. It's either up to the game to catch these events or up to the front end to disable this behavior on canvas element?
The game use user-scalable=no: <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1.0, user-scalable=no"> A double click should not be resizing the game. See bug 707571
preventDefault on touchdown should also prevent this. Is that happening Paul? I think there is a race somewhere in the touch event->preventPanning code that we lose sometimes, but I haven't been able to track it down. Or its possible the demo is only calling preventDefault on touchmove which never fires?
We don't preventDefault on touchdown (touchstart?). I can do that.
Whoops. Yep, touchstart. Like I said, I think I have seen that fail. I can invest some time this afternoon if its a priority.
(In reply to Wesley Johnston (:wesj) from comment #4) > Whoops. Yep, touchstart. > > Like I said, I think I have seen that fail. I can invest some time this afternoon if its a priority. I'll make some tests tomorrow and let you know.
I also don't see any monsters outside of the town while the rats in town do load. I can walk all the way to the final boss without getting attack so I imagine it's not a platform canvas bug otherwise if the monster were there the character would get killed. Any idea where that bug is?
Summary: Double clicking with canvas causes zooming → Browser Quest: Double clicking with canvas causes zooming
Is this maple-specific?
Assignee: nobody → paul
Whiteboard: MAPLE mwc-demo
This works for me using the current Maple tinderbox and Nightly.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
I can kinda duplicate the issue by placing the device in landscape, but it doesn't reflow much and it doesn't seem to harm anything.
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.