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

Issue 780733 link

Starred by 2 users
Status: Duplicate
Merged: issue 370874
Owner:
mstensho@chromium.org
Closed: Feb 2018
Cc:
█ msten...@opera.com
rkalavakuntla@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

CSS position absolute within relative column item remains in document flow

Reported by oliverj...@gmail.com, Nov 2 2017 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36

Steps to reproduce the problem:
Example: http://jsbin.com/bexewig/4

1. Create a column layout using `column-count: 1`
2. Add a column item with `position: relative`, and within that an element with `position: absolute`

What is the expected behavior?
The column container should not contain the absolutely positioned item, because absolutely positioned items are not part of the document flow.

What went wrong?
The column container does contain the absolutely positioned item. See border on container in JSBin example.

I expect this to be the same as if the container was not a column container (first example in JSBin).

Did this work before? N/A 

Does this work in other browsers? No
 Also occurs in Firefox. Does not occur in Safari.

Chrome version: 61.0.3163.100  Channel: n/a
OS Version: OS X 10.13.0
Flash Version:

Comment 1 by woxxom@gmail.com, Nov 2 2017 

Bisect info: 331422 (good) - 331433 (bad)
https://chromium.googlesource.com/chromium/src/+log/555f740c..e0788afb?pretty=fuller
Suspecting r331424 "Roll src/third_party/WebKit"
In webkit roll suspecting db89e3146bd1d19b5f178ecd576483e3f6fce966 "Enable RegionBasedColumns runtime flag for stable"
Landed in 45.0.2414.0

P.S. Use the attached test.html, which adds a prefixed CSS column rule to run in old builds.
test.html
864 bytes View Download

Comment 2 by nyerramilli@chromium.org, Nov 2 2017

Labels: Needs-Bisect Needs-Milestone

Comment 3 by krajshree@chromium.org, Nov 3 2017

Components: Blink>CSS
Labels: -Type-Bug -Pri-2 -Needs-Bisect M-64 hasbisect OS-Linux OS-Windows Pri-1 Type-Bug-Regression
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on Windows 10, mac 10.12.6 and ubuntu 14.04 using chrome stable version #62.0.3202.75 and latest canary #64.0.3256.0.

Bisect Information:
=====================
Good build: 50.0.2654.0  Revision(376054)
Bad Build : 50.0.2655.0  Revision(376333)

Change Log URL: 
https://chromium.googlesource.com/chromium/src/+log/b3d6d548c137cea06101937cec56d085fb40fae0..a7a6196257751af4e1bf769d60cb566c437f28e8

Unable to find any suspect from the above change log. Hence, marking it as untriaged and requesting anyone from the dev team to please help us in assigning it to the right owner.

Thanks...!!

Comment 4 by woxxom@gmail.com, Nov 3 2017 

krajshree@chromium.org, in yourchangelog it's ef0bbaa58e53dc720970aec40a06f24ca66f7b0d which introduced unprefixed CSS columns and exposed the bug found in my #c1 using a prefixed property. You can CC or assign mstensho@opera.com who authored both commits.

Comment 5 by ligim...@chromium.org, Nov 3 2017

Cc: msten...@opera.com
Labels: -Needs-Milestone
Owner: dsinclair@chromium.org
Status: Assigned (was: Untriaged)
Assiging to one of the reviewers of the patch, mstensho@ id seems to be not in use.

Comment 6 by dsinclair@chromium.org, Nov 6 2017

Owner: e...@chromium.org
eae@ to triage for layout dev.

Comment 7 by meade@chromium.org, Nov 7 2017

Components: -Blink>CSS Blink>Layout

Comment 8 by e...@chromium.org, Nov 7 2017

Cc: rkalavakuntla@chromium.org
 Issue 781144  has been merged into this issue.

Comment 9 by e...@chromium.org, Nov 9 2017

Owner: mstensho@chromium.org

Comment 10 by e...@chromium.org, Nov 30 2017

Labels: -Pri-1 Pri-2

Comment 11 by mstensho@chromium.org, Feb 13 2018

Mergedinto: 370874
Status: Duplicate (was: Assigned)
►

Sign in to add a comment