Open Bug 539738 Opened 11 years ago Updated 4 years ago

Tree width of Preferences window has been hardcoded (need category splitter)

Categories

(SeaMonkey :: Preferences, defect)

SeaMonkey 2.0 Branch
defect
Not set
normal

Tracking

(Not tracked)

ASSIGNED

People

(Reporter: milupo, Assigned: mnyromyr)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; hsb-DE; rv:1.8.1.23) Gecko/20090825 SeaMonkey/1.1.18
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; hsb-DE; rv:1.8.1.23) Gecko/20090825 SeaMonkey/1.1.18

Th width of the tree part of the preferences window (left side of the window) has been hardcoded. Therefore localized text within this tree may not fit in the tree area of the Preferences window. The tree width has been defined with "13em", see file chrome://content/communicator/pref/preferences.xul, line 66:

style="width: 13em;"

There should be defined an entity instead of the text "width: 13em", e.g. "&preferencesTree.width". In file preferences.dtd the value should be assigned to this entity, similar to the entity "accountTree.width" in the file AccountManager.dtd for tree width of the account settings window of the Mail & Newsgroups component. 



Reproducible: Always



Expected Results:  
Contents of Preferences window tree should be customizable for localizers.
Version: unspecified → SeaMonkey 2.0 Branch
I was going to make the right edge of the preftree draggable in bug 456874, but you're right, the initial width should be localizable as well. 
I guess I'll move the whole preftree fixes here.
Assignee: nobody → mnyromyr
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
OS: Windows XP → All
Hardware: x86 → All
In SM 2.1 beta 1 the preftree width is still hardcoded. It would be good if the preftree width would be customizable for localizers in final SM 2.1.
Summary: Tree width of Preferences window has been hardcoded → Tree width of Preferences window has been hardcoded (need category splitter)
Duplicate of this bug: 80404
I rediscovered this bug. It is not fixed yet, after more than 6 years.
You need to log in before you can comment on or make changes to this bug.