Closed Bug 1196163 Opened 5 years ago Closed 5 years ago

[e10s] Window.fullScreen always returns false for content window

Categories

(Core :: DOM: Core & HTML, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla43
Tracking Status
e10s + ---
firefox43 --- fixed

People

(Reporter: xidorn, Assigned: xidorn)

References

Details

Attachments

(3 files)

Step to reproduce:
1. open the Web Console
2. press F11 to enter fullscreen mode
3. in the console, execute `window.fullScreen`

Expected result:
the expression returns true

Actual result:
the expression returns false


This is not a regression. It is always this way as we do not store the fullscreen state in the content process at all.

Also, Window.fullScreen is not a standard attribute, hence this is probably not important. The only issue is that, the fullscreen-api-race test relies on this. I want to have a way to detect whether the window is actually exit fullscreen state in that test.
Bug 1196163 part 1 - Use nsSizeMode instead of int32_t for nsIWidget::{SizeMode,SetSizeMode}.
Attachment #8653784 - Flags: review?(roc)
Bug 1196163 part 2 - Send sizemode as part of UpdateDimensions message to TabChild.
Attachment #8653785 - Flags: review?(roc)
Attachment #8653785 - Flags: review?(bugs)
Bug 1196163 part 3 - Derive value of window.fullScreen for content process from the sizemode of puppet widget.
Attachment #8653786 - Flags: review?(bugs)
Comment on attachment 8653784 [details]
MozReview Request: Bug 1196163 part 1 - Use nsSizeMode instead of int32_t for nsIWidget::{SizeMode,SetSizeMode}.

https://reviewboard.mozilla.org/r/17519/#review15655
Comment on attachment 8653785 [details]
MozReview Request: Bug 1196163 part 2 - Send sizemode as part of UpdateDimensions message to TabChild.

https://reviewboard.mozilla.org/r/17521/#review15657
Attachment #8653785 - Flags: review?(roc) → review+
Attachment #8653785 - Flags: review?(bugs) → review+
Attachment #8653786 - Flags: review?(bugs) → review+
Depends on: 1204149
You need to log in before you can comment on or make changes to this bug.