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

Issue 702128 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Jun 2017
Cc:
tkent@chromium.org
nyerramilli@chromium.org
kkaluri@chromium.org
█ brajkumar@chromium.org
█ msrchandra@chromium.org
█ ranjitkan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Misalignment of header option is observed on webpage after clicking ‘Developer website’ link of Darkness extension.

Reported by dmascare...@etouch.net, Mar 16 2017 
Chrome Version:59.0.3043.0 (Official Build) fe785a58e31217e1ef0e1c8946a4e853829371f8-refs/heads/master@{#457297}
OS :Mac (10.11.6,10.12.1)

Pre-condition: Add ‘Darkness’ extension using url:https://chrome.google.com/webstore/detail/darkness-beautiful-dark-t/imilbobhamcfahccagbncamhpnbkaenm/related?utm_source=chrome-ntp-icon

What steps will reproduce the problem?
1. Launch chrome and navigate to chrome://extensions/
2. Click on ‘ Developer website’ link of same extension such that webpage gets open, Observe header options (i.e. About,Product,Contact)

Actual: Misalignment of header option is observed on webpage after step 2.
Expected: Header option should be in proper position.

This is regression issue, broken in ‘M 59’ and below Manual bisect info:
Good build:58.0.3012.0
Bad build:58.0.3013.0

Note: Issue is not seen on Windows and Linux OS.
Actual_darknes.mov
2.2 MB Download

Comment 1 by kkaluri@chromium.org, Mar 16 2017

Cc: kkaluri@chromium.org
Labels: hasbisect-per-revision
Owner: yosin@chromium.org
Status: Assigned (was: Unconfirmed)
Bisect Info:
===========
Good build : 58.0.3012.0 ,  Revision Range - 450199
Bad build  : 58.0.3013.0 ,  Revision Range - 450530

After executing the per-revision bisect script , i got the following CL's between good and bad build versions
===========================================
https://chromium.googlesource.com/chromium/src/+log/18375370aff250f59f5ef624ecf686d860377ece..d892f9592860691ae9a782c12260c94ed6bd1a63

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

Review-Url: https://codereview.chromium.org/2680943004

yosin@- 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 2 by ranjitkan@chromium.org, Mar 16 2017

Labels: ReleaseBlock-Stable
Adding release block label, please undo if not the case.

Comment 3 by manoranj...@chromium.org, Mar 16 2017

Labels: -ReleaseBlock-Stable
Seems like, this alignment issue is specific to one extension website. Hence not a "RB-Stable".

Comment 4 by yosin@chromium.org, Mar 23 2017

Owner: ----
My change mentioned in #c1 changes internal data for selection.
It should not affect layout.

Comment 5 by manoranj...@chromium.org, Mar 23 2017

Labels: Needs-Bisect

Comment 6 by brajkumar@chromium.org, Jun 21 2017

Cc: tkent@chromium.org brajkumar@chromium.org
Components: -Platform>Extensions Blink
Labels: -Needs-Bisect hasbisect
Status: Untriaged (was: Assigned)
Tried performing per-revision bisect once again and observing the same change log provided in the comment #1. So, providing chromium bisect information below. 

Bisect Information:
---------------------
You are probably looking for a change made after 450366 (known good), but no later than 450376 (first known bad).

CHANGELOG URL:
----------------  https://chromium.googlesource.com/chromium/src/+log/226d1bedd1dd5ccc7b2c8a67c72470a4c88d179d..c8e27a009a07233002d0397cf8c0134e09b572f5

Unable to find the actual suspect from the above log, could someone help us in assigning to the concerned owner.

Thanks!

Comment 7 by bokan@chromium.org, Jun 22 2017

Components: -Blink Blink>Layout
Reproduced in 61.0.3135.4.

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

Status: WontFix (was: Untriaged)
An extension that modifies websites by injecting content is breaking the web site of the extension itself? There is a lot of irony in there.

Regardless, this is an issue with the extension in question, not with Chrome.
►

Sign in to add a comment