74371 2011-12-12 17:00:01 -0800 Need data on whether we can implement DOM4 attribute objects 2023-12-29 03:05:03 -0800 1 1 1 Unclassified WebKit DOM 528+ (Nightly build) Unspecified Unspecified RESOLVED CONFIGURATION CHANGED P2 Normal --- 1 ojan webkit-unassigned adamk annevk ap arv darin mjs rafaelw rniwa sam skyul syoichi oldest_to_newest 519696 0 ojan 2011-12-12 17:00:01 -0800 DOM4 considerably simplifies Attrs (http://www.w3.org/TR/domcore/#interface-attr). DOM2 has them be full-fledged Nodes. We need data on how safe implementing DOM4's version will be. If someone instruments Node to log to Chromium histograms everytime an API is used on an Attr, then we can get data and make informed decisions. The new API is 1000x better, so the more of it we can implement the better. The parts we're worried about implementing should be brought up on www-dom@. 520201 1 ap 2011-12-13 11:11:39 -0800 > The new API is 1000x better For completeness, could you explain some ways in which it is better? 520213 2 ojan 2011-12-13 11:26:01 -0800 The main difference is that they are not Nodes anymore. They are (hopefully) just the minimal interface required by web compat. This makes Attrs a lot lighter-weight (e.g. don't need to have member variables for child nodes) and gets rid of non-sensical APIs (e.g. appendChild to an Attr). In terms of WebCore implementation, it may eventually allow us to remove the distinction between Attrs and Attributes. 523131 3 ap 2011-12-16 16:05:21 -0800 One place where attribute nodes are particularly visible in the platform is XPath. 2002209 4 annevk 2023-12-29 03:05:03 -0800 This is more or less complete now. Any further improvements should have more detailed bugs.