Open Bug 1299889 Opened 5 years ago Updated 3 years ago

Popups sometimes have an extra 1px white border

Categories

(WebExtensions :: Frontend, defect, P3)

defect

Tracking

(firefox51 affected)

Tracking Status
firefox51 --- affected

People

(Reporter: kmag, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: triaged)

(In reply to Kris Maglione [:kmag] from bug 1280128 comment #56)
> (In reply to Kris Maglione [:kmag] from comment #55)
> > (In reply to Andrei Vaida, QA [:avaida] – please ni? me from comment #54)
> > >         - 50.0a2 (2016-04-25): the background extends to the entire
> > >           visible area, *excluding* the arrow AND there's a white
> > >           right-border visible, for both the browserAction and
> > >           pageAction popups
> > >            - screenshot: http://imgur.com/a/pQkyf
> > 
> > Hm. I guess we'll have to re-add the negative end margin for 50, but not 49
> > or
> > 51. I'll look into this a bit more and try to find out exactly what's going
> > on.
> 
> Ok, apparently this is being caused by the extra 1px that we add to the
> calculated width of the browser, combined with a layout bug caused by the
> size calculation code reflowing the browser to its preferred width. I don't
> know why we're only seeing this on 50 now, I'm considering removing the
> extra 1px and uplifting to 50, since this bug seems worse, and more common,
> than the one rhat was trying to address[1].
> 
> Thoughts?
> 
> [1]: Sometimes lines of text wind up wrapping, even though the panel should
> be wide enough for them. I can't actually reproduce this anymore, and it's
> possible that ot was fixed by recent changes to the resizing code that hid
> the panel's scrollbars.
Priority: -- → P1
Whiteboard: triaged
I'm still getting this on 54.0a1 (2017-01-23) using a popup with html, body { padding: 0; margin: 0; } and a background color that makes it obvious. The 1px border is on the right.
Assignee: kmaglione+bmo → nobody
Priority: P1 → P3
Product: Toolkit → WebExtensions
You need to log in before you can comment on or make changes to this bug.