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

Kumar Rahul commented on OFBIZ-10716:
-------------------------------------

Hi Devanshu Vayas,

I have verified the patch and the searching results in the Webtools application 
are working fine.

> Browser Unresponsive when Loading Entity with Large Results
> -----------------------------------------------------------
>
>                 Key: OFBIZ-10716
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-10716
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: framework/webtools
>    Affects Versions: Trunk
>            Reporter: Devanshu Vyas
>            Assignee: Devanshu Vyas
>            Priority: Major
>         Attachments: OFBIZ-10716.patch, OFBIZ-10716.patch, Screenshot from 
> 2018-12-22 11-03-16.png
>
>
> Recently, I came across a situation where an entity was taking too much of a 
> time(browser asked me to either wait or kill) while loading/searching results 
> in the Webtools application. The entity had close to 5M records, and I 
> checked the server responded timely but the rendering of the screen was 
> taking time.
> When I explored the issue I came across a macro which renders the pagination 
> on the screen, and it had a code block which was causing the screen rendering 
> delay.
> {code}
> <#assign x=(listSize/viewSize)?ceiling>
>   <#list 1..x as i>
>     <#if i == (viewIndex+1)><option selected="selected" value="<#else><option 
> value="</#if>${i-1}">${i}</option>
>   </#list>
> {code}
> This code seems logical enough to me, and what I gather from this is that the 
> list will render a select box with 250,000 options. 
> I would like to propose a change in this UI/UX from select box to an input 
> text box so a user can navigate to any page, similar to a navigation input 
> box in a PDF document reader application.
> Please let me know your thoughts on this and share some more ideas to how we 
> can improve/resolve this issue. Looking forward to your replies!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to