Closed Bug 761256 Opened 8 years ago Closed 8 years ago

Disable Mac a11y in Aurora 15

Categories

(Core :: Disability Access APIs, defect)

15 Branch
x86_64
Linux
defect
Not set

Tracking

()

RESOLVED FIXED
mozilla16
Tracking Status
firefox15 --- fixed

People

(Reporter: hub, Assigned: hub)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Disable Mac a11y in Aurora 15 (soon uplifted)

Disable the mochitest a11y on Mac as well.

Leave it in Nightly.
Assignee: nobody → hub
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?
Aurora 15 I mean.
I think we need this in nightly as well until bug 759736 is ready.
Blocks: 759236
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.
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.
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+
http://hg.mozilla.org/releases/mozilla-aurora/rev/b765828410ff
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla15
Hub, fixed?
(In reply to alexander :surkov from comment #14)
> Hub, fixed?

when it is merged to m-c.
Target Milestone: mozilla15 → mozilla16
Are we going to disable on Nightly as well?
https://hg.mozilla.org/mozilla-central/rev/195d06e53895
Status: ASSIGNED → RESOLVED
Closed: 8 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.
(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.