[jira] [Commented] (WOOKIE-20) Conform to the LC W3C Widget API specification

["Scott Wilson (Commented) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WOOKIE-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147116#comment-13147116 ] 

Scott Wilson commented on WOOKIE-20:
------------------------------------

Current test results (0.9.2 rev 1199782) show mostly green, the following red:

1 Test preferences_attrreadonly failed because preferences in window.widget is not read-only
2 Test return-emtpy-strings failed because one of the attributes returned an incorrect value
3 Test did not run or storage event was never fired.
4 Test au failed because the values of the stored preferences were not what they should have been.

#1 is because the preferences attribute itself is not read-only
#2 is because we always generate an ID for a widget, even if it doesn't have one by default.
#3 is a bit of a strange one to implement

I'm not sure what causes the problem with #4, but it throws an engine.js error.
                
> 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