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

Re: [tor-bugs] #6280 [EFF-HTTPS Everywhere]: https-everywhere.js:434 - lst is null

#6280: https-everywhere.js:434 - lst is null
-------------------------------------+--------------------------------------
    Reporter:  grarpamp              |       Owner:  pde   
        Type:  defect                |      Status:  closed
    Priority:  normal                |   Milestone:        
   Component:  EFF-HTTPS Everywhere  |     Version:        
  Resolution:  fixed                 |    Keywords:        
      Parent:                        |      Points:        
Actualpoints:                        |  
-------------------------------------+--------------------------------------
Changes (by pde):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 That's a particularly hacky code path. It attempts to work out which
 windows requests pertain to in order to poplulate the HTTPS Everywhere
 context menu correctly. Although I can't reproduce this error, I'm not
 totally surprised that it happens and it could do nasty things to the UI.

 It therefore makes sense to handle a null value for lst more gracefully.
 [https://gitweb.torproject.org/https-
 everywhere.git/commitdiff/5a13a7b217544b9c7052785ec1a699de1700046c Done].

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6280#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