Bug 22632 - Add a test for DOM operations on incompatible arguments
Summary: Add a test for DOM operations on incompatible arguments
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Pam Greene (IRC:pamg)
Depends on:
Reported: 2008-12-03 10:47 PST by Pam Greene (IRC:pamg)
Modified: 2008-12-05 15:19 PST (History)
0 users

See Also:

New test + result (4.14 KB, patch)
2008-12-03 10:51 PST, Pam Greene (IRC:pamg)
eric: review+
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Pam Greene (IRC:pamg) 2008-12-03 10:47:48 PST
Another test.
Comment 1 Pam Greene (IRC:pamg) 2008-12-03 10:51:06 PST
Created attachment 25715 [details]
New test + result

Tests DOM operations with incompatible or non-DOM receivers or arguments.
Comment 2 Eric Seidel (no email) 2008-12-03 12:34:28 PST
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.

Comment 3 Pam Greene (IRC:pamg) 2008-12-03 13:46:01 PST
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.
Comment 4 Pam Greene (IRC:pamg) 2008-12-05 15:19:57 PST
Landed r39047