6 ms·

I don't understand why they don't just create an API that allows extensions to modify userChrome.css. It seems like this would solve a lot of the complaints peo

by jamoes 9y ago

I don't understand why they don't just create an API that allows extensions to modify userChrome.css. It seems like this would solve a lot of the complaints people have about the new extension framework, and it would be a way better experience for non-tech-savvy users.

devit 9y ago
Probably because any change to the Firefox UI would potentially break an extension using such an API, and part of the point of switching to WebExtensions is to have extensions that never break. Also, such an API would allow an extension to make the browser UI unusable, which would make figuring out the problem and removing the offending extension quite hard.
the8472 9y ago
Mozilla basically titled the security vs. versatility balance massively in the direction of security with no sudo-equivalent for AMO-distributed addons.
baby 9y ago
because they're inconsiderate of Tree Style Tab users. They could really well include a setting to disable the tab bar on top, but they're not doing it. There are no security reasons for not having such a setting. None.
- Manishearth 9y ago
  Tree Style Tabs is used by like half the folks working at Mozilla. I doubt that's the reason.
  - baby 9y ago
    For some reason I really doubt that statement.
    - Manishearth 9y ago
      I work at Mozilla.
      - nol13 9y ago
        The other half use tab center?
        Manishearth 9y ago
        shrug lots of folks don't use tab addons. But yes, Tab Center (Redux) is significantly used too.
        baby 9y ago
        maybe a bit of dogfooding and getting everyone to try tree style tabs would help make Firefox a better browser.
      - baby 9y ago
        Then care to explain why we still can't hide the top bar as a setting?
        ripdog 9y ago
        It's happening (as a WE API) but it's taking a while because they're doing it properly, and a lot of the browser expects the tab bar to be visible.
        Manishearth 9y ago
        Folks are working on it, I've been part of a couple of discussions about this. https://bugzilla.mozilla.org/show_bug.cgi?id=1332447 https://bugzilla.mozilla.org/show_bug.cgi?id=1332447 This comment kinda sums up why it's a hard problem https://bugzilla.mozilla.org/show_bug.cgi?id=1332447#c116 https://bugzilla.mozilla.org/show_bug.cgi?id=1332447#c116 There's a major problem with addons doing stuff the users don't want, and the tab strip is a critical portion of the user interface so "just let them hide it" has problems with abuse. So it needs to be something that can still be autoreviewed, and it needs to be something that gives clear indications to the user as to what is going on.
- PurpleRamen 9y ago
  They work on it. The main problem is simply that Mozilla fucked up the transition from legacy addons to the new system. There are so many APIs and functionallity still missing, that most commercial companys would have been killed over it. But with OpenSource this has become kind of normal to accept it. Just Remember KDE 3 -> 4. Python 2 -> 3. Gnome 1 -> 2 -> 3. Breaking things is just to common now.

by jamoes 9y ago

devit 9y ago

Probably because any change to the Firefox UI would potentially break an extension using such an API, and part of the point of switching to WebExtensions is to have extensions that never break. Also, such an API would allow an extension to make the browser UI unusable, which would make figuring out the problem and removing the offending extension quite hard.

the8472 9y ago

Mozilla basically titled the security vs. versatility balance massively in the direction of security with no sudo-equivalent for AMO-distributed addons.

baby 9y ago

because they're inconsiderate of Tree Style Tab users. They could really well include a setting to disable the tab bar on top, but they're not doing it. There are no security reasons for not having such a setting. None.

Manishearth 9y ago
Tree Style Tabs is used by like half the folks working at Mozilla. I doubt that's the reason.
- baby 9y ago
  For some reason I really doubt that statement.
  - Manishearth 9y ago
    I work at Mozilla.
    - nol13 9y ago
      The other half use tab center?
      - Manishearth 9y ago
        shrug lots of folks don't use tab addons. But yes, Tab Center (Redux) is significantly used too.
        baby 9y ago
        maybe a bit of dogfooding and getting everyone to try tree style tabs would help make Firefox a better browser.
    - baby 9y ago
      Then care to explain why we still can't hide the top bar as a setting?
      - ripdog 9y ago
        It's happening (as a WE API) but it's taking a while because they're doing it properly, and a lot of the browser expects the tab bar to be visible.
      - Manishearth 9y ago
        Folks are working on it, I've been part of a couple of discussions about this. https://bugzilla.mozilla.org/show_bug.cgi?id=1332447 https://bugzilla.mozilla.org/show_bug.cgi?id=1332447 This comment kinda sums up why it's a hard problem https://bugzilla.mozilla.org/show_bug.cgi?id=1332447#c116 https://bugzilla.mozilla.org/show_bug.cgi?id=1332447#c116 There's a major problem with addons doing stuff the users don't want, and the tab strip is a critical portion of the user interface so "just let them hide it" has problems with abuse. So it needs to be something that can still be autoreviewed, and it needs to be something that gives clear indications to the user as to what is going on.
PurpleRamen 9y ago
They work on it. The main problem is simply that Mozilla fucked up the transition from legacy addons to the new system. There are so many APIs and functionallity still missing, that most commercial companys would have been killed over it. But with OpenSource this has become kind of normal to accept it. Just Remember KDE 3 -> 4. Python 2 -> 3. Gnome 1 -> 2 -> 3. Breaking things is just to common now.