Open
Bug 1431840
Opened 6 years ago
Updated 2 years ago
Support "beforeCurrent" as an option to browserSettings.newRelatedTabPosition and newUnrelatedTabPosition
Categories
(WebExtensions :: General, enhancement, P3)
Tracking
(firefox59 affected)
NEW
Tracking | Status | |
---|---|---|
firefox59 | --- | affected |
People
(Reporter: mconca, Unassigned)
References
(Blocks 1 open bug)
Details
Bug 1344749 implemented browserSettings.newRelatedTabPosition and browserSettings.newUnrelatedTabPosition with support for "afterCurrent" and "endOfTabStrip". This bug is to add support for "beforeCurrent" to those two API.
Comment 1•6 years ago
|
||
The use case for this seems rather vague; I don't fully understand bug 1344749 comment 40. As it stands I don't think we should do this.
Updated•6 years ago
|
Priority: -- → P2
Reporter | ||
Comment 2•6 years ago
|
||
(In reply to Dão Gottwald [::dao] from comment #1) > The use case for this seems rather vague; I don't fully understand bug > 1344749 comment 40. As it stands I don't think we should do this. The use case is vertical tabs (or tree tabs, or any alternate tab model implemented in sidebars instead of across the top). In these cases it is often more intuitive for users to have the new tab appear at the top of the tab list, which would be "before" any existing tabs.
Comment 3•6 years ago
|
||
What prevents those extensions from treating "afterCurrent" or "endOfTabStrip" as "above the current subtree" or "at the top of the tree", respectively? This doesn't seem like something that should reflect back to the API.
Comment 4•6 years ago
|
||
CSS order[1] should be able to handle the use case from comment 2, assuming the sidebar wants the same order (just reversed) as the tabstrip. Assuming tab is in a tabs array, one could do a little calculation like: tab.style.order = tabs.length - tab.index Given that, I don't think there is anything to do here. If the use case is to cover the firefox tabstrip, then it might need to be implemented in tabbrowser.
Flags: needinfo?(mconca)
Reporter | ||
Comment 5•6 years ago
|
||
The use case is to offer a complete tab positioning API to developers that allows them to offer opening positions of before, after and end-of-strip, for the Firefox tabstrip as well as any other alternate tab model. Since bug 1344749 hasn't hit release yet, let's wait for developer feedback on this feature request.
Flags: needinfo?(mconca)
Reporter | ||
Updated•6 years ago
|
Priority: P2 → P3
Updated•6 years ago
|
Product: Toolkit → WebExtensions
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•