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
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

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
  • #14061

Closed (moved)
Open
Opened Dec 31, 2014 by Trac@tracbot

Develop a new cookie inspector accommodating double key logic

New concept

Design and implement a cookie inspector resembling the concept graphic suggested by mikeperry: https://trac.torproject.org/projects/tor/raw-attachment/ticket/3246/NewCookieManager2.png

Existing reuse

An alternative design to be considered involves reusing the existing ESR cookie representation while adding a widget controlling indexing of cookies by 1st or 3rd party contexts: https://support.cdn.mozilla.net/media/uploads/gallery/images/2013-07-12-12-57-44-88051d.png This design could be improved by allowing quick changes of indexing via a widget directly on the cookie inspector interface.

Challenges

  • Mitigate the listing of duplicate (hidden in legacy 3rd party cookie logic) 3rd party cookies, otherwise bloating cookie lists considerably.
  • Avoid forcing the user to inspect cookies by one of 1st or 3rd party keys, and support choice of either indexing method.
  • Allow the user to find individual cookies at least as easily as preexisting representations allow, and avoid exaggerated scrolling.

Requirements

To be announced.

Trac:
Username: michael

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