| Summary: | Dictionary with attribute set to 'undefined' counts as set but shouldn't | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Dirk Schulze <krit> |
| Component: | Bindings | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW --- | ||
| Severity: | Normal | CC: | oliver, rniwa, sam |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
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.)