Closed Bug 202393 Opened 17 years ago Closed 17 years ago
Add DOM class info for ns
So tree.builderView can be removed as well.
Status: NEW → ASSIGNED
Priority: -- → P5
Target Milestone: --- → mozilla1.4beta
Comment on attachment 120815 [details] [diff] [review] patch I would prefer to have the XUL stuff together in one place in ns[I]DOMClassInfo.[h|cpp] How about putting the TreeBuilder right next to its kin TreeContentView? And I would prefer TreeBuilder over XULTreeBuilder, the XUL addition seems to be only for CIs that exist in a non-XUL version, too. But those are more style issues, jst or peterv should have a real word on this. Other than that, firstname.lastname@example.org
Attachment #120815 - Flags: review?(axel) → review+
jst, peterv: I recall that new nsDOMClassInfoID records must be put at the end or am I missing something ?
Yes, we try to keep nsDOMCI binary compatible, so new stuff needs to be added at the end of that list.
Thanks, any chance to get this in for 1.4? (just asking)
I guess, this won't make 1.4
Target Milestone: mozilla1.4beta → mozilla1.5alpha
Attachment #120815 - Flags: superreview?(peterv) → superreview+
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Comment on attachment 127347 [details] [diff] [review] Supplementary patch yeah, I know I just didn't want to check it in w/o testing
Comment on attachment 127347 [details] [diff] [review] Supplementary patch sr=jag
Attachment #127347 - Flags: superreview?(jaggernaut) → superreview+
Component: XP Toolkit/Widgets: Trees → XUL
QA Contact: shrir → xptoolkit.widgets
You need to log in before you can comment on or make changes to this bug.