Closed Bug 1411063 Opened 7 years ago Closed 6 years ago

touchscreen zooming behavior must be changed because some elements get cut off

Categories

(Core :: Panning and Zooming, defect, P3)

All
Android
defect

Tracking

()

RESOLVED DUPLICATE of bug 656036
mozilla63
Tracking Status
platform-rel --- ?
fennec + ---
firefox57 --- affected
firefox58 --- affected

People

(Reporter: billdillensrevenge, Unassigned)

Details

(Whiteboard: [gfx-noted])

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0
Build ID: 20170926190823

Steps to reproduce:

get an Android phone, open Firefox and go to justgetflux.com . Notice in the top-right corner there is "Forum Blog Research FAQ" sections . Now, zoom in the page. These sections are now out of view and scrolling/panning over doesn't reveal them! The only way to see them again is to zoom out. I think this behavior should be changed to what Chrome for Android and Safari for iPhone do: simply zoom in
Status: UNCONFIRMED → NEW
tracking-fennec: --- → ?
Ever confirmed: true
OS: Unspecified → Android
Hardware: Unspecified → All
Version: 56 Branch → Trunk
This is webcompat or platform, not related to Fennec front-end.
tracking-fennec: ? → ---
platform-rel: --- → ?
Flags: webcompat?
Flags: needinfo?(dbolter)
Hi Botond, can you triage this one further? Seems like a "viewport compatibility" bug/feature.
Flags: needinfo?(dbolter) → needinfo?(botond)
This is caused by Firefox's treatment of position:fixed elements during zooming. Bug 656036 tracks a fix for issues like this.
Depends on: 656036
Flags: needinfo?(botond)
Component: General → Panning and Zooming
Priority: -- → P3
Product: Firefox for Android → Core
Whiteboard: [gfx-noted]
tracking-fennec: ? → +
I just wanted to add, I didn't mean to title this bug "touchscreen scrolling...", I meant to write "touchscreen zooming..."
Summary: touchscreen scrolling behavior must be changed because some elements get cut off → touchscreen zooming behavior must be changed because some elements get cut off
This was fixed by bug 656036.
Status: NEW → RESOLVED
Closed: 6 years ago
No longer depends on: 656036
Resolution: --- → DUPLICATE
Target Milestone: --- → mozilla63
You need to log in before you can comment on or make changes to this bug.