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

Re: [tor-bugs] #19048 [Applications/Tor Browser]: Review Firefox Developer Docs and Undocumented bugs since FF45esr



#19048: Review Firefox Developer Docs and Undocumented bugs since FF45esr
-------------------------------------------------+-------------------------
 Reporter:  gk                                   |          Owner:  tbb-
                                                 |  team
     Type:  task                                 |         Status:  new
 Priority:  Medium                               |      Milestone:
Component:  Applications/Tor Browser             |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  ff52-esr, tbb-7.0-must,              |  Actual Points:
  TorBrowserTeam201703, GeorgKoppen201703        |
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
                                                 |  Sponsor4
-------------------------------------------------+-------------------------

Comment (by gk):

 Replying to [comment:17 mcs]:
 > Replying to [comment:15 gk]:
 > > Replying to [comment:9 mcs]:
 > > > e) window.showModalDialog() is not available when e10s is enabled.
 Should we always make it unavailable (even when e10s is disabled)? Or
 maybe we don't care because we will probably enable e10s for all Tor
 Browser users or none.
 > > > https://bugzilla.mozilla.org/show_bug.cgi?id=1234700
 > >
 > > I think we should not care. Besides that it seems that non of our code
 is using `showModalDialog()` anyway.
 >
 > Okay. Kathy and I were thinking about regular web pages using that API
 and/or detecting that it is not available. But there are probably other
 ways to detect that e10s is enabled.

 I made a note in #21432. Maybe we find some good solution to the "e10s and
 fingerprinting" issue.

 > > > h) We will need to set `network.dns.blockDotOnion = false`.
 > >
 > > Hm. You mean for the transparent proxying option?
 >
 > I was thinking that the Firefox code would block .onion requests even
 when they go through the SOCKS proxy. But you may be correct.

 I opened #21674 for investigating this.

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