1479178 - Find a better way to store AccessibleNode properties

Status: RESOLVED WONTFIX

(Core :: Disability Access APIs, defect, P3)

Description

[dora.tokio]

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36



Actual results:

This is from https://bugzilla.mozilla.org/show_bug.cgi?id=1468110#c67

Comment 1

[dora.tokio]

I'd like to check just in case; what we have to consider in this bug is how to put together nsDataHashtables which have a few properties (e.g. m(Double | Int | Relation)Properties) into one hashtable? As a way of achieving this, we can use union, for example.
I personally think there is a trade-off between memory-usage and search speed of hashtable. Is it worth compiling those properties even if it would lead to the lowering of search speed?

Comment 2

[alexander :surkov (:asurkov)]

My primary concern is it'd be good to reduce memory usage when the properties are not used. It's basically why we proceeded with hash tables approach; despite the hash tables are slower than direct access as Olli pointed out. So if we have multiple tables, then it will have higher memory usage. 

I'm not sure I follow why union usage in a hash table would mean lower search speed?

Comment 3

[James Teh [:Jamie]]

AccessibleNode is from an old version of the AOM spec. It's possible we may need something similar when we get to virtual a11y nodes, but until that is actually specified, we really have no idea. Closing for now.