Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #14205

Closed (moved)
Open
Opened Jan 14, 2015 by Mike Perry@mikeperry

Closely review all uses of IsCallerChrome() for e10s

A lot of our fingerprinting patches depend upon the accuracy is nsContentUtils::IsCallerChrome() to determine if it is content window or browser chrome accessing fingerprinting information.

IsCallerChrome() kind of scares me, and has had issues for unexpected contexts like WebWorkers (See #13027 (moved)).

We should keep a close eye on this as we transition to e10s support post FF38, as who knows that the child/parent context relationship changes may do to various codepaths.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#14205