Laura, do you know whom would own this sort of bug?

This is marked as a R68 stable blocker and we are nearing stable in the next couple weeks.

This bug needs to be fixed and merged back within the next week or it will start blocking our R68 stable release.

dtseng@ can you talk this over with katydek@ and zhelfins@ and have one of you take this on?

I can look into this.

 Issue 867429  has been merged into this issue.

If we need to do anything about this, it needs to be done by Monday afternoon, our stable RC builds on Monday night. 

This is currently blocking the 68 stable release, we intend to build tonight, so if at all possible this should be resolved in the next few hours.

Raising priority.

I don't believe this is a blocker. The repro is very tricky because the ChromeVox enabled state (whether it is toggled on automatically) is synced across machines for a given account. So, if you turned on ChromeVox in m68, then tried doing the repro on m67, you are not necessarily hitting the desired behavior.

To really repro:
- on m68,k turn off ChromeVox on your test account.
- go through OOBE on m67 and sign into the test account.

I believe we should address this if it indeed reproduces, but I don't think it's a blocker.

SGTM, dropping from the blocking list and lowering priority.

Assigning to David to investigate