Bug Tracker

Opened 12 years ago

Closed 12 years ago

Last modified 11 years ago

#7423 closed bug (worksforme)

`val` fails to return numeric elem.value

Reported by: vostrel Owned by:
Priority: high Milestone: 1.5
Component: attributes Version: 1.4.3
Keywords: Cc:
Blocked by: Blocking:


When non-string value is assigned to element by:


and then retrieving the value back using:


I'm getting (in Chrome 7.0):

TypeError: Object 3.5 has no method 'replace'

pointing me to line 1589 in the latest 1.4.3. In there:

return (elem.value || "").replace(rreturn, "");

I'm not really sure if this actually is a bug or a feature. Either way my tests uncovered this issue.

I think adding an empty string to the elem.value would make it a string and while not hurting existing strings. But I may as well be missing the big picture here.

return (elem.value + "" || "").replace(rreturn, "");

Or are values required to be just strings?

Thanks very much for clarification

Change History (3)

comment:1 Changed 12 years ago by vostrel

Correction: when the value is assigned using val it kinda works - assigned numeric value is returned as a string. But hey, who cares, string to number conversion is cheap. It fails on assigning the numeric value directly to the DOM node using value property.

comment:2 Changed 12 years ago by Rick Waldron

Component: unfiledattributes
Priority: undecidedhigh
Resolution: worksforme
Status: newclosed

I cannot reproduce this issue with 1.4.4rc2


comment:3 Changed 12 years ago by vostrel

OK. Thanks

Note: See TracTickets for help on using tickets.