-
Notifications
You must be signed in to change notification settings - Fork 29.3k
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
fix: to #182266, Corrected Webview hasFocus check #182279
base: main
Are you sure you want to change the base?
fix: to #182266, Corrected Webview hasFocus check #182279
Conversation
if (viewContainerId && viewContainerId === activePanel?.getId()) { | ||
return true; | ||
} | ||
|
||
const container = this.getContainer(part); | ||
|
||
return !!container && isAncestorUsingFlowTo(activeElement, container); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have you investigated why isAncestorUsingFlowTo
doesn't work in this case? Ideally this part of the code shouldn't have to know anything webview specific
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have you investigated why
isAncestorUsingFlowTo
doesn't work in this case? Ideally this part of the code shouldn't have to know anything webview specific
Yes, I commented on #182266 (comment) earlier.
it looks like the activeElement
is incorrect when Webview clicked
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have you investigated why
isAncestorUsingFlowTo
doesn't work in this case? Ideally this part of the code shouldn't have to know anything webview specific
Have you investigated why
isAncestorUsingFlowTo
doesn't work in this case? Ideally this part of the code shouldn't have to know anything webview specific
I think what you said is right. Ideally, there should be no special treatment for it. I'll try to see if activeElement
value can be corrected.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have you investigated why
isAncestorUsingFlowTo
doesn't work in this case? Ideally this part of the code shouldn't have to know anything webview specific
hi @mjbvz activeElement
looks like a read-only property, we don't seem to be able to actively modify the value for it.
ec38a3d
to
c30cebe
Compare
Close #182266.