Opened 11 years ago
Closed 11 years ago
#11875 closed bug (invalid)
getAttributeNode is undefined
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | undecided | Milestone: | None |
Component: | unfiled | Version: | 1.7.2 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
set: function (a, b, d) { var e = a.getAttributeNode(d);
this line throws exception in the "a.getAttributeNode" because the getAttributeNode is undefined.
Change History (4)
comment:1 follow-up: 2 Changed 11 years ago by
Owner: | set to [email protected]… |
---|---|
Status: | new → pending |
comment:2 Changed 11 years ago by
Replying to dmethvin:
Yeah, we're having a lot of problems with that
a
variable. I think we should change it tob
, maybe that would fix it.Oh, by the way, can you create a test case and put it on jsFiddle so we know what the value of
a
is when the error occurs?
I am using a lot of libraries and they are conflicts with the jQuery I think you just need to add if (typeof a.getAttributeNode != "undefined") -- maybe....
comment:3 Changed 11 years ago by
We still need a test case before we can proceed. I want to know what a
has.
comment:4 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!
Yeah, we're having a lot of problems with that
a
variable. I think we should change it tob
, maybe that would fix it.Oh, by the way, can you create a test case and put it on jsFiddle so we know what the value of
a
is when the error occurs?