The default bug view has changed. See this FAQ.

Disable Mac a11y in Aurora 15

RESOLVED FIXED in Firefox 15

Status

()

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

People

(Reporter: hub, Assigned: hub)

Tracking

(Blocks: 1 bug)

15 Branch
mozilla16
x86_64
Linux
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox15 fixed)

Details

Attachments

(1 attachment)

(Assignee)

Description

5 years ago
Disable Mac a11y in Aurora 15 (soon uplifted)

Disable the mochitest a11y on Mac as well.

Leave it in Nightly.

Updated

5 years ago
Assignee: nobody → hub
(Assignee)

Comment 1

5 years ago
Created attachment 629868 [details] [diff] [review]
Disable a11y on Mac for Aurora. r= a=
(Assignee)

Comment 2

5 years ago
Comment on attachment 629868 [details] [diff] [review]
Disable a11y on Mac for Aurora. r= a=

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

Uplift is too soon. Requesting Aurora approval. This is a straight backout of bug 733513 and we want it in ASAP as Mac a11y seems to have had far too many side effects.
Attachment #629868 - Flags: approval-mozilla-aurora?
(Assignee)

Comment 3

5 years ago
Aurora 15 I mean.
Attachment #629868 - Flags: review+
I think we need this in nightly as well until bug 759736 is ready.
Related mailing list discussion: http://bit.ly/Li5rPP

Updated

5 years ago
Blocks: 759236
(Assignee)

Comment 6

5 years ago
Disabling in 16 until we get the bug 759736 fixed.

https://hg.mozilla.org/integration/mozilla-inbound/rev/195d06e53895

Comment 7

5 years ago
If I'm understanding what disabling a11y Mac support would mean, I don't think think we should just go and disable it on Aurora 15. For now, Aurora updates are disabled until we stabilize updates (see bug 761189). I think we should instead wait to see what happens in bug 759236 before taking drastic action.

Basically, we wouldn't ship with a11y disabled, so this bug is moot.
(Assignee)

Comment 8

5 years ago
a11y was disabled on Mac in FF 14. It was enable for 15, but it seems to cause more issues. Disabling it is not a regression.
(In reply to Alex Keybl [:akeybl] from comment #7)
> If I'm understanding what disabling a11y Mac support would mean, I don't
> think think we should just go and disable it on Aurora 15. For now, Aurora

we said when we turned a11y on just after branching 14 that we expected issues to arise and might well disable a11y on mac before release, so this isn't really just on a wim

> updates are disabled until we stabilize updates (see bug 761189). I think we
> should instead wait to see what happens in bug 759236 before taking drastic

I'm not sure how much we can investigate there, we know roughly what the problem is, but its not easily solved.
(In reply to Trevor Saunders (:tbsaunde) from comment #9)
> (In reply to Alex Keybl [:akeybl] from comment #7)
> > If I'm understanding what disabling a11y Mac support would mean, I don't
> > think think we should just go and disable it on Aurora 15. For now, Aurora
> 
> we said when we turned a11y on just after branching 14 that we expected
> issues to arise and might well disable a11y on mac before release, so this
> isn't really just on a wim
> 
> > updates are disabled until we stabilize updates (see bug 761189). I think we
> > should instead wait to see what happens in bug 759236 before taking drastic
> 
> I'm not sure how much we can investigate there, we know roughly what the
> problem is, but its not easily solved.

So there would be no regression for a user going from FF14 to FF15 at release if left disabled? I just want to verify that before approving.
(Assignee)

Comment 11

5 years ago
No regression because a11y for Mac isn't enabled in FF14.
Comment on attachment 629868 [details] [diff] [review]
Disable a11y on Mac for Aurora. r= a=

[Triage Comment]
Approved for Aurora 15.
Attachment #629868 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
(Assignee)

Comment 13

5 years ago
http://hg.mozilla.org/releases/mozilla-aurora/rev/b765828410ff
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla15

Comment 14

5 years ago
Hub, fixed?
(Assignee)

Comment 15

5 years ago
(In reply to alexander :surkov from comment #14)
> Hub, fixed?

when it is merged to m-c.

Updated

5 years ago
status-firefox15: --- → fixed
Target Milestone: mozilla15 → mozilla16
Are we going to disable on Nightly as well?
Blocks: 761574
https://hg.mozilla.org/mozilla-central/rev/195d06e53895
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
(In reply to Rob Campbell [:rc] (:robcee) from comment #16)
> Are we going to disable on Nightly as well?

Temporarily yes, and then whitelist for VoiceOver, see bug 759736.

Also, if you need a11y enabled, there's a script in m.d.platform which you probably have seen.
(Assignee)

Comment 19

5 years ago
(In reply to Rob Campbell [:rc] (:robcee) from comment #16)
> Are we going to disable on Nightly as well?

see comment 6
You need to log in before you can comment on or make changes to this bug.