Why is the event bound by jquery using click invalid?
jqueryEvent bound using clickInvalid
1 2 3 4 5 6 7 8 9 |
|
The relevant basic code is as above, the Refresh a element can be obtained smoothly, but it is the bound click event Invalid, no valid binding can be found in the "Event Listeners" of "Elements" in Chrome's "Developer Tools".
The DOM added by the basic code above is all valid. The outer layer is two each loops, but I feel that it should have no impact. All codes can be executed smoothly, including the binding step. Even if you click on the a element after the execution is completed, it will not work, and you can't find the function bound to it. . . . . . .
1 2 3 |
|
on I also tried it, but it didn’t work. It seems that these two are basically the same?
Because the a element itself has the clickable attribute, after clicking, it will still respond to its original event, such as href=‘#’, and a # will be added at the end of the address bar. . . . I wonder if it is because the original event overwrites the later added event? . . . . .
Your previous binding was
1 2 3 |
|
The same as normal click binding
Try binding like this
1 2 3 |
|
Your element is dynamically generated ?
If so, use live or delegate binding
live jquery1.9 has removed it. Now it is not that the element cannot be found or cannot be bound, but that it is invalid after binding.
I directly changed a to p element, which is also included in click listeners, but the alter("hello"); cannot be triggered no matter what. . . . . .
First, use firebug to see if there is a script error on the page
Again, make sure your code finds the a element
Finally. You can use
1 2 3 |
|
If that doesn’t work, please send me the complete code
The above is the detailed content of Why is the event bound by jquery using click invalid?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



The main reasons why you cannot log in to MySQL as root are permission problems, configuration file errors, password inconsistent, socket file problems, or firewall interception. The solution includes: check whether the bind-address parameter in the configuration file is configured correctly. Check whether the root user permissions have been modified or deleted and reset. Verify that the password is accurate, including case and special characters. Check socket file permission settings and paths. Check that the firewall blocks connections to the MySQL server.

It is impossible to view MongoDB password directly through Navicat because it is stored as hash values. How to retrieve lost passwords: 1. Reset passwords; 2. Check configuration files (may contain hash values); 3. Check codes (may hardcode passwords).

CentOS will be shut down in 2024 because its upstream distribution, RHEL 8, has been shut down. This shutdown will affect the CentOS 8 system, preventing it from continuing to receive updates. Users should plan for migration, and recommended options include CentOS Stream, AlmaLinux, and Rocky Linux to keep the system safe and stable.

The kill command in MySQL sometimes fails because of the special process status and improper signal level. Methods to effectively terminate the MySQL process include: confirming the process status, using the mysqladmin command (recommended), using kill -9 with caution, checking system resources, and in-depth troubleshooting of error logs.

Recovering deleted rows directly from the database is usually impossible unless there is a backup or transaction rollback mechanism. Key point: Transaction rollback: Execute ROLLBACK before the transaction is committed to recover data. Backup: Regular backup of the database can be used to quickly restore data. Database snapshot: You can create a read-only copy of the database and restore the data after the data is deleted accidentally. Use DELETE statement with caution: Check the conditions carefully to avoid accidentally deleting data. Use the WHERE clause: explicitly specify the data to be deleted. Use the test environment: Test before performing a DELETE operation.

Navicat for MariaDB cannot view the database password directly because the password is stored in encrypted form. To ensure the database security, there are three ways to reset your password: reset your password through Navicat and set a complex password. View the configuration file (not recommended, high risk). Use system command line tools (not recommended, you need to be proficient in command line tools).

It is impossible to view PostgreSQL passwords directly from Navicat, because Navicat stores passwords encrypted for security reasons. To confirm the password, try to connect to the database; to modify the password, please use the graphical interface of psql or Navicat; for other purposes, you need to configure connection parameters in the code to avoid hard-coded passwords. To enhance security, it is recommended to use strong passwords, periodic modifications and enable multi-factor authentication.

Reasons for Navicat connection timeout: network instability, busy database, firewall blocking, server configuration problems, and improper Navicat settings. Solution steps: Check network connection, database status, firewall settings, adjust server configuration, check Navicat settings, restart the software and server, and contact the administrator for help.
