-
Notifications
You must be signed in to change notification settings - Fork 951
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
:focus
selector inconsistent in Edge Legacy
#424
Comments
I don't think so - I don't think the As I state in jquery/jquery#4109 (comment) (and the sample in jquery/jquery#4109 (comment) shows) it appears that jquery has two different ways of determining the value of In addition, when the "Sizzle path" is taken for an element, it appears that Sizzle caches that decision for the element and the "native path" will no longer be taken for that element. Thus: |
I should have been more clear, by "lose focus", I meant the activeElement property gets unset or the page loses focus. Has nothing to do with whether the cursor is actually still in the input. |
I don't think it is anything "dynamic" - I don't think I think it is simply that Edge's notion of Actually, Sizzle's notion depends on if the jquery object contains one element or if it contains more than one element. If it contains one element then Sizzle's notion also returns [*1]: with the caveat in item 2 above - Sizzle's notion may return |
Again, it was just a theory. We've seen situations where simply accessing a property in IE or Edge has unexpected side effects. It seemed conceivable that something like that was happening here when hitting Whether it's checking more than one element is not really the issue. It may be a factor in whether the native In other words, when to use native |
And I have not stated that is the issue. The issue, I think, is that there currently are two different ways/paths to determine the value of
I am not sure Here is another sample that shows the current behavior.
Assume
But currently, in this particular scenario (when the page is reloaded by clicking browsers "Reload" button, the following is observed:
|
I'm sorry, but you're still not understanding what I'm saying.
This is the same thing I said just in different words. There are two paths. One is native and one is Sizzle. We can only control the Sizzle path. Once we get that right, we can make sure native is working right. If it's not, as you suspect, there are ways we can ensure that the Sizzle path is always used in edge. Anyway, I don't think we need to keep having a conversation here. We will investigate and fix the inconsistency. |
No need to be sorry - I understand it all right. And am glad you do too now. |
The old Edge is retired and the new Edge is chromium based so not even sure its worth investigating this issue @timmywil ?? |
@melloware Sizzle supports and will support Edge Legacy. That said, Sizzle is getting close to being archived; jQuery 4.0 will embed a selector engine ported from Sizzle with workarounds for legacy browsers stripped out; we won't care about Edge Legacy there. This issue may remain open; if someone submits a fix, we'll review it. It's unlikely anyone from the jQuery team will look into fixing it by themselves, though. |
:focus
selector inconsistent in Edge:focus
selector inconsistent in Edge Legacy
jQuery version of this issue: jquery/jquery#4109 |
Migrated from jquery/jquery#4109
Test case: https://jsfiddle.net/63zby1nt/
Seems like maybe the process the of checking for focus in Edge causes the input to lose focus. More thorough analysis is available in the comments on the jQuery issue.
The text was updated successfully, but these errors were encountered: