New issue
Advanced search Search tips

Issue 732397 link

Starred by 5 users
Status: Available
Owner: ----
Cc:
atotic@chromium.org
kkaluri@chromium.org
pbomm...@chromium.org
e...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Mac
Pri: 3
Type: Bug



Sign in to add a comment

Element in different position after toggling display property from absolute and back

Reported by josh.bje...@gmail.com, Jun 12 2017 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.86 Safari/537.36

Steps to reproduce the problem:
1. Set element display to absolute, relative to a parent with some inline content in front of it
2. Change element display to static (or anything else)
3. Change element display back to absolute

https://codepen.io/anon/pen/bWjbPN (click "toggle position" button twice)

What is the expected behavior?
Element should return to its initial position

What went wrong?
Element winds up in completely different position

Did this work before? N/A 

Chrome version: 59.0.3071.86  Channel: stable
OS Version: OS X 10.12.4
Flash Version: Shockwave Flash 25.0 r0

Seems as though its absolute position becomes no longer relative to the (relative) parent. Here's a CodePen: https://codepen.io/anon/pen/bWjbPN (click "toggle position" button twice). Behaviour as expected in both Firefox and IE.

Comment 1 by pbomm...@chromium.org, Jun 12 2017

Cc: pbomm...@chromium.org
Components: -UI Blink>Layout
Labels: pre-stable-59.0.3071.86 M-59 Needs-Bisect OS-Android OS-Linux OS-Windows
Status: Available (was: Unconfirmed)
Able to reproduce the issue with latest Chrome current and previous stable channels i.e., 59.0.3071.86, 58.0.3029.110 and 57.0.2987.133 on Windows 7,10, mac and Linux and also able to reproduce the issue on latest Chrome beta(60.0.3112.24), Dev(61.0.3124.10) and Canary(61.0.3128.0).

Comment 2 by josh.bje...@gmail.com, Jun 13 2017 

Sorry, position* property

Comment 3 by kkaluri@chromium.org, Jun 22 2017

Cc: kkaluri@chromium.org e...@chromium.org
Labels: -Needs-Bisect -M-59 M-61
Status: Untriaged (was: Available)
Able to reproduce this issue on Windows 10, Ubuntu 14.04 and Mac 10.12.5 with chrome Stable #59.0.3071.109, Canary #61.0.3137.0 and also in earlier version M-30 #30.0.1549.0, this is a non regression issue hence marking it as untriaged.

Attaching the screen-cast for reference.

cc'ing the Blink>layout dev eae@ for further triage.
Issue 732397.mp4
434 KB View Download

Comment 4 by e...@chromium.org, Jun 26 2017

Labels: -Pri-2 Pri-3
Status: Available (was: Untriaged)

Comment 5 by josh.bje...@gmail.com, Sep 21 2017 

Any progress made on this?
Project Member

Comment 6 by sheriffbot@chromium.org, Sep 21

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 7 by josh.bje...@gmail.com, Sep 21 

Kinda shocked this still hasn't been addressed. A pretty major issue if you ask me.

Comment 8 by e...@chromium.org, Sep 25

Cc: atotic@chromium.org
Status: Available (was: Untriaged)
Still broken both in legacy and LayoutNG.
►

Sign in to add a comment