Bug 13723

Summary:

Test the behavior of setting a DOMString attribute to JS undefined.

Product:

WebKit

Reporter:

Sam Weinig <sam>

Component:

Tools / Tests

Assignee:

Nobody <webkit-unassigned>

Status:

RESOLVED CONFIGURATION CHANGED

Severity:

Normal

CC:

alice.barraclough

Priority:

Version:

523.x (Safari 3)

Hardware:

Mac

OS:

OS X 10.4

Attachments:

Description	Flags
[WIP] patch	none

Sam Weinig

Reported 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.

Attachments
[WIP] patch (118.46 KB, patch) 2007-05-16 13:55 PDT, Sam Weinig	no flags	Details Formatted Diff Diff
View All Add attachment proposed patch, testcase, etc.

Sam Weinig

Comment 1 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.

Sam Weinig

Comment 2 2017-05-09 16:03:49 PDT

We have coverage now.

Note You need to log in before you can comment on or make changes to this bug.