This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 14217 - Use DOMString instead of DOMString? for setProperty
Summary: Use DOMString instead of DOMString? for setProperty
Status: RESOLVED FIXED
Alias: None
Product: CSS
Classification: Unclassified
Component: CSSOM (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Simon Pieters
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-19 11:43 UTC by Simon Pieters
Modified: 2013-08-08 13:26 UTC (History)
2 users (show)

See Also:

Attachments

Description Simon Pieters 2011-09-19 11:43:10 UTC 
Why use DOMString? for setProperty? Seems inconsistent (e.g. removeProperty uses DOMString).
Comment 1 Anne 2011-10-03 13:43:25 UTC 
I removed these for now. It might be that these need TreatAsNull annotations though the data from Microsoft suggested that was not the case.