[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #26545 [Applications/Tor Browser]: Investigate NoScript related errors in RequestGuard.js

#26545: Investigate NoScript related errors in RequestGuard.js
--------------------------------------+--------------------------
 Reporter:  gk                        |          Owner:  tbb-team
     Type:  task                      |         Status:  new
 Priority:  High                      |      Milestone:
Component:  Applications/Tor Browser  |        Version:
 Severity:  Normal                    |     Resolution:
 Keywords:  ff60-esr                  |  Actual Points:
Parent ID:                            |         Points:
 Reviewer:                            |        Sponsor:
--------------------------------------+--------------------------

Comment (by ma1):

 This error message just mean that the window (as identified by tabId and
 frameId) which the message was sent to doesn't exist anymore.
 Due to the asynchronous nature of all the WebExtensions API this is hardly
 an exceptional case, and it's not something which needs to be cared for
 from a security standpoint, hence the best course for me is probably
 wrapping each of the two sendMessage() calls in its try/catch block and
 just make it quiet.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/26545#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs