These are all conditional uses of ALLOW_COMPILER_WARNINGS=True that are no
longer necessary.
--HG--
extra : rebase_source : e654fa940aed18b1d5ef7b2bebb45bbef59cfd84
For now this isn't really different from the class used to wrap
HyperTextAccessibles. However we will need to store extra data to map IDs to
accessibles when we implement events.
This probably should never happen, but it seems to sometimes in the wild, and
its hard to know what caused that without a test case. So for now work around
the issue by adding a null check.
In theory this should be the same, but slightly faster than checking there is
one child and it is a document. However it appears ChildCount() sometimes
returns 1 when there is no child 0.
The patch removes 455 occurrences of FAIL_ON_WARNINGS from moz.build files, and
adds 78 instances of ALLOW_COMPILER_WARNINGS. About half of those 78 are in
code we control and which should be removable with a little effort.
--HG--
extra : rebase_source : 82e3387abfbd5f1471e953961d301d3d97ed2973
The NSAccessibilityHelpAttribute is being repurposed here, too, to expose the information other platforms call the Accessible Description rather than the Accessible Help tag, which traditionally referred to a connection to a Windows help file in old MSAA.
--HG--
extra : commitid : It2o0CiKUxb
extra : rebase_source : 06f20dcafbb937f103a3ed3de5681576518c037e
interfaces is supposed to be a bit mask indexed by MAI_INTERFACE_X, so when
adding interfaces MAI_INTERFACE_X should be used as an index of the bit to set,
not the mask to add.
Soon we will need to be able to update the text change event data from both
HandleAccEvent() and ProxyTextChangeEvent(), so separate out the logic to do
that into a function.
HyperTextAccessibleWrap r=davidb
This is rather unfortunate, AccessibleWrap itself wastes a fair amount of space
when it just stores a pointer to a proxy, and this makes it waste even more.
However this is rather necessary for now because we need to be able to downcast
classes such as ia2AccessibleText to one type that works both when the
accessible is pointing to a proxy and when it is not. That means
HyperTextAccessibleWrap and HyperTextProxyAccessibleWrap need to have the same
layout.
Having one reorder event that superseeds another does not mean that the
dependant mutation events for the first reorder are obsolete. So we if we
coalesce a reorder event away we should leave its subordinate mutation events
alone.
Trevor Saunders
Shu-yu Guo
Alexander Surkov
Eitan Isaacson
Nicholas Nethercote
Wes Kocher
Masayuki Nakano
Olli Pettay
Marco Zehe
Chris Peterson
Ryan VanderMeulen