Bug 13723 - Test the behavior of setting a DOMString attribute to JS undefined.
Summary: Test the behavior of setting a DOMString attribute to JS undefined.
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 523.x (Safari 3)
Hardware: Macintosh OS X 10.4
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-14 19:23 PDT by Sam Weinig
Modified: 2017-05-09 16:03 PDT (History)
1 user (show)

See Also:


Attachments
[WIP] patch (118.46 KB, patch)
2007-05-16 13:55 PDT, Sam Weinig
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Sam Weinig 2007-05-14 19:23:59 PDT
As a follow up to bug 13541, we should test and asses the behavior of setting DOMString attributes to JS undefined.  We should test using both dot notation and get/setAttribute.
Comment 1 Sam Weinig 2007-05-16 13:55:09 PDT
Created attachment 14585 [details]
[WIP] patch

This patch refactors the tests for setting js null to DOMString DOM attributes and uses the new modularity to add similar tests for js undefined.  I still need to make sure the results are correct and update the expected results to show that.
Comment 2 Sam Weinig 2017-05-09 16:03:49 PDT
We have coverage now.