Open
Bug 1227602
Opened 10 years ago
Updated 3 years ago
Ensure the <xul:browser> is being displayed before attempting to flip remoteness to true
Categories
(Firefox :: Tabbed Browser, defect, P5)
Firefox
Tabbed Browser
Tracking
()
NEW
People
(Reporter: mconley, Unassigned)
Details
Not sure if this is worth it, but I've burned time trying to figure out why I can't flip the remoteness of a browser. It turned out that the browser had some CSS styling on it that made it display:none. This meant that it wasn't given a frameloader after flipping the remote attribute.
I could have saved a bunch of time if updateBrowserRemoteness did such a check before attempting to flip remoteness, and throwing because the browser is not visible.
This is low-priority. More of a footgun guard than anything.
|
||
Updated•8 years ago
|
Component: General → Tabbed Browser
Priority: -- → P5
|
||
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•