-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ReadingBlock for MyChallengeAccordinBox content #440
Comments
This should be fully implemented. @terracoda please review. |
|
|
Yes, please move reading block
And keep it as an all-input reading block. New strings for the reading block:
|
Yes, I think controls inside reading blocks will have to work like that. That is how it works in GFLB as well. So, let's keep it like that and be aware of it. |
And the number spinners won't have a hint, see related issue #441 |
Ok The reading block should be done. I updated the focus order, removed the NumberPicker hint responses, and changed the reading block hint response. |
Sorry @zepumph, I did not explain the Tab Order explicitly. The My Challenge button should stay where it was in the Tab Order, and the reading block should only be in one spot. On first tab through I seem to be able to get tot eh reading block twice before and after the number spinners. When the accordion panel is open, it should have 3 Tab stops after the actual My Challenge heading/button, one for each number spinner and 1 for the reading block. When the accordion panel is closed, it should have 1 tab stop, the My Challenge heading/button. Tabbing Order from top to bottom when Accordion is open:
Tabbing Order from bottom to top when Accordion is open:
In addition, the hint response content is correct, but the actual Reading Block content needs to be changed to "Current Challenge {{1}} to {{2}}". This string is shared with the PDOM, so updating removes the need for a custom string. |
I think #446 and this issue are related. I am getting a strange assertion about PDOM order/DAG, which is also why we were getting duplicate ReadingBlock highlights. I'll take a look. |
Ok, sorry, the focus order is buggy, but will be handled in phetsims/scenery#1385. Sorry for the confusion, I thought it was working but didn't test this case enough. |
@jessegreenberg and I discussed the focus order issue, and solved it in this commit. I'll update the context response next. |
See #381 for review. |
The reading block works great with pointer and focus inputs. Nice work! |
Related to #381
https://docs.google.com/document/d/1offJbONUg8y5Aa9kHewC9iTDtNISzna4giGt7WrpXCk/edit#heading=h.tmpeoajac3hg
#363
The text was updated successfully, but these errors were encountered: