[
https://issues.apache.org/jira/browse/WOOKIE-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583449#comment-13583449
]
Scott Wilson commented on WOOKIE-400:
-------------------------------------
OK, I've done some initial investigation, and at least it seems that injecting
the pages with the scripts is doable.
The issue however is authz; the start page is issued a token (id_key) as a URL
parameter; this is not present when you navigate within the widget to another
page, and without it the page cannot access the API on the server side.
I can't think of any obvious and elegant solutions for this one. Ideas?
> Make Widget API available in all widget pages, not just start files
> --------------------------------------------------------------------
>
> Key: WOOKIE-400
> URL: https://issues.apache.org/jira/browse/WOOKIE-400
> Project: Wookie
> Issue Type: Improvement
> Components: Parser
> Reporter: Scott Wilson
> Fix For: 0.15.0
>
>
> The W3C Widgets spec doesn't specify a single page for widgets, and several
> developers have identified use cases for widgets requiring multiple pages,
> and therefore potential access required to the Widget API.
> To achieve this, the parser needs to be able to inject the required scripts
> into other files in the widget package.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
