The default bug view has changed. See this FAQ.

Status

()

Toolkit
WebExtensions: Frontend
2 months ago
2 days ago

People

(Reporter: mikedeboer, Unassigned)

Tracking

(Depends on: 14 bugs, Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: triaged, URL)

(Reporter)

Description

2 months ago
Main tracking bug for all feature development related the a new theming API that will become part of Firefox.
Each epic will be marked as blocking this bug. You can find the full engineering document that lists these epics at [see URL field].

This bug can be closed once all epics are complete (and linked bugs are closed as well).
(Reporter)

Updated

2 months ago
Depends on: 1330335
Depends on: 1330338

Updated

2 months ago
Blocks: 1329713
Depends on: 1319821

Updated

2 months ago
Depends on: 1320736

Updated

2 months ago
Whiteboard: triaged
Depends on: 1335171
(Reporter)

Updated

2 months ago
Depends on: 1337334
(Reporter)

Updated

2 months ago
Depends on: 1337335

Updated

a month ago
Depends on: 1339131
(Reporter)

Updated

a month ago
No longer depends on: 1339131

Comment 1

a month ago
Will the theming api, or any other planned/approved api, allow either of the following?

* Hiding core ui elements (e.g. tab bar, navigation and menu bar)
* Defining a new ui element that can expand/overlay the main page and be controlled by a web extension

Both of these features are required to port vimperator, a somewhat popular addon that essentially replaces firefox's UI.

The latter capability would be used to draw the command/statusline (needs to expand to show autocomplete options). It is not sufficient to draw the statusline in a content script whilst content scripts are forbidden for some URLs as that would make the main UI element unusable on some pages.

Digression:

:kmag suggests in another bug that permitting content scripts to run on about:downloads is "out of the question", and I understand the motivation, but this will make it difficult for addons that replace or augment the UI (through differing keybinds or new features (e.g. hint mode)) to provide a consistent UX.

Our preferred solution is that content scripts be permitted to run on all tabs iff the user agrees to some scarily named permission and the developer pinky swears they'll be careful and not use exposed attributes that they shouldn't.

Thanks for your attention and apologies if this is the wrong place for this question.
Flags: needinfo?(mdeboer)
(Reporter)

Comment 2

a month ago
Hi Colin, thanks for being interested! I'm afraid this is indeed not the right venue for these kind of questions. We're planning to send out a comprehensive blog mailing list(s) post that explains what the new Theming API will and will not support when the first version ships.
Please stay tuned and feel free to ask any question you might have then. Thanks!
Flags: needinfo?(mdeboer)

Comment 3

a month ago
Thanks for the information. Looking forward to it.

Sorry about polluting this bug.

NNTR.
Depends on: 1341722
Depends on: 1343921

Updated

21 days ago
Depends on: 1320585

Updated

12 days ago
Depends on: 1333953
(Reporter)

Updated

12 days ago
No longer depends on: 1333953
(Reporter)

Updated

12 days ago
Depends on: 1347166
(Reporter)

Updated

12 days ago
Depends on: 1347171
(Reporter)

Updated

12 days ago
Depends on: 1347201
(Reporter)

Updated

12 days ago
Depends on: 1347205

Updated

10 days ago
Depends on: 1348034

Updated

10 days ago
Depends on: 1348039

Updated

10 days ago
No longer depends on: 1348039

Updated

10 days ago
Depends on: 1348147

Updated

10 days ago
Depends on: 1348151

Updated

9 days ago
No longer depends on: 1348151

Updated

9 days ago
Depends on: 1348151

Updated

9 days ago
No longer depends on: 1348151
Depends on: 1350356
You need to log in before you can comment on or make changes to this bug.