Closed Bug 283678 Opened 20 years ago Closed 20 years ago

Serif / Sans-serif pref ui doesn't work anymore

Categories

(Firefox :: Settings UI, defect)

defect
Not set
major

Tracking

()

RESOLVED FIXED
Firefox1.5

People

(Reporter: asaf, Assigned: asaf)

References

Details

(Keywords: regression)

Attachments

(1 file, 2 obsolete files)

That's becuase the new pref code has overwritten the changes from bug 95227.
Severity: normal → major
Flags: blocking-aviary1.1?
What do I need to change?
Attached patch patch (obsolete) — Splinter Review
Assignee: bugs → bugs.mano
Status: NEW → ASSIGNED
Attachment #175720 - Flags: review?(bugs)
Comment on attachment 175720 [details] [diff] [review] patch >Index: components/preferences/fonts.js >=================================================================== ... > if (!preference) { > preference = document.createElement("preference"); > var name = prefs[i].format.replace(/%LANG%/, aLanguageGroup); > preference.id = name; >- preferences.appendChild(preference); > preference.name = name; > preference.type = prefs[i].type; >+ preferences.appendChild(preference); > } (This change should fix bug Bug 283869, not sure).
Blocks: 283869
(this one, bug 283869, bug 283945)
Attachment #175720 - Attachment is obsolete: true
Attachment #175760 - Flags: review?(bugs)
Attachment #175720 - Flags: review?(bugs)
Comment on attachment 175760 [details] [diff] [review] font dialog regressions - combined patch > var name = prefs[i].format.replace(/%LANG%/, aLanguageGroup); > preference.id = name; >- preferences.appendChild(preference); > preference.name = name; > preference.type = prefs[i].type; >+ preferences.appendChild(preference); Why did you do this? How can this work? You can't access the XBL properties on the preference element until after it has been inserted into the document...
well, this was working...(In reply to comment #5) > (From update of attachment 175760 [details] [diff] [review] [edit]) > > var name = prefs[i].format.replace(/%LANG%/, aLanguageGroup); > > preference.id = name; > >- preferences.appendChild(preference); > > preference.name = name; > > preference.type = prefs[i].type; > >+ preferences.appendChild(preference); > > Why did you do this? Apparently, without applying the type/name to the |preference| binding before it's initialized, it (the binding) doesn't behave properly (i.e. bug 283869). > How can this work? You can't access the XBL properties on > the preference element until after it has been inserted into the document... Although it was working... I'll change the type/name sets to |setAttribute| once i get home.
Curious. Yes, change to setAttribute to be on the safe side, then r=ben@mozilla.org
marking r= based on comment 7
Attachment #175760 - Attachment is obsolete: true
Attachment #175816 - Flags: review+
Attachment #175760 - Flags: review?(bugs)
Checking in content.js; /cvsroot/mozilla/browser/components/preferences/content.js,v <-- content.js new revision: 1.7; previous revision: 1.6 done Checking in content.xul; /cvsroot/mozilla/browser/components/preferences/content.xul,v <-- content.xul new revision: 1.4; previous revision: 1.3 done Checking in fontbuilder.js; /cvsroot/mozilla/browser/components/preferences/fontbuilder.js,v <-- fontbuilder.js new revision: 1.3; previous revision: 1.2 done Checking in fonts.js; /cvsroot/mozilla/browser/components/preferences/fonts.js,v <-- fonts.js new revision: 1.3; previous revision: 1.2 done Checking in fonts.xul; /cvsroot/mozilla/browser/components/preferences/fonts.xul,v <-- fonts.xul new revision: 1.3; previous revision: 1.2 done
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Flags: blocking-aviary1.1?
Resolution: --- → FIXED
Target Milestone: --- → Firefox1.1
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs, filter on "beltznerLovesGoats" to get rid of this mass change
QA Contact: mconnor → preferences
Depends on: 347415
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: