[
https://issues.apache.org/jira/browse/WOOKIE-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194830#comment-13194830
]
Scott Wilson commented on WOOKIE-20:
------------------------------------
OK, I've checked again and it looks like the WebStorage spec changed or I
misinterpreted it: while clear() must remove the entries, getItem() must return
Null rather than undefined when requesting a non-existing item:
widget.preferences.clear(); // get rid of everything
widget.preferences.setItem("foo", null); // set "foo" to equal null
widget.preferences.getItem("foo"); // tuple exists and is set to null; return
null
widget.preferences.getItem("completely_undefined_bar"); tuple doesn't exist,
return null
I've updated Wookie and we can now pass test "at". We don't pass "au" but I'll
raise another issue for that.
> Conform to the LC W3C Widget API specification
> ----------------------------------------------
>
> Key: WOOKIE-20
> URL: https://issues.apache.org/jira/browse/WOOKIE-20
> Project: Wookie
> Issue Type: Task
> Components: Server
> Reporter: Scott Wilson
> Assignee: Scott Wilson
> Priority: Critical
> Fix For: 0.9.2
>
> Original Estimate: 120h
> Time Spent: 1h
> Remaining Estimate: 119h
>
> As the W3C Widgets API spec gets to last call (LC) status, we should ensure
> that Wookie is able to pass all conformance requirements. This means that we
> need to:
> - update the self-test widget to conform to the spec; this widget includes
> test cases that helps us check conformance
> - all metadata properties specified in the W3C Widget interface are available
> - all metadata properties noted as READ-ONLY in the specification raise an
> appropriate exception if someone attempts to modify them
> - methods are created to handle widget and height attribute requests
> appropriately
> - the preferences object is instantiated correctly and behaves according to
> specification
> - the openURL method is correctly implemented
> - remove any attributes or methods left over from earlier drafts of the spec,
> e.g. showNotification, window modes etc
> Overall, we need to ensure that all MUSTs in the spec are adhered to.
> See also: http://dev.w3.org/2006/waf/widgets-api/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
