[perf] use private API instead of SetAttribute to maintain content construction state

RESOLVED FIXED in M11

Status

()

Core
XUL
P3
normal
RESOLVED FIXED
19 years ago
10 years ago

People

(Reporter: Chris Waterson, Assigned: Chris Waterson)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Assignee)

Description

19 years ago
currently, we set attributes in the content model to remember state for the
RDFGenericBuilder. This is surprisingly expensive. Use a private API and
booleans or a bit flag to do this instead.
(Assignee)

Updated

19 years ago
Status: NEW → ASSIGNED
Target Milestone: M11
(Assignee)

Updated

19 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED

Updated

19 years ago
QA Contact: ckritzer → waterson

Comment 1

19 years ago
Assigning to originator per new organizational structure.

Updated

18 years ago
QA Contact: waterson → ckritzer

Comment 2

18 years ago
Changing QA Contact back to ckritzer@netscape.com

Comment 3

18 years ago
BULK MOVE: Changing component from XUL to XP Toolkit/Widgets: XUL.  XUL 
component will be deleted.
Component: XUL → XP Toolkit/Widgets: XUL

Comment 4

18 years ago
Massive QA Contact update.
QA Contact: ckritzer → jrgm

Updated

10 years ago
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: jrgmorrison → xptoolkit.widgets
You need to log in before you can comment on or make changes to this bug.