If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

remove MAI logging

RESOLVED FIXED in mozilla20

Status

()

Core
Disability Access APIs
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: tbsaunde, Assigned: tbsaunde)

Tracking

(Blocks: 1 bug)

unspecified
mozilla20
All
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

5 years ago
I've never used this and I suspect nobody else has in a while either.  If anyone does need this stuff logged we should add generic a11y logging instead of atk only logging.
(Assignee)

Comment 1

5 years ago
Created attachment 687915 [details] [diff] [review]
patch
Attachment #687915 - Flags: review?(surkov.alexander)

Comment 2

5 years ago
Comment on attachment 687915 [details] [diff] [review]
patch

Review of attachment 687915 [details] [diff] [review]:
-----------------------------------------------------------------

Neither I aware of usecase of it. I agree it should be easy to recreate it by a11y logging system if needed.
Attachment #687915 - Flags: review?(surkov.alexander) → review+
(Assignee)

Comment 3

5 years ago
remote:   https://hg.mozilla.org/integration/mozilla-inbound/rev/faf52cdfbbb3

Comment 4

5 years ago
https://hg.mozilla.org/mozilla-central/rev/faf52cdfbbb3
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla20
You need to log in before you can comment on or make changes to this bug.