ubuntu-webapps-bugs team mailing list archive

[Chris Coulson <chris.coulson@xxxxxxxxxxxxx>]

Public bug reported:

With bug 1542119, compositing logic and input handling will move to
WebContentsView, and a new client class will be used for querying bounds
/ visibility etc from the actual view (whether that be
OxideQQuickWebView or some other content view).

To do this, fullscreen logic needs to come out of oxide::WebView, as we
need to query fullscreen state when determing the view bounds.

** Affects: oxide
     Importance: Low
     Assignee: Chris Coulson (chrisccoulson)
         Status: Triaged

** Changed in: oxide
   Importance: Undecided => Low

** Changed in: oxide
       Status: New => Triaged

** Changed in: oxide
     Assignee: (unassigned) => Chris Coulson (chrisccoulson)

-- 
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1543761

Title:
  Move fullscreen logic out of oxide::WebView

Status in Oxide:
  Triaged

Bug description:
  With bug 1542119, compositing logic and input handling will move to
  WebContentsView, and a new client class will be used for querying
  bounds / visibility etc from the actual view (whether that be
  OxideQQuickWebView or some other content view).

  To do this, fullscreen logic needs to come out of oxide::WebView, as
  we need to query fullscreen state when determing the view bounds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1543761/+subscriptions