J.B. Moreno wrote: >Yes, it is *user*Content.css -- but that doesn't mean that the standard >distribution shouldn't install it by default, with some sensible >values. > I agree that we should install it by default, but empty. This file is only for stuff in the app that the user wants to *override*, not for adding features. Otherwise, we will add more and more to it and the user will be overwelmed, scared to break something or to add his own rules (or delete some), while the file is indeed for him.
>I (at least) think of it as a type of preference file -- and I think >that's liable to be a common view. If it is, then it should be >installed, with defaults to what most people will want. > Not that our pref defaults aren't in user.js either. userContent.css is the equivalence of user.js. >And this is a great example of that, most people *will* want to have >quoted text colored, > I am not sure. In any case, they will not all agree on the same colors. You cannot assume that users will edit a text file to set prefs, so telling them to edit the values in userContent.css, just so they can use the colors they like, is not good IMO. IMO, adding a prefs UI is the right way to go. Waiting for Jen's reply... (However, I don't know, if I will implement that myself. I will surely give detailed instructions of how I think the "bug" should be fixed.) Ben
