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

Issue 878802 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 693412
Owner:
Closed: Aug 30
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

position: sticky sometimes off by 1 pixel

Reported by callaha...@gmail.com, Aug 29

Issue description

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

Steps to reproduce the problem:
1. Open the test file or visit https://codepen.io/chriscallahan/pen/pOEqbb (the code is the same)
2. Scroll down the page. Notice that when the "Section 3" header is stuck to the top, there is 1px of blue visible above the header.

What is the expected behavior?
There is no space between the top of the header and the top of the page.

What went wrong?
Although all four <header> elements have the same `position: sticky;` and `top: 0;` rules applied, the behavior is slightly different for the third header. This header should be stuck to the top of its container (see section-1 screenshot), but there is 1 pixel of blue content from its container that is visible above the header (see section-3 screenshot).

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 68.0.3440.106  Channel: stable
OS Version: OS X 10.12.6
Flash Version:
 
sticky.html
936 bytes View Download
section-1.png
15.2 KB View Download
section-3.png
20.1 KB View Download
Labels: Needs-Triage-M68
Components: Blink>Layout
Labels: -Type-Bug -Pri-2 hasbisect-per-revision Triaged-ET M-69 ReleaseBlock-Stable Target-69 FoundIn-70 Target-68 FoundIn-68 FoundIn-69 Pri-1 Type-Bug-Regression
Owner: yigu@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on Mac 10.13.3 using chrome reported version #68.0.3440.106 but the same is not reproducible in the latest canary #70.0.3536.0. Issue is not seen in OS-win and OS-linux.

Reverse Bisect Information:
=====================
Good build: 70.0.3530.0  
Bad Build : 70.0.3529.0  

Change Log URL: 
https://chromium.googlesource.com/chromium/src/+log/def4c5c79f27879310d32906121d48d3291724f6..20c11c9492d799080819ff38696f09b2102211f6

From the above change log suspecting below change
Change-Id: Ideab875d2d087b8fe97264d0bddbd7e2393f8e7f
Reviewed-on: https://chromium-review.googlesource.com/1183622

yigu@ - Could you please check and merge the fix to M-69 if it is a valid candidate.
Adding RBS as it seems to be a recent regression. Please feel free to remove the same if not appropriate.
Thanks...!!
Cc: smcgruer@chromium.org pdr@chromium.org
Labels: Merge-Request-69
Cherry-picked patch: https://chromium-review.googlesource.com/c/chromium/src/+/1196822

cc the reviewers of the origin patch just an FYI.
Project Member

Comment 4 by sheriffbot@chromium.org, Aug 30

Labels: -Merge-Request-69 Merge-Review-69 Hotlist-Merge-Review
This bug requires manual review: We are only 4 days from stable.
Please contact the milestone owner if you have questions.
Owners: amineer@(Android), kariahda@(iOS), cindyb@(ChromeOS), govind@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: amineer@chromium.org
Components: -Blink>Layout Internals>Compositing
Add amineer@ for manual review.
Labels: -M-69 -Target-69 -Merge-Review-69 Merge-Rejected-69 Target-70 M-70
This is regressed in M68 and So far we only have one bug report with 1 star. M69 is going to stable next week and we're only taking  absolutely critical merges in at this point. So rejecting merge to M69. Pls let me know ASAP if there is any concern here.  


Mergedinto: 693412
Status: Duplicate (was: Assigned)
Agreed. The fix is a nice-to-have but not must-have. Dup the issue into the one that fixed the bug.

Sign in to add a comment