When using editable tables I am seeing an issue with the delete button taking an excessive amount of time to complete. ( actually all js commands take a little longer in IE but delete is by far the worst)
The editable table is contained in an AJAX partial page and set up as follows:
~ contains about 20 rows of data with the following cell formats
Drop Down, Text Box, Drop Down, Drop Down, Currency TB, Text Box, Drop Down, Drop Down, hidden, hidden, Currency TB
This problem is specific to IE. Deleting the top row in FireFox 3.6.16 takes ~4 seconds, IE 7 ~90 seconds
By using JS alerts I have pinpointed the problem to the FOR statement on line 810 of the editabletable.js --FOR (var i=0; i<spans.length; ++i)
Has this issue ever come up before? And is there a remedy?
Server: BizFlow 11.7.0.1 (Webmaker 3.1.2.0.7) +?+?+? Java 6 1.6.0_b04
The editable table is contained in an AJAX partial page and set up as follows:
~ contains about 20 rows of data with the following cell formats
Drop Down, Text Box, Drop Down, Drop Down, Currency TB, Text Box, Drop Down, Drop Down, hidden, hidden, Currency TB
This problem is specific to IE. Deleting the top row in FireFox 3.6.16 takes ~4 seconds, IE 7 ~90 seconds
By using JS alerts I have pinpointed the problem to the FOR statement on line 810 of the editabletable.js --FOR (var i=0; i<spans.length; ++i)
Has this issue ever come up before? And is there a remedy?
Server: BizFlow 11.7.0.1 (Webmaker 3.1.2.0.7) +?+?+? Java 6 1.6.0_b04
RE: problems with editable tables and IE
Would it be possible to share a bit more information on your page layout and bindings?
Are your binding document structures different for the partial (AJAX) page and the page that contains the partial page?
When you mention 20 rows of data, is all the data mapped to the table fields or do you have a much larger set of data, which is then selectively mapped? i.e. do you have quite a large volume of data that is being sent back to the browser? You can locate the actual data being returned to the page by looking at the outgoing message for your partial page controller in the Test Dashboard.
When you say the delete takes a long time, have you isolated the time being taken is on the client-side only? i.e. is the delay once you hit the (x) on the row or is it after the delete operations followed by a page submission?
Finally, are you testing IE7 using compatibility mode in IE8/IE9 or are you using IE7 native?
Sorry for all the questions and I appreciate you shouldn't see such a discrepancy between browsers, but just trying to isolate some variables.
Kind Regards
Abdul
RE: problems with editable tables and IE
We have a WebMaker project that goes from controller one to a form (FORM A).
FORM A has two ajax paths to two different forms (FORM B and FORM C)
FORM B is a read only copy of data x via a standard table.
FORM C is an editable copy of data x via an editable table.
FORM A has two buttons on the page: edit and save.
When FORM A loads, the save button is hidden and the ajax to load FORM B is called.
When you click edit button the ajax to load FORM C is called and the edit button is hidden and the save button is shown. (The ajax group that contains FORM B is replaced with FORM C)
I am using IE 7 Native
All the data is pulled into form data fields on page load. It is not a selective display.
What happens is when you click the x button to delete the button gets pressed in and IE essentially freezes with the button pressed in until the Javascript has completed and when it completes the row dissapears and functionality comes back to the browser.
The FOR statement that I mentioned in my previous post is the culprit. When delete is selected and the delete function is called it deletes the row and then chages all the row numbers respectively.
If the last row is deleted it is instantanious because the FOR loop is not called. If the second to last row is deleted the FOR loop is run once and it take ~5 seconds. If the 10th row is deleted the for loop runs 9 times correcting the row ids which takes 9 times as long
When I click the button to save the changes it is instantanious. Editable table is sotred in form data until the submit button is selected(Controller loops through each row sending the data to a stored procedure SQL)