mirror of
https://github.com/imputnet/helium.git
synced 2026-11-17 18:59:24 +00:00
[FR]: Browser Windows Should Have Roles and Weights: A Design Idea #2549
Labels
No labels
approved
approved
approved
bad ux
bot:review
bot:size
bug
bug
bug
can't replicate
can't replicate
can't replicate
confirmed
confirmed
confirmed
external
feat
feat
feat
good first issue
good first issue
good first issue
invalid
invalid
invalid
needs more info
needs more info
needs more info
pending
pending
pending
upstream
upstream
upstream
WAI
WAI
WAI
wontfix
wontfix
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
imputnet/helium#2549
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
Browser windows should be like different workspaces with their own roles and priorities, keeping the main one focused while temporary content goes where it belongs, all shaped by what you’re doing.
Who's implementing?
The problem
Browser Windows Should Have Roles and Weights: A Design Idea
This post is to share a feeling I’ve had after using browsers for a long time. It’s not a feature request, more of a design direction. If it resonates, I’d be happy to discuss.
The problem I run into
I usually keep a main browser window on the left, basically fixed, for my main workflow. On the right, I keep a secondary window for temporary searches, external links, and quick lookups. Some high-frequency apps become PWAs on the desktop. Ideally, I’d also have a window tucked at the edge of the screen that slides out when I move my mouse there.
But browsers treat all of these as the same kind of window. A new link steals focus. A quick search interrupts the main workflow. External links enter the main tab system and pollute the current context. Then I have to
Ctrl+Tabback.Arc’s Little Arc made me realize something: it’s useful not because it’s “small,” but because it’s low-weight — temporary, doesn’t steal focus, doesn’t enter the main tab system, previewable, promotable, disposable.
Core idea: separate form and weight
A window has two dimensions:
Today browsers mostly distinguish only “window” and “tab,” without defining window roles. So by default, every new window becomes the same thing: steals focus, takes a taskbar slot, enters the tab system, and needs manual management.
If the “low-weight” idea behind Little Arc became a general capability, and different windows could have different weights, this would feel much better.
Window roles
Key capabilities: which role new links go to by default; whether they can open in the background without stealing focus; whether they can be promoted to Anchor or pinned as a PWA with one action; whether they can be demoted, archived, or moved across windows; whether identity is shared cookies or isolated.
Contexts
Right now Profile, Workspace, Window, Little Arc, PWA, and Air Traffic Control are fragmented: Profile handles identity, Workspace handles tab grouping, Window handles display, Little Arc handles low-weight temporary content, PWA handles desktop-ification, and Air Traffic Control handles part of routing.
But what users actually face is a task context: work, reading, temporary. In that context, identity, windows, routing, focus, lifecycle, and layout are all connected.
For example, a “Work context”: Anchor on the left with company dashboards, email, and docs; Scratch on the right for external links, quick searches, and ChatGPT; Shelf for calendar and todos; Slack and Notion as PWAs in the Dock; company domains go to Anchor, external docs go to Scratch, searches go to Peek; Scratch doesn’t steal focus from Anchor by default.
A “Reading context” looks different: Anchor for the article, Shelf for notes, Peek for dictionary lookups, PWAs for read-later and Readwise.
This is closer to real tasks than just managing profiles.
Understanding it as layers
It helps to break it into L0–L5:
Today’s products cover only some of these layers, and they don’t connect. Profile covers L0. Workspace covers part of L1. Window covers L5. Little Arc covers part of L2 and L4. Ideally, one “context” would include all of them.
Routing can be more fine-grained
Based on source, URL, and current context, decide: which window role, whether to steal focus, which identity, how long it lives, and which screen it goes to.
For example:
Minimum prototype
If starting with a minimum version:
Prove that “window roles + focus protection + low-weight temporary windows” are valuable first, then build up.
Questions to discuss
One-line summary
I don’t want more windows. I want a window system with roles, weights, and routing rules. Generalize Little Arc’s “low-weight” idea, then use contexts to unify identity, routing, focus, and lifecycle.
If this direction seems useful, I’d love to hear your thoughts.
Disclosure: This article was polished with AI assistance.
Possible solutions
This is an idea-level proposal, not a concrete spec. The core direction is to give windows roles and weights, keep the main window focus-protected, and route new links by context to Scratch / Peek / Shelf / PWA / Ghost. A minimal starting point could be: Anchor + Scratch, background open without focus steal, a shortcut to promote Scratch to Anchor, and a simple routing table.
Additional context
No response
This issue appears to combine separate feature requests. Could you keep this issue focused on one request and open another issue for the other? If we have misunderstood the scope, please let us know.