[
https://issues.jboss.org/browse/RF-13615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12963922#comment-12963922
]
Holger Walter commented on RF-13615:
------------------------------------
Update:
I tried to adapt the 'setColumnWidth' function in extendedDataTable.js, by
applying a small change: the ajax request at the end of the function is now
only triggered in case the respective column is not already available in the
array 'newWidths', with the given width.
This workaround works - the columns are sized correctly, and the second ajax
request is not sent.
However, your approach of correcting the column width on client side on each
request, after it had been resized once is not really the most performant one,
especially when you take IE8 into account.
As far as I remember you added a fix in 4.3.5 which fixed incorrect column
sizes after scrolling. I have the feeling, that the current problem was
introduced with this fix - but I'm not sure.
Best reagrds
wlh
> ExtendedDataTable: double ajax request on scrolling
> ---------------------------------------------------
>
> Key: RF-13615
> URL: https://issues.jboss.org/browse/RF-13615
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: showcase
> Affects Versions: 4.3.6
> Environment: Problem can be tested in richfaces showcase.
> http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=extendedDataTable&skin=blueSky
> Reporter: Holger Walter
>
> 1. Go to the extendedDataTable showcase
> 2. Turn on ajax loading.
> 3. Open the debugger of your browser and watch the network communication
> 4. Scroll down in the table untli new data has to be fetched.
> => one POST request is sent. This is fine.
> 5. Change the width of a column in the table.
> => one POST request is sent. This is fine.
> 6. Scroll again in the table untli new data has to be fetched.
> -> 2 POST requests are sent. WHY?
> From now on, on each scroll, the table always sends 2 requests. This behavior
> stops only when your relaod the table.
> Due to this behavior I get some perfromance issues, as I have to execute some
> own javascript after each request.
> Is there a possibility to prevent the 2nd POST request. I would be happy even
> with a dirty hack, or just a hint showing me from where the 2nd request is
> triggered.
> Best regards
> wlh
--
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
_______________________________________________
richfaces-issues mailing list
richfaces-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/richfaces-issues
