Make sure we're doing the right thing with chromeFlags in ContentParent::CreateBrowserOrApp for the app case

NEW
Unassigned

Status

()

Core
DOM: Content Processes
2 years ago
2 years ago

People

(Reporter: mconley, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

In bug 1194897, we realized that we weren't sending the right chromeFlags down to the content process (which it needed to check the values of window.locationbar.visible, window.menubar.visible, etc). smaug noticed that we're sending a 0 down as the chromeFlags to the TabChild process in the app case later on in that method. He asked me to file this bug to ensure that this is actually what we should be doing.

Comment 1

2 years ago
I think we want to sent the proper flags in both cases. But do we want to send even
CHROME_PRIVATE_WINDOW and CHROME_PRIVATE_LIFETIME?
You need to log in before you can comment on or make changes to this bug.