You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wookie.apache.org by "Scott Wilson (JIRA)" <ji...@apache.org> on 2009/08/17 16:41:14 UTC
[jira] Created: (WOOKIE-20) Conform to the LC W3C Widget API
specification
Conform to the LC W3C Widget API specification
----------------------------------------------
Key: WOOKIE-20
URL: https://issues.apache.org/jira/browse/WOOKIE-20
Project: Apache Wookie
Issue Type: Task
Components: Server
Reporter: Scott Wilson
Priority: Critical
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.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (WOOKIE-20) Conform to the LC W3C Widget API
specification
Posted by "Scott Wilson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on WOOKIE-20 started by Scott Wilson.
> 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.8.3
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WOOKIE-20) Conform to the LC W3C Widget API
specification
Posted by "Scott Wilson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Wilson updated WOOKIE-20:
-------------------------------
Fix Version/s: 0.8.3
> 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
> Priority: Critical
> Fix For: 0.8.3
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (WOOKIE-20) Conform to the LC W3C Widget API
specification
Posted by "Scott Wilson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Wilson reassigned WOOKIE-20:
----------------------------------
Assignee: Scott Wilson
> 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.8.3
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> 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.
-
You can reply to this email to add a comment to the issue online.