goUp command should work with page anchors (#xxx), query strings (?xxx), and sub-domains (xxx.)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Currently, the goUP command behaves unaware of page anchors (#xxx), query strings (?xxx), and sub-domains (xxx.). When first using goUP command, anchor and query is removed at along with the last part of the directory. And after using the last goUP command, sub-domains are not removed and it stays on the same URL. Lack of these features is the primary reason why I still keep the separate NavigUp extension around:
Navigate to parent address. It means removing page anchor (#xxx), query string (?xxx), file or the last directory (/xxx), port number (:xxx), sub-domain (xxx.) or secure layer (https -> http), whichever is first found (preserving mentioned order).
Removing the secure layer (https -> http) is probably unnecessary in 2021 (the extension is from 2013), but the rest I find very useful. For when you actually want to remove the achors and queries at once, the extension has additional shortcuts:
Use Alt+Up (Shift = +1, Ctrl = +2 levels) or click the icon (many times = many levels).
...
Use (Ctrl+)(Shift+)Alt+Up for it. Shift means going up one more level, Ctrl - additional two levels. Ctrl and Shift can be combined. If you click extension's icon (in the address bar) many times within one third of second, then you'll go up many levels at once.
Vimium already has this implemented in a more intuitive way (number and then the goUP command shortcut), so I would love to use that instead, if goUP is able to navigate in more parts of the URL like the NavigUp extension.
In the meanwhile, I think the goToRoot command should probably stay as it is, without stripping the subdomain, as stripping the subdomain would be achievable with a subsequent goUP command if desired.
(A portion of this potential feature was previously mentioned by one of the maintainers in #1344.)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the goUP command implementation and compare its URL handling with the existing goToRoot behavior. Use the NavigUp behavior quoted in the issue as the acceptance criteria, including anchors, query strings, directories, ports, and subdomains, while preserving goToRoot's current behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100