Layout and input events messed up when using Flash in fullscreen
Bug #1510508 reported by
Chris Coulson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Oxide |
Fix Released
|
Medium
|
Chris Coulson |
Bug Description
If I make Flash go fullscreen from a maximised window, then it seems to work ok. However, if I make it go fullscreen from a non-maximised window, the layout seems to be slightly broken. In addition to that, input events don't work correctly.
See the example of the BBC iPlayer
Related branches
Changed in oxide: | |
assignee: | nobody → Chris Coulson (chrisccoulson) |
Changed in oxide: | |
status: | Triaged → In Progress |
Changed in oxide: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
This happens because Flash content expects the content to be resized synchronously when going fullscreen, but that doesn't happen in webbrowser-app.
Chrome has a workaround for this in DesktopWindowTr eeHostX11: :SetFullscreen, with the following comment:
// Try to guess the size we will have after the switch to/from fullscreen: /crbug. com/361408 bounds_ in_pixels_ = bounds_in_pixels_;
gfx::Screen: :GetScreenFor( NULL)-> GetDisplayNeare stWindow( window( )); in_pixels_ = ToPixelRect( display. bounds( )); in_pixels_ = restored_ bounds_ in_pixels_ ;
// - (may) avoid transient states
// - works around Flash content which expects to have the size updated
// synchronously.
// See https:/
if (fullscreen) {
restored_
const gfx::Display display =
bounds_
} else {
bounds_
}
I guess we can do something similar in Oxide, where we resize the Flash content before the browser actually goes fullscreen