Closed megan-phet closed 6 years ago
@jessegreenberg do you have access to a mac to confirm this bug? Can you provide insight?
I do, Ill take a look.
@megan-phet in the posted video (which is really helpful, thanks!) when it stops working, do you have to release the "fn" key and then press again to get features to work again?
Also, is VoiceOver turned on in these tests? I assume no but just want to make sure.
No I did not let go of the "fn" key, and VoiceOver was not on.
I was able to reproduce on Mac OS 10.13.5.
But it only happened when alternating between the arrow keys fast enough so that both were pressed at once for a split second.
For instance, another way to reproduce (and I think this is what is happening when pressing them quickly):
This may be an Apple behavior, browser is just clearly not sending key codes corresponding to "home" and "end" in this case. Ill try to reproduce in a JSFiddle, and also see if google knows about this.
This is also an issue for page up/page down.
Verified https://github.com/phetsims/resistance-in-a-wire/issues/163#issuecomment-403985560, I was able to reproduce the problem in this JSFidle on a Mac: http://jsfiddle.net/sp0569jw/6/.
I personally don't think this should block publication of RIAW. And since this is how Apple behaves with all web sliders, I am not sure if spending any time on a workaround is even worthwhile.
@emily-phet what do you think?
Hmm, just looking into it a little I am not sure if a workaround is possible. "Fn" key produces no DOM event when pressed, and it is not a modifier key. This behavior is still there when checking event.key, and I can't think of other options.
@jessegreenberg, I personally do not think this should block publication. I use a Mac and have never noticed a problem with the Home and End Keys or the Page Up and Down keys.
I can't reproduce the problem on my Macbook Pro 10.13.5 when pressing quickly. I am not saying it is not a reproducible problem, but I can't reproduce it.
Excellent, thanks @terracoda!
@jessegreenberg how should we proceed with this issue? Should we unassign? Mark low/deferred Priority? Move to a11y-research? Just close the issue and tag as a "wont-fix"?
Lets discuss open RIAW issues at todays a11y dev meeting.
Discussed 7/17/18 meeting:
It is OK to let this one go. We should add this bug to the list of "Platform A11y bugs".
Here is a link to the doc: https://docs.google.com/document/d/1518zv6F0odExFsodShZxwTmWNQk3civuNwtQUR-rEBs/edit
I added a note in the document, closing
Test device:
Operating System:
Browser:
Problem description:
For phetsims/QA/issues/137 The "home" and "end" buttons are "fn"+["left arrow" or "right arrow"] on a Mac. If "fn"+"left arrow" and "fn"+ "right arrow" are pressed repeatedly one after another, it won't jump to maximum or minimum. This doesn't happen on Windows.
Steps to reproduce:
Screenshots: Video
Troubleshooting information (do not edit):