зеркало из https://github.com/mozilla/gecko-dev.git
6896a2d0f4
We need to implement things like https://developer.gnome.org/atk/unstable/AtkObject.html#atk-object-ref-state-set and the same basic thing on windows. That API is fundamentally sync, but the information necessary to implement it is only available in the child process. That seems to leave us with two options, either we can use sync ipc or we can use async ipc but spin a nested event loop. If we were to spin nested event loops we'd have to be careful to make sure a11y didn't do anything until the nested event loop was done, and then a11y would have to deal with whatever changed. I'm not sure that will work, and since the system is probably waiting for the accessibility information anyway I don't think we get much out of spinning the event loop. So I think its somewhat less bad to use sync ipc here. |
||
|---|---|---|
| .. | ||
| atk | ||
| base | ||
| generic | ||
| html | ||
| interfaces | ||
| ipc | ||
| jsat | ||
| mac | ||
| other | ||
| tests | ||
| windows | ||
| xpcom | ||
| xul | ||
| moz.build | ||