[
https://issues.apache.org/jira/browse/WOOKIE-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13191179#comment-13191179
]
Paul Sharples commented on WOOKIE-20:
-------------------------------------
I have just re-run all these tests on Windows 7, in the following
environments...
IE 9
Firefox 9.0.1
Opera 11.10
Google Chrome 16.0.912.75 m
and the results were the same in each case...
Test "return-empty-strings" fails because widget.id returns wookies internal
generated Id (expected behavior for wookie)
Test "setItem-fires-event" fails (storage event from iframe)
Test "removeItem-fires-event" fails (storage event from iframe)
Test "clearItem-fires-event" fails (storage event from iframe)
Test "Test at" fails because widget expects
window.widget.preferences.getItem('deletable') to be null. it is actually
"undefined"
Test "au" fails because widget expects prefs.getItem("test1") to be null. it
is actually "undefined"
It looks to me that this is in keeping with Scotts results, ok to verifiy now?
> 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
