Open
Bug 1280086
Opened 8 years ago
Updated 2 years ago
Child process shouldn't send events to parent if a11y isn't enabled in parent
Categories
(Core :: Disability Access APIs, defect, P3)
Core
Disability Access APIs
Tracking
()
NEW
People
(Reporter: lsocks, Unassigned)
Details
Attachments
(1 file)
6.00 KB,
patch
|
tbsaunde
:
review+
|
Details | Diff | Splinter Review |
Child process will try to send IPC messages to parent when parent process doesn't have a11y enabled but child does (e.g. marionette-e10s tests)
Reporter | ||
Comment 1•8 years ago
|
||
Assignee: nobody → lorien
Attachment #8762717 -
Flags: review?(tbsaunde+mozbugs)
Reporter | ||
Updated•8 years ago
|
Summary: Child process shouldn't send IPC messages if a11y isn't enabled in parent → Child process shouldn't send events to parent if a11y isn't enabled in parent
Comment 2•8 years ago
|
||
Comment on attachment 8762717 [details] [diff] [review] check if a11y is enabled in parent first before sending events r=me with the first comment fixed. > Accessible::HandleAccEvent(AccEvent* aEvent) > { > NS_ENSURE_ARG_POINTER(aEvent); > >- if (IPCAccessibilityActive() && Document()) { >+ if (IPCAccessibilityActive() && Document() && GetAccService()->IsEnabledInChrome()) { you missed the IPCAccessibilityActive() check in DocManager.cpp which would have the effect of not creating any DocAccessibleParents (the NotificationController change prevents sub document ones). >+ >+ virtual void SetEnabledInChrome() = 0; could use a comment. Also yuk this interface should be merged with nsAccessibilityService itself, but that requires either a static cast or fixing how the service is started which I don't think needs to be done now.
Attachment #8762717 -
Flags: review?(tbsaunde+mozbugs) → review+
Updated•8 years ago
|
Priority: -- → P2
Updated•8 years ago
|
Priority: P2 → P3
Updated•2 years ago
|
Assignee: lorien → nobody
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•