Bug 82119 - ReadOnly state in DOM should be "pay as you go"
Summary: ReadOnly state in DOM should be "pay as you go"
Status: NEW
Alias: None
Product: WTP Source Editing
Classification: WebTools
Component: wst.sse (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: David Williams CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted, performance
Depends on:
Blocks:
 
Reported: 2005-01-03 22:14 EST by David Williams CLA
Modified: 2007-09-13 03:18 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2005-01-03 22:14:57 EST 
Currently the read-only controller in XMLNode's *always* traverses nodes to keep
read-only state accurate. See for example 	
syncChildEditableState(Node child)
in NodeContainer

If there is never any read-only nodes in document, this can cause *lots* of
extra DOM traversals. 

While these ultimately result in "no-ops", so not too expensive, for large
documents, with lots of elements, can result in a million "no-ops" for no good 
reason. 

A better design would be to quickly decide to do nothing, until at least 
one node was set to be read-only.
Comment 1 Tod Creasey CLA 2005-03-07 11:57:14 EST 
Adding my name to the cc list as we are now tracking performance issues more
closely. Please remove the performance keyword if this is not a performance bug.