Closed
Bug 1424315
Opened 8 years ago
Closed 8 years ago
Expose browser.tabs.opentabfor.middleclick via API
Categories
(WebExtensions :: Frontend, enhancement, P5)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: mconca, Unassigned)
Details
(Whiteboard: [design-decision-denied])
Add a browserSetting API to expose the about:config pref browser.tabs.opentabfor.middleclick. This allows middle click (or CTRL+click) to open new tabs. Note that this bug was branched from bug 1421447.
Recommended for discussion in design decision meeting.
| Reporter | ||
Updated•8 years ago
|
Severity: normal → enhancement
Whiteboard: [design-decision-needed]
Updated•8 years ago
|
Priority: -- → P5
Comment 1•8 years ago
|
||
Hi Mike, let's talk about this during the February 20, 2018 WebExtensions APIs triage! All who are interested in this bug are welcome to join.
Here’s a quick overview of what to expect at the triage:
* We normally spend 5 minutes per bug
* The more information in the bug, the better
* The goal of the triage is to give a general thumbs up or thumbs down on a proposal; we won't be going deep into implementation details
Relevant Links:
* Wiki for the meeting: https://wiki.mozilla.org/WebExtensions/Triage#Next_Meeting
* Meeting agenda: https://docs.google.com/document/d/1-edU5RRFo2TupsOW400AcTOj8yyQnXd0F7uSsqkEzck/edit#
* Vision doc for WebExtensions: https://wiki.mozilla.org/WebExtensions/Vision
| Reporter | ||
Comment 2•8 years ago
|
||
Hi Caitlin, I'll be there with bells on!
| Reporter | ||
Comment 3•8 years ago
|
||
Luke, I wanted to see if you still had a need for this pref to be exposed via the WebExtensions API. Even though containers found a workaround, do you still see a use case for this? Also, any idea who might own (or understand) this pref on the engineering side? I'd like to get input on the stability and supportability of the pref (i.e. is it going to be around for a while).
Flags: needinfo?(lcrouch)
Comment 4•8 years ago
|
||
I don't have any new info beyond our original Container need, sorry.
Flags: needinfo?(lcrouch)
| Reporter | ||
Comment 5•8 years ago
|
||
Closing this as WONTFIX, design-decision-denied. In a vacuum, there is no objection to exposing this pref via an API, but no viable use cases have presented themselves at this time. It doesn't make sense to increase our development, test and maintenance burden until viable market demand exists.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Whiteboard: [design-decision-needed] → [design-decision-denied]
Updated•7 years ago
|
Product: Toolkit → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•