Skip to content

Enhance support for different profiles #9

Description

@artob

Use case

URIs/IRIs don't support unencoded spaces, so "chrome://bookmarks/Profile 1" can't be supported as an input URL. Meanwhile, "chrome://bookmarks/Profile%201" ("%20" being a URL-encoded space), while correct, is quite baroque and cumbersome for users. The "chrome://bookmarks/Profile+1" variant ("+" being a plus-encoded space) is also not standards conformant, since pluses are only allowed in form data, not path components.

As there is no particular precedent here to adhere to given browsers themselves don't currently support addressing a particular profile in this way, let's simplify and make our structure chrome://bookmarks/N where "N" is a number addressing a specific profile number from 1 (the default) to N.

At the same time, let's make sure that chrome://bookmarks exports all bookmarks from all profiles.

Proposal

  • chrome://bookmarks: the union of all bookmarks from all profiles
  • chrome://bookmarks/1: only the bookmarks from the "Profile 1" (or "Default") profile
  • chrome://bookmarks/2: only the bookmarks from the "Profile 2" profile

Note that the underlying folder name of the default profile seems to vary between different browsers as either "Default" or "Profile 1".

@race-of-sloths invite

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Fields

No fields configured for Feature.

Projects

Status
In progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions