-
Notifications
You must be signed in to change notification settings - Fork 3
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
Error: Assertion failed: The focused Node should have a one and only one PDOM instance LanguageSelectionNode#7268 #261
Comments
Sorry, I took a look for a few minutes but didn't notice anything obvious. I couldn't get this to happen locally. I don't see the LanguageSelectionNode using DAG. Using the debugger, the number of I am wondering if something is breaking before the instance count is correct and this assertion is being thrown during a transient state. Let me know if you want to take a look together. |
I don't think it is about DAG, my guess is that it is about some sort of condition where the LanguageSelectionNode is the pdomFocusedNode but it doesn't have any pdomInstances during the closing of the Dialog. I too can't reproduce FYI. I'll keep investigating. |
Ok, after thinking about this more, it seem that the main issue here is that we are making an assumption about the focused node: That is always has a pdomInstance and is in the PDOM. I believe that this is not true, even if we want it to. It would make sense if we wanted to add an assertion to investigate that assumption a bit more. When a new focus is set. We add a listener to it that says "If you ever remove your pdomInstance, assert". Or "If you every remove your pdomInstance, blur/clear scenery focus." No matter, the assertion we are hitting is downstream of this issue. We are in pdomInstance, and just wanting to make sure that when toggling to invisible, that we blur focus if applicable. One case where it isn't applicable is if the focus doesn't even have a pdomInstance, so I got rid of the assertion and just added grace. @jessegreenberg would you like me to investigate the underlying assumption about how we are sometimes having a |
Tagging @jessegreenberg as a potential locale/keyboard/preference bug. My primary goal for this issue is to silence this bug, but let me know if you have any ideas about solving this.
Right now it is showing up as this message, but actually this is downstream:
The text was updated successfully, but these errors were encountered: