Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Please start changing the UI via an XML type setting file as opposed to hardcoding it

more options

I changed to Chrome from Firefox a year or so ago primarily for performance reasons even though it felt like a major sacrifice swapping to the 'minimalist' type UI of Chrome though it wasn't too tough to mod it to an approximation of earlier versions of Firefox. Recently Chrome has swapped to a policy of automatically disabling all extensions that don't come from their store (even after users jump through all the hoops required to install/develop non-store extensions) with no way to disable said "feature" so it was time to drop them as I prefer freedom in browsers above all. Lo and behold I come back to firefox and I'm still experience a bit worse performance, but on top of it the UI is now clearly heavily influenced by exactly what I was trying to avoid with Chrome, with no straight forward means of reverting to previous Firefox UIs.

Why not simply change the UI using a sort of XML or other setting file? It'd be trivial to be backwards compatible (so long as new versions don't remove any functionality) and allow users to easily choose exactly how they want their experience to be.

Now I'm sure the answer is something like "We did user research and spent a millenia researching the new UI and even had Mohammed Ganesha Jesus himself come tell us exactly what users want so we decided to force it on everybody!" but honestly I don't really care. I like to stick to a simple dictum of "If it's not broken, don't fix it." It wasn't broken for me, so I have no interest in the fixes. I'm always enthusiastic about back end fixes, but if I'm happy with the front-end why force me to change it?

I changed to Chrome from Firefox a year or so ago primarily for performance reasons even though it felt like a major sacrifice swapping to the 'minimalist' type UI of Chrome though it wasn't too tough to mod it to an approximation of earlier versions of Firefox. Recently Chrome has swapped to a policy of automatically disabling all extensions that don't come from their store (even after users jump through all the hoops required to install/develop non-store extensions) with no way to disable said "feature" so it was time to drop them as I prefer freedom in browsers above all. Lo and behold I come back to firefox and I'm still experience a bit worse performance, but on top of it the UI is now clearly heavily influenced by exactly what I was trying to avoid with Chrome, with no straight forward means of reverting to previous Firefox UIs. Why not simply change the UI using a sort of XML or other setting file? It'd be trivial to be backwards compatible (so long as new versions don't remove any functionality) and allow users to easily choose exactly how they want their experience to be. Now I'm sure the answer is something like "We did user research and spent a millenia researching the new UI and even had Mohammed Ganesha Jesus himself come tell us exactly what users want so we decided to force it on everybody!" but honestly I don't really care. I like to stick to a simple dictum of "If it's not broken, don't fix it." It wasn't broken for me, so I have no interest in the fixes. I'm always enthusiastic about back end fixes, but if I'm happy with the front-end why force me to change it?

所有回复 (2)

more options

Please provide that feedback here, where the "decision makers" can see it. https://input.mozilla.org/en-US/feedback

more options

Firefox's UI is built with XML, CSS, and JavaScript. These files then are compressed into a JAR archive for efficiency. While it's possible to tweak the files in that archive, it is much easier to apply changes using an add-on. (Also, if you modify the JAR file, you would have to redo the changes after each update.)