Opened 11 years ago
Closed 11 years ago
#10141 closed bug (invalid)
Webkit browsers empty function behavior
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | low | Milestone: | None |
Component: | misc | Version: | 1.6.2 |
Keywords: | Cc: | dmethvin | |
Blocked by: | Blocking: |
Description
Line 5663 (manipulation.js)
Bugfix in Webkit browsers when use jQuery empty function (demo only valid for Webkit http://goo.gl/zow5W)
Change History (9)
comment:1 Changed 11 years ago by
Owner: | set to [email protected]… |
---|---|
Priority: | undecided → low |
Status: | new → pending |
comment:2 Changed 11 years ago by
Maybe doesn't be a bug, but a differ behavior.
If you use html function for change a container and now this container has one script tag (<script></script>) and a form with a textbox (<form><input type="text"></form>), when you focus the textbox and press enter for submit form and change again the container, the scroll will go top, if you press button submit this won't happen.
This only happen if your browser uses Webkit (ex: Chrome).
A proof of concept: http://jsfiddle.net/yeikos/SgNKV/
Sorry for my bad writting (I'm spanish)
comment:3 Changed 11 years ago by
Resolution: | → patchwelcome |
---|---|
Status: | pending → closed |
This seems like an edge case at best.
comment:4 Changed 11 years ago by
Component: | unfiled → misc |
---|
comment:6 Changed 11 years ago by
Resolution: | patchwelcome |
---|---|
Status: | closed → reopened |
comment:7 Changed 11 years ago by
Cc: | dmethvin added |
---|
Sorry, that was a misfiling. I'm going to defer to @dmethvin for a verdict here
comment:8 Changed 11 years ago by
Status: | reopened → pending |
---|
As asked in the commit, why does the .innerHTML
require a try/catch?
comment:9 Changed 11 years ago by
Resolution: | → invalid |
---|---|
Status: | pending → closed |
Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!
Thanks for filing, but you still haven't made it clear what the bug is