Bug 22632

Summary: Add a test for DOM operations on incompatible arguments
Product: WebKit Reporter: Pam Greene (IRC:pamg) <pam>
Component: DOMAssignee: Pam Greene (IRC:pamg) <pam>
Status: RESOLVED FIXED    
Severity: Normal    
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Attachments:
Description Flags
New test + result eric: review+

Pam Greene (IRC:pamg)
Reported 2008-12-03 10:47:48 PST
Another test.
Attachments
New test + result (4.14 KB, patch)
2008-12-03 10:51 PST, Pam Greene (IRC:pamg) 		eric: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Pam Greene (IRC:pamg)
Comment 1 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.
Eric Seidel (no email)
Comment 2 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. Thanks!
Pam Greene (IRC:pamg)
Comment 3 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.
Pam Greene (IRC:pamg)
Comment 4 2008-12-05 15:19:57 PST
Landed r39047
Note You need to log in before you can comment on or make changes to this bug.