-
Notifications
You must be signed in to change notification settings - Fork 12
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
Assertion failed: If we select more than one this way, we have problems #811
Comments
Marking as high priority because it is blocking a high priority issue. @jonathanolson let me know if there is anything I can do to help. |
I found another assertion that triggered while working on
it fails out with another assertion in AccessibleInstance.sortChildren:449 (as of this writing) It also failed out when the tag was 'input'. This may be similar to the other assertion above, so I thought I would add it in here. I'm happy to pair on this too so that next time I might not need to take your time to debug this a11y scenery internal stuff. |
Looks potentially related. I'm still working at understanding the cause of the failure here, but the root cause is 2 "identical" accessible instances are created where only 1 should be created. I have checked in the way to reproduce in the playground, and with the logging output, it logs:
|
@jonathanolson hunted down this bug and shared it with me today. Basically it has to do with reentrance. I was calling the accessibleName setter in |
I came across this while trying to implement
accessibleName
setter for #795. @jonathanolson said he would take a look at it. Thank you! Let me know if I can help.The text was updated successfully, but these errors were encountered: