[
https://issues.apache.org/jira/browse/RAVE-776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Carlucci updated RAVE-776:
----------------------------------
Description:
The current widget rendering algorithm on the client side does not take into
account whether or not the widget is located on a non-active sub page / tab
when the page loads. For example, with the current demo data, the "My
Activity" widget on the "My Activity" tab on the Person Profile page is still
rendering and sending extra network traffic to the widget provider. For a
single widget this is not a lot of overhead, but for a custom sub-page that may
have a dozen widgets on this, the extra overhead adds up in the form of a
slower user experience in rendering the page.
Improve the widget rendering logic on the client side so only visible widgets
are rendered upon the initial page request.
was:
The current widget rendering algorithm on the client side does not take into
account whether or not the widget is located on a non-active sub page / tab
when the page loads. For example, with the current demo data, the "My
Activity" widget on the "My Activity" tab on the Person Profile page is still
rendering and sending extra network traffic to widget provider. For a single
widget this is not a lot of overhead, but for a custom sub-page that may have a
dozen widgets on this, the extra overhead adds up.
Improve the widget rendering logic on the client side so only visible widgets
are rendered upon the initial page request.
> Don't render Widgets on hidden sub-pages / tabs upon initial page load
> ----------------------------------------------------------------------
>
> Key: RAVE-776
> URL: https://issues.apache.org/jira/browse/RAVE-776
> Project: Rave
> Issue Type: Improvement
> Affects Versions: 0.14
> Reporter: Anthony Carlucci
> Assignee: Anthony Carlucci
>
> The current widget rendering algorithm on the client side does not take into
> account whether or not the widget is located on a non-active sub page / tab
> when the page loads. For example, with the current demo data, the "My
> Activity" widget on the "My Activity" tab on the Person Profile page is still
> rendering and sending extra network traffic to the widget provider. For a
> single widget this is not a lot of overhead, but for a custom sub-page that
> may have a dozen widgets on this, the extra overhead adds up in the form of a
> slower user experience in rendering the page.
> Improve the widget rendering logic on the client side so only visible widgets
> are rendered upon the initial page request.
--
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
