Bug 133912 - Dictionary with attribute set to 'undefined' counts as set but shouldn't
Summary: Dictionary with attribute set to 'undefined' counts as set but shouldn't
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Bindings (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-14 14:01 PDT by Dirk Schulze
Modified: 2014-06-14 14:01 PDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Schulze 2014-06-14 14:01:35 PDT 
If an object has something like { x: undefined }, then the attribute x should count as unset. Instead it is set and can lead to wrong results. Example:

DOMPoint({x: undefined})

shouldn't set DOMPoint.x (so that it defaults to 0). With the bug, DOMPoint.x gets set to NaN. (Undefined on number -> NaN.)