Add an API to allow content scripts to bind objects to the main world global object

Bug #1221996 reported by Chris Coulson
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Alexandre Abreu
Alexandre Abreu

Bug Description

As all content scripts run in an isolated world, properties they modify on their global object are not reflected in to the main world. This makes it difficult for content scripts to add new API's.

It looks like unity-chromium-extension works around this for Chromium by inserting a script element in to a webpage which adds a proxy API. The proxy API uses DOM events to pass messages to communicate to the content script, which then communicates with the browser.

In oxide, it would be nice to have an API that allows content scripts to bind an object to the main world global object, rather than having to insert script elements in to a page.

Related branches

Changed in oxide:
importance: Undecided → Medium
status: New → Triaged
Changed in oxide:
assignee: nobody → Alexandre Abreu (abreu-alexandre)
David Barth (dbarth)
tags: added: desktop webapp-container
David Barth (dbarth)
tags: added: webapps-blocker
Changed in oxide:
status: Triaged → In Progress
David Barth (dbarth)
tags: added: html5-blocker
removed: desktop webapp-container webapps-blocker
David Barth (dbarth)
tags: added: rtm14
tags: added: touch-2014-09-18
Changed in oxide:
importance: Medium → Critical
tags: added: touch-2014-10-09
removed: touch-2014-09-18
Revision history for this message
David Barth (dbarth) wrote :

Adjusting the priorities. It is required to remove qtwebkit, but is not a user facing issue.

tags: added: ota-1
removed: rtm14
Changed in oxide:
importance: Critical → High
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Per dbarth, this is not a ship blocker, should be High and delivered as part of ota-1. This is part of the removing webkit from the images work and is on track to be delivered sooner.

Olivier Tilloy (osomon)
tags: added: touch-2014-10-16
removed: touch-2014-10-09
Changed in oxide:
status: In Progress → Fix Released
milestone: none → 1.3.0
Changed in oxide:
milestone: 1.3.0 → branch-1.3
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers