Just a suggestion to swap File Types, which is currently under Content, with Languages, which is currently under Advanced. Basically, I think Languages shouldn't be hidden under Advanced, and it's more closely related to the Fonts section than anything else. File Types should be next to Downloads if anything, but it's a pretty technical (advanced) topic. IMHO.
OS: Linux → All
Hardware: PC → All
Version: unspecified → Trunk
File Types has just been moved to its own Applications pane, so there is now plenty of room in the Contents pane. In Languages the user says which language he wants the content (!) to be displayed in, and in Fonts & Colors, in which font, size and color. That belongs together. Fonts & Colors and Languages were already next to each other in Firefox 1.0, in the General section. But in Firefox 1.5, there wasn't enough space in the Content pane. Beltzner, what do you think?
Summary: swap File Types with Languages in preferences dialog → move Languages from Advanced to Content, below Fonts & Colors, in preferences dialog
Yeah, this is a good idea.
Flags: blocking-firefox3? → blocking-firefox3+
Created attachment 283330 [details] [diff] [review] move it
I fixed the indentation in content.dtd in my tree.
Comment on attachment 283330 [details] [diff] [review] move it r=mano
Attachment #283330 - Flags: review?(mano) → review+
Comment on attachment 283330 [details] [diff] [review] move it Beltzner already agreed in comment 2, so seeking approval.
Comment on attachment 283330 [details] [diff] [review] move it ui-r+a=me (fwiw, "yeah, we should do this" and marking blocking is pretty much ui-r already ;))
Status: ASSIGNED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
Target Milestone: Firefox 3 M10 → Firefox 3 M9
verified using Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9b3pre) Gecko/2007122704 Minefield/3.0b3pre on Fedora 8 and Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b3pre) Gecko/2007122704 Minefield/3.0b3pre -> Verified fixed
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.