New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 676368 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

position:fixed not fixed in device mode when fixed height and body width > 100vw

Reported by bertrand...@gmail.com, Dec 21 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36

Steps to reproduce the problem:
1. Have a DOM element with `position: fixed` in a body that has a fixed height and a body width greater than 100vw.

Here’s an example : http://jsbin.com/rexebamomo/edit?html,css

2. Open the device toolbar, pick any device, refresh the page.

3. The fixed element will be scrolling as if it was absolutely positioned.

What is the expected behavior?
Fixed elements should remain fixed elements.

It’s behaving correctly in chrome (outside of the device tools)

What went wrong?
http://output.jsbin.com/rexebamomo

Did this work before? Yes 

Chrome version: 55.0.2883.95  Channel: stable
OS Version: OS X 10.12.1
Flash Version: Shockwave Flash 24.0 r0
 
Labels: M-55 Needs-Bisect
Cc: ranjitkan@chromium.org
Labels: Needs-Feedback
Could you please explain us what is happening or what went wrong. Currently we are not clear what is the actual behavior, A screen cast will be very helpful

Thanks.!
Hey,

Here’s a screen cast: https://youtu.be/PIDc3efCyMc

And here’s the source of the page: https://gist.github.com/tusbar/563109db3cfa83d2702ecd7bd8d89725

I hope it helps.
Cc: kkaluri@chromium.org
Labels: -M-55 -Needs-Feedback -Needs-Bisect M-57 hasbisect OS-Linux OS-Windows
Owner: erikc...@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce this issue on Windows 10, Ubuntu 14.04 and Mac 10.12.2 on chrome stable version 55.0.2883.87 and also in current canary version #57.0.2962.0
Issue is broken in M47. 

Bisect Info:
==========
Good build : 47.0.2501.0,  Revision Range -347299
Bad build  : 47.0.2502.0,  Revision Range -347539

After executing the (old)bisect script, i got the following CL's between good and bad build versions
===================================================
https://chromium.googlesource.com/chromium/src/+log/e043c0711a789da1046912c6a75bb1f52812d29e..8a8f456d5916917035b7b4e8bb64182c1c473758

The suspecting Change Log is :
-----------
https://chromium.googlesource.com/chromium/src/+/0bc400e1c96da5a05379bc1b634ec278f36d3417

From the above CL suspecting the below change
---------------------------
Review URL: https://codereview.chromium.org/1307203006

erikchen@- Could you please look into this issue, if it's related to your change?  if not could you please help us to reassign this issue to the right owner.

Components: -Platform>DevTools Blink
Owner: ----
Status: Untriaged (was: Assigned)
Components: Platform>DevTools
Components: -Blink Blink>Paint
Labels: -OS-Linux -OS-Windows -OS-Mac OS-All
I can't reproduce this in M-56 beta on Mac nor M-57 Canary on Mac, using the jsbin provided. I tried refreshing the page with DevTools open in device mode and it worked fine.

Any idea what I'm missing? Otherwise I'll try some other platforms when I next can.


Labels: -hasbisect Needs-Bisect
Status: Available (was: Untriaged)
I can reproduce on 57.0.2950.4 / Mac with the test file at https://gist.github.com/tusbar/563109db3cfa83d2702ecd7bd8d89725.
It appears to only happen in devtools emulation mode, not on a real mobile device.

The bisect is wrong, please redo the bisect.
Labels: -Pri-2 -OS-All -Needs-Bisect hasbisect OS-Linux OS-Mac OS-Windows Pri-1
Owner: bokan@chromium.org
Status: Assigned (was: Available)
Able to reproduce this issue on Windows 10, Ubuntu 14.04 and Mac 10.12.2 on chrome stable version 55.0.2883.87 and also in current canary version #57.0.2964.0
Issue is broken in M41. 

Bisect Info:
==========
Good build : 41.0.2253.3,  Revision Range -308982
Bad build  : 41.0.2254.0,  Revision Range -309179

After executing the (old)bisect script, i got the following CL's between good and bad build versions
===================================================
https://chromium.googlesource.com/chromium/src/+log/008e903998af2fc2bbe600f86c69f85fb97ae7c5..e06ea3d8d0d0978001b5fc1f6a54c4665e0e82a7

The suspecting Change Log is :
-----------
https://chromium.googlesource.com/chromium/src/+/66f25e1d8c97a209dd0bf0ed8669575d355265f6

From the above CL suspecting the below change
---------------------------
Review URL: https://codereview.chromium.org/795513003

bokan@- Could you please look into this issue, if it's related to your change?  if not could you please help us to reassign this issue to the right owner.

Comment 10 by bokan@chromium.org, Dec 30 2016

Status: WontFix (was: Assigned)
This is working as intended. When you turn on device emulation ("device tools" in the repro screencast), the page is zoomed in so position: fixed elements won't stay stuck to the screen (you can zoom out by clicking and dragging while holding Shift).

The CL above made this change but it was intentional. See http://bokand.github.io/viewport/index.html to get an idea of how this works.

Sign in to add a comment