I discussed with Paolo a plan to improve the usage of restriction characters in the Location Bar: 1. bug 1376986: remove the ability to define them with prefs. This will simplify the management code and give us some more space for improvements. 2. remove the less useful ones. For example "typed" makes no sense, the user is unlikely to remember whether a page was typed, especially since we define typed in some fancy way. 3. Change the search token from "$" to "?". 4. Fix bug 1177895, bug 1315509, bug 1334019 5. make more natural to type these, for example typing a question mark just after a word, like "mozilla?" should match only search results for "mozilla" and not try to search "mozilla?". Same for "?mozilla". This requires some checks to avoid confusing urls for which the token may be a valid char.
I think this is a P3, unless it is blocking or otherwise impacting other work, or is a very simple fix.
I looked at the dependencies and tend to agree. This was likely intended as a meta-bug, I'm marking it as P2 as some dependencies like bug 1334019 are also marked as P2. We can likely adjust later with Marco.
Priority: P1 → P2
Summary: Improve restriction characters in the Location Bar → [meta] Improve restriction characters in the Location Bar
You need to log in before you can comment on or make changes to this bug.