ubuntu-webapps-bugs team mailing list archive

[Chris Coulson <chrisccoulson@xxxxxxxxxx>]

Public bug reported:

I'd like to deprecate WebContext.userScripts and move it to a new user
data manager object instead, along with the script message handlers. The
situation today where user scripts are registered per-WebContext but
message handlers for those scripts are registered per-WebView is a bit
odd.

I'd also like to extend this new interface to support adding custom
stylesheets (see bug 1414078).

We could also investigate allowing WebView's to provide a custom user
data manager instance which overrides the one provided by the WebContext
- this is a bit tricky though, which is why user scripts are only per-
WebContext.

** Affects: oxide
     Importance: Medium
         Status: Triaged

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

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

** Description changed:

  I'd like to deprecate WebContext.userScripts and move it to a new user
  data manager object instead, along with the script message handlers. The
  situation today where user scripts are registered per-WebContext but
  message handlers for those scripts are registered per-WebView is a bit
  odd.
  
  I'd also like to extend this new interface to support adding custom
- stylesheets (see bug 1414078)
+ stylesheets (see bug 1414078).
+ 
+ We could also investigate allowing WebView's to provide a custom user
+ data manager instance which overrides the one provided by the WebContext
+ - this is a bit tricky though, which is why user scripts are only per-
+ WebContext.

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

Title:
  Add a user data manager API

Status in Oxide:
  Triaged

Bug description:
  I'd like to deprecate WebContext.userScripts and move it to a new user
  data manager object instead, along with the script message handlers.
  The situation today where user scripts are registered per-WebContext
  but message handlers for those scripts are registered per-WebView is a
  bit odd.

  I'd also like to extend this new interface to support adding custom
  stylesheets (see bug 1414078).

  We could also investigate allowing WebView's to provide a custom user
  data manager instance which overrides the one provided by the
  WebContext - this is a bit tricky though, which is why user scripts
  are only per-WebContext.

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