Skip to main content

Bug Tracker

Side navigation

#12493 closed bug (wontfix)

Opened September 09, 2012 03:04PM UTC

Closed September 10, 2012 12:40PM UTC

Last modified September 10, 2012 12:40PM UTC

null value in WebKit

Reported by: Owned by:
Priority: undecided Milestone: None
Component: attributes Version: 1.8.1
Keywords: Cc:
Blocked by: Blocking:

In Chrome passing a null value to a $("div").text(null) method results in a "null" string printed inside the div.

Attachments (0)
Change History (4)

Changed September 09, 2012 03:39PM UTC by dmethvin comment:1

owner: →
status: newpending

That's outside the valid inputs for the method, the docs clearly say it takes a string, and null is not a string.

What result did you expect?

Changed September 10, 2012 07:07AM UTC by anonymous comment:2

Is just a different behaviour. On the previous versions checking if the var is null was not necessary, now it prints out null.

Changed September 10, 2012 12:40PM UTC by mikesherov comment:3

resolution: → wontfix
status: pendingclosed

Thanks for contributing! However, unexpected inputs produce unexpected outputs! Unfortunately, we can't guarantee (and you shouldn't expect) that every invalid input to every function will behave the same way between versions. We only attempt to guarantee valid and consistent output for valid inputs.

For that reason, I'm going to close this bug as won't fix.

Changed September 10, 2012 12:40PM UTC by mikesherov comment:4

component: unfiledattributes