Opened 10 years ago
Closed 10 years ago
#6045 closed bug (invalid)
$('<p>some text</p>').get() doesn't return a dom-node anymore
| Reported by: | dwt | Owned by: | john |
|---|---|---|---|
| Priority: | Milestone: | 1.4.2 | |
| Component: | manipulation | Version: | 1.4.1 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
I'm trying to migrate my testsuite to jquery 1.4.1 from 1.3.2 and this is one of the biggest roadblocks I've hit so far.
Running "$('<p>some text</p>').get()" in one of the browser debugger js shells should return that dome node.
This works with jQuery 1.3.1
Tested in WebKit Nightly as of 6.2.10
Change History (4)
comment:1 Changed 10 years ago by
| Component: | core → manipulation |
|---|---|
| Owner: | set to john |
| Status: | new → assigned |
comment:2 Changed 10 years ago by
(I can confirm that it works in Safari 4 and breaks in the nightlies.)
comment:3 Changed 10 years ago by
Ok, wait, this seems to only be a problem with the debugger shell. The content is actually there (doing .get()[0].nodeName gives the paragraph) so it's just a display problem, it seems - but the array does appear to be empty, even though it's not.
comment:4 Changed 10 years ago by
| Resolution: | → invalid |
|---|---|
| Status: | assigned → closed |
Filed at WebKit: https://bugs.webkit.org/show_bug.cgi?id=34680
Note: See
TracTickets for help on using
tickets.
Sounds like a serious problem with the WebKit nightlies!