| Summary: | Add a test for DOM operations on incompatible arguments | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Pam Greene (IRC:pamg) <pam> | ||||
| Component: | DOM | Assignee: | Pam Greene (IRC:pamg) <pam> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | ||||||
| Priority: | P2 | ||||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Attachments: |
|
||||||
|
Description
Pam Greene (IRC:pamg)
2008-12-03 10:47:48 PST
Created attachment 25715 [details]
New test + result
Tests DOM operations with incompatible or non-DOM receivers or arguments.
Comment on attachment 25715 [details]
New test + result
So strange. The test is fine. I assume we match IE/FF on all of these? If not (and you think any of them matter) we should file bugs to match.
Thanks!
Firefox and IE throw exceptions for many of the cases where we return false or null, but they don't match each other exactly either. It's hard to imagine this really mattering. None of these cases actually *do* anything in any browser, so it's just a matter of how much attention they call to themselves. I'm not inclined to call it a bug, although I'd be easy to convince. |