[tbb-bugs] #26520 [Applications/Tor Browser]: NoScript is broken with TOR_SKIP_LAUNCH=1 in ESR 60-based Tor Browser
Tor Bug Tracker & Wiki
blackhole at torproject.org
Tue Aug 28 07:40:53 UTC 2018
#26520: NoScript is broken with TOR_SKIP_LAUNCH=1 in ESR 60-based Tor Browser
-------------------------------------------------+-------------------------
Reporter: gk | Owner:
| pospeselr
Type: defect | Status: new
Priority: High | Milestone:
Component: Applications/Tor Browser | Version:
Severity: Normal | Resolution:
Keywords: ff60-esr, TorBrowserTeam201808, | Actual Points:
noscript |
Parent ID: | Points:
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by rustybird):
Replying to [comment:34 ma1]:
> If your XPI is a bootstrapped (legacy) extensions and does all its
initialization in its startup callback yes, it's impossible for NoScript
to be initialized first
Theoretically, Torbutton as an **un**bootstrapped / XUL overlay flavor of
legacy extension should load even earlier, right? Although I'm unfamiliar
with Torbutton's startup and don't know about the potential async
initialization work you mentioned.
Replying to [comment:33 arthuredelstein]:
> If we wanted to be absolutely sure, NoScript could be patched to listen
for a "ping" and reply with a "pong". And then torbutton could repeatedly
send "ping" (say, once a second) until it receives a "pong", and then
proceed by sending the first updateSettings message.
Sounds like an improvement. And if Torbutton accepts both "start" and the
first "pong", there wouldn't even be an up to 1 second delay (which might
be a problem if a URL is loaded quickly after browser startup, e.g. a
non-`about:` homepage).
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/26520#comment:38>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tbb-bugs
mailing list