New issue
Advanced search Search tips

Issue 786894 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 750419
Owner: ----
Closed: Nov 2017
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Extension popup borders became inconsistent

Reported by shuto...@gmail.com, Nov 20 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36

Steps to reproduce the problem:
1. Install some extension with popup action page.
2. Click action button.
3. See the popup.

What is the expected behavior?
No borders are displayed at all or at least horizontal and vertical borders have the same width.

What went wrong?
There are white borders at top and bottom. Left and right borders are missing. Pages with dark background have become weird and there is no way to make custom design with dark background look good in harmony with browser.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 62.0.3202.94  Channel: stable
OS Version: 10.0
Flash Version:
 
chrome-62-extension-frames.png
60.2 KB View Download
chrome-61-extension-popup-border.png
91.1 KB View Download

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

Duplicate of  issue 750419 .
The developers don't see it as a problem or can't do better at the moment until some underlying "layer masks" functionality is added.

Actually, it grew on me too over the 3 months I've been seeing the new borders in Chrome canary - at least I'm not upset about it. 
The only realistic fix/workaround seems to be to suggest the extension authors to add side borders on <body> element based on the browser version.
Labels: Needs-Triage-M62 Triaged-ET
Mergedinto: 750419
Status: Duplicate (was: Unconfirmed)
The issue looks similar to issue id: 750419. Hence, merging into issue id: 750419.

Thanks...!!

Comment 3 by shuto...@gmail.com, Nov 21 2017

So, I've described a problem and you have merged it into closed issue?

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

It's a duplicate so it was merged, which is the usual practice on all bug trackers. That closed issue has a chromium member in its "Owner" field so you can try to appeal to the developers by posting a convincing argument (not yet posted there) in a comment to that original issue.

Sign in to add a comment