ubuntu-webapps-bugs team mailing list archive

[Chris Coulson <chris.coulson@xxxxxxxxxxxxx>]

Public bug reported:

This is all stuff that was written for the first iteration of Oxide, and
is a bit inconsistent. Eg, UserScript can be shared between
WebContext's, and WebContext will only take ownership of an unowned
UserScript. However, ScriptMessageHandler can't be shared between
message targets, and a message target (WebView or WebFrame) will
unconditionally take ownership of a ScriptMessageHandler.

Given that ScriptMessage has a frame property, there's no reason why we
shouldn't make ScriptMessageHandler shareable

** Affects: oxide
     Importance: Medium
         Status: Triaged

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

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

-- 
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/1435769

Title:
  Fix ScriptMessageHandler ownership and allow it to be shared between
  message targets

Status in Oxide Webview:
  Triaged

Bug description:
  This is all stuff that was written for the first iteration of Oxide,
  and is a bit inconsistent. Eg, UserScript can be shared between
  WebContext's, and WebContext will only take ownership of an unowned
  UserScript. However, ScriptMessageHandler can't be shared between
  message targets, and a message target (WebView or WebFrame) will
  unconditionally take ownership of a ScriptMessageHandler.

  Given that ScriptMessage has a frame property, there's no reason why
  we shouldn't make ScriptMessageHandler shareable

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