al_9x wrote:Classic Theme Restorer is probably the best canary in the coal mine for these changes, because it radicallyunfuckstweaks post australis ui, through xul, css and javascript hacks that mozilla is not likely to acknowledge as needed (that would mean admitting they've been making things worse for years)
The author of CTR is not optimistic about its future:
Where is this discussion happening? Could you please post some links for me to partecipate?
al_9x wrote:@Giorgio Does your optimism extend to CTR?
Of course it does.
al_9x wrote: If so, on what basis?
- My native.js approach, which is linked from the WebExtensions FAQ itself and called by the lead developer of the WebExtensions APIs "a good proposal I'd like to start prototyping soon", allows add-ons to do everything the browser (whose front-end is going to be still coded in JavaScript for any foreseeable future) can do: you will have different but not less powerful ways to customize any aspect of the UI.
- Even before native.js was proposed, UI customization APIs have been planned as first-class citizens of the Firefox-specific part of the WebExtensions API:https://wiki.mozilla.org/Browser_Extensions#Additional_APIs wrote:
- Sidebars. Opera already supports sidebar functionality; Chrome may soon. We would like to be able to implement Tree Style Tabs or Vertical Tabs by hiding the tab strip and showing a tab sidebar.
- Toolbars. Firefox has a lot of existing toolbar add-ons.
- Better keyboard shortcut support. We'd like to support Vimperator-type functionality.
- Ability to add tabs to about:addons.
- Ability to modify the tab strip (Tab Mix Plus).
- I'm quite confident that UI customization is going anyway to be even easier than before, since everything (and especially Firefox OS) suggests that the replacement for XUL is HTML5.