[
https://issues.apache.org/jira/browse/RAVE-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Trevor Mack updated RAVE-728:
-----------------------------
Attachment: canvas-supportedViews.xml
Here is the example gadget to demonstrate this behavior.
> gadgets.views.requestNavigateTo
> -------------------------------
>
> Key: RAVE-728
> URL: https://issues.apache.org/jira/browse/RAVE-728
> Project: Rave
> Issue Type: Bug
> Components: rave-portal
> Affects Versions: 0.14
> Reporter: Trevor Mack
> Priority: Minor
> Labels: gadget, shidnig
> Attachments: canvas-supportedViews.xml
>
> Original Estimate: 5h
> Remaining Estimate: 5h
>
> When a gadget is rendered without explicitly declaring content views (ie.
> canvas, home, default, profile, etc.) gadgets.requestNavigateTo(...) has some
> strange behaviors. The behaviors I have seen is that the gadget can request
> to be displayed in canvas view, but once canvas view has been rendered the
> gadget can not be taken out of canvas view.
> The default behavior that I believe should happen when a gadget developer
> doesn't declare any content views is that the one content block that is
> defined should act as if it has been requested to be every view that the
> container supports. Also it might be important to mention that
> gadgets.views.getCurrentView() always returns the gadgets.views.ViewType for
> "profile" view even after the gadget is rendered as a canvas view.
> The attached files demonstrate the above explained behaviors within a simple
> gadget that has links to toggle between the different gadget views and
> displays the currently reported ViewType.getName().
--
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
