[tbb-bugs] #21267 [Applications/Tor Browser]: e10s compatibility for Torbutton's content sizer
Tor Bug Tracker & Wiki
blackhole at torproject.org
Thu Feb 9 16:56:38 UTC 2017
#21267: e10s compatibility for Torbutton's content sizer
-------------------------------------------------+-------------------------
Reporter: mcs | Owner: tbb-
| team
Type: defect | Status:
| needs_information
Priority: Medium | Milestone:
Component: Applications/Tor Browser | Version:
Severity: Normal | Resolution:
Keywords: tbb-torbutton,ff52-esr, | Actual Points:
TorBrowserTeam201702 |
Parent ID: #21201 | Points:
Reviewer: | Sponsor:
| Sponsor4
-------------------------------------------------+-------------------------
Changes (by mcs):
* cc: arthuredelstein (added)
Comment:
Kathy and I spent some time looking at what it would take to make the
content-sizer.js code work in an e10s environment. Unfortunately, it does
not look like it will be a simple task and the existing code is
complicated enough that it makes sense for Arthur to own this task.
Most of the problems are inside the updateDimensions() function. All
places where the code accesses gBrowser.contentWindow must be modified to
get information using an alternative method, or we need to use a content
script combined with Firefox's message manager from the chrome side to
request the info we need (full screen state, zoom factor, content window
dimensions). The necessary changes will be a little tricky because simple
variable access must be replaced with asynchronous message exchanges.
Kathy and I do not understand the existing content-sizer code well enough
to be confident that we will account for everything correctly when we
rearchitect the code in this way.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21267#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tbb-bugs
mailing list