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

Issue 618423 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

position:absolute not displaying correctly

Reported by jamescol...@gmail.com, Jun 8 2016

Issue description

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

Example URL:
http://semantic-ui.com/elements/divider.html

Steps to reproduce the problem:
1. Visit vertical divider section of http://semantic-ui.com/elements/divider.html 
2. Observe location of vertical dividers compared to chrome stable.

What is the expected behavior?
Correct positioning of floated content

What went wrong?
In between content is pushed all the way to the left

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? Yes Chrome stable

Does this work in other browsers? Yes 

Chrome version: 53.0.2762.0  Channel: canary
OS Version: OS X 10.11.4
Flash Version: Shockwave Flash 22.0 r0
 
Want to mention this github issue with this when I filed it with semantic.
https://github.com/Semantic-Org/Semantic-UI/issues/3986
Components: -Blink Blink>Layout
This appears to be an issue with :before and :after content.
Cc: msrchandra@chromium.org
Labels: -Type-Bug M-52 OS-Linux OS-Windows Type-Bug-Regression
Owner: kulshin@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on Latest Beta# 52.0.2743.33 and Latest Dev# 53.0.2756.0 and Latest Canary# 53.0.2763.0 on Windows, Mac and Linux.

This is a Regression Issue in M52, below are the CL details ::
Chrome Good Build :: 52.0.2718.0
Chrome Bad  Build :: 52.0.2719.0

CHANGELOG URL:
  https://chromium.googlesource.com/chromium/src/+log/33a081977fa4f03d96265f6ada2d3347d9f0db46..187a2805642014aead68645a21dd3ac2c3c5cecb

Suspecting Commit# 1acd6b6af8c9ef59fe7227faff4585310e5c2ec8
Suspecting Review URL# https://codereview.chromium.org/1919573002

@kulshin -- Could you please look into the issue, pardonme if it has nothing to do with your changes and if possible please assign it to concern owner.

Thank You.


If this repros on Mac and Linux, that should be an indication that 1acd6b6af8c9ef59fe7227faff4585310e5c2ec8 is likely not the cause, as that change is almost exclusively Windows-only. I can take a closer look in the morning, but in the meantime, have you excluded b80c579439ab737f82cddb5c73c91bc1daacd354 from consideration?
Cc: cbiesin...@chromium.org
Thank You Kulshin for the update. As per Comment#4 looping in related Dev.
Thank You.
Project Member

Comment 6 by sheriffbot@chromium.org, Jun 9 2016

Labels: -M-52 M-53 MovedFrom-52
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Assigned)
Summary: position:absolute not displaying correctly (was: position:relative not displaying correctly)
This is position: absolute, not relative.

We have updated our implementation to match the spec. absolutely-positioned elements are now positioned according to the spec:
https://drafts.csswg.org/css-flexbox/#abspos-items

I would suggest you reopen the bug report with semantic pointing to the spec. Thanks!
Cc: gw...@microsoft.com
Note that Edge should display this the same way as our new behavior, though I can't immediately verify.
It does and soon will for FF as they're refactoring their code as well. https://twitter.com/CodingExon/status/738499222333325312

I've attached a screenshot comparing Edge and Canary.
semantic-ui.PNG
60.6 KB View Download
Owner: cbiesin...@chromium.org

Sign in to add a comment