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
Strange error behavior of event delegation when customizing jQuery #5379
Comments
Thanks for the report. This is on the In jQuery 3.x, the Line 1057 in 87467a6
defined in the same file: Lines 853 to 876 in 87467a6
On the Line 454 in c98597e
which lies outside of this module and this dependency was not made explicit. Depending on Line 7 in c98597e
but that's mostly an artifact from jQuery 3.x previously depending on jQuery.find.attr from the selector module here:Line 68 in 87467a6
while on the main branch a native getAttribute is used:Line 61 in c98597e
We should remove the dependency on
I'm gravitating towards the first option for the following reasons:
|
Actually, I was wrong about the logic change. Line 13 in b922eed
Line 13 in b922eed
On the Lines 102 to 128 in 99151d7
Thus, the logic is fine, we just need to declare the dependency explicitly. I submitted removing unneeded |
This fixes custom builds using the `--include` switch that don't include the `attributes` module. Fixes jquerygh-5379
This fixes custom builds using the `--include` switch that don't include the `attributes` module. Fixes jquerygh-5379
PR: #5384 |
This fixes custom builds using the `--include` switch that don't include the `attributes` module. Fixes jquerygh-5379
This fixes custom builds using the `--include` switch that don't include the `attributes` module. Fixes jquerygh-5379
This fixes custom builds using the `--include` switch that don't include the `attributes` module. Fixes jquerygh-5379
Description
My build script is as follows:
When I use event delegation
html
According to the description of readme.md,selector: The full jQuery selector engine. When this module is excluded, it is replaced with a rudimentary selector engine based on the browser's querySelectorAll,However, querySelectorAll supports this type of selector
I would like to ask if this design is intentional or is it a flaw?
By the way, I have already tested it in the full version and there is no such issue
Thank you.
Link to test case
The text was updated successfully, but these errors were encountered: