gmhawash@ - Thanks for filing the issue...!!

Could you please provide a sample URL to test the issue from TE-end. This will help us in triaging the issue further.

Thanks...!!

The app is locked down with password and browser certs.  I would be happy to set up an account for you to access, but I need a specific email address to send the certs to.  Should I use krajshree@chromium.org?  If not, please provide me with an email address.

Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Hi gmhawash@,

Accepting credentials for bug repros is difficult for us for a variety of reasons.

instead of providing credentials, would it be possible to either:
* save the page on which the issue is occurring and attach the HTML to this issue; or
* save the page and strip out any sensitive information before attaching the HTML?

Ok, I've saved the page from Chrome and attached a zip file below.

Deleted: Chrome 61 issue.zip 583 KB

Chrome 61 issue.zip 583 KB Download

Thank you for providing more feedback. Adding requester "rjwright@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Can the page be simplified?

Is the icon shown in other browsers?

Our app only works with Chrome, no other browser.  But, if you try Chrome 60 (and before) worked fine, but Chrome 61 does not.

Here is a video that demonstrates the issue https://youtu.be/u7fwGqlGByM.  There are two icons, one shows up immediately, and the other one does not.  As the video shows, I can make it show up by toggling the 'display' attribute.  On Chrome 60, it just shows up on page load.

Thank you for providing more feedback. Adding requester "ericwilligers@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Assigning to Eric to confirm

Confirmed 61.0.3163.100 (Official Build) (64-bit). Second icon doesn't show up until I toggle the display property.

Cannot repro on 63.0.3218.0 (Official Build) dev (64-bit). Second icon shows up immediately. Requesting triage to find the revision that fixed this issue.

Oops, I meant requesting a bisect.

Able to reproduce the issue on Windows 10, mac 10.12.6 and Ubuntu 14.04 using chrome stable version #61.0.3163.100 but the same is not reproducible in the latest canary #63.0.3223.8.

Reverse Bisect Information:
=====================
Good build: 63.0.3211.0  Revision(500753)
Bad Build : 63.0.3210.0  Revision(500529)

Change Log URL: 
https://chromium.googlesource.com/chromium/src/+log/14527543958d60b00d130bb0a06945d72b44966f..27c507212fd72de9f944ff001665c242a7785cce

From the above change log possible CL that fixed this issue:
Change-Id: I1ad11423182282066ede39a4e8da2bab0fbab1da
Reviewed-on: https://chromium-review.googlesource.com/655309

ericwilligers/eae@ - Could you please check and merge the fix to M63 if it is a valid canadidate.
Note: ccing reviewer(eae@) of the issue as the author(robhogan@) seems to be OOO from more than 30 days.
Also adding label ReleaseBlock-Stable as it seems to be a recent regression. Please feel free to remove the same if not appropriate.

Thanks...!!

Reassigning. This isn't a CSS bug.

r500539 indeed seems like a likely change to have fixed this issue.
We're likely too late in the process to DI the fix into 62 by now.

gmhawash: A potential workaround until 63 is released would be to remove the "display: inline-block" style. That prevents it from disappearing without changing the layout in any way that I can detect.

krajshree: This is marked as RB-S for 63. Given that the issue does not occur in 63 that doesn't make much sense. Did you mean to mark it for M62?

To krajshree for clarification.

Apologies for the milestone being marked to M-63. The issue is reproducible on latest beta #62.0.3202.45. Hence, changing the milestone to M-62.

Thanks...!!

eae@, Just wondering, are we still targeting the fix to M62? If not please adjust the priority and other milestone labels.

Thank you!

Given that this is already broken in 61 and that a workaround is available I'm reluctant to integrate the fix in 62 given the risks involved.

Note that this *has* been fixed in 63.

Updating status accordingly.