We have a section of one of our sites with large tables. Sometimes when editing the Table Properties via the WYSIWYG the entire session crashes and all matrix browser windows close. This issue is intermittent.
However consistently on pages with tables of 30+ rows it takes over a minute to view the source code or to commit, and during that minute matrix completely freezes and the browser window is either inaccessible or goes blank.
Is there a way we can allocate more memory, or configure something either in Matrix or on the server, so that pages like these with large tables don't cause Matrix to freeze and generally be slow?
Thanks,
Sarah
The table editor / WYSIWYG editor is purely browser-based, written in JavaScript. I'm not sure there is much we can do from a server perspective to change how the browser behaves. Can you reproduce this issue in a different browser?
[quote]We have a section of one of our sites with large tables. Sometimes when editing the Table Properties via the WYSIWYG the entire session crashes and all matrix browser windows close. This issue is intermittent.
However consistently on pages with tables of 30+ rows it takes over a minute to view the source code or to commit, and during that minute matrix completely freezes and the browser window is either inaccessible or goes blank.[/quote]
This issue may be related to [bug]1758: Large tables cause the WYSIWYG editor to hang/freeze[/bug]. This particular bug has been resolved in 3.8.7 and 3.10.2 and later versions. On which version of Matrix is this problem occuring?
(Edit: Reduced quoted text)
3.14.3
I'll try another browser
Fine in Firefox - 2 sec to view source / 4 sec to commit
In IE over a minute for both...
Unfortunately we only have IE installed in our standard operating environment :(
There is obviously something weird going on with the JavaScript. Are you using all the plugins or do you have some disabled? Which version of IE are you guys using? Do you have a copy of Matrix v3.16 and if so, can you reproduce the issue in that version (considering the JavaScript may be different).
Slow table rendering is a fairly well known issue with Internet Explorer. This is related to the fact that it does a lot of calculations before painting a table, whereas Firefox will do it progressively. This may be related to this problem.
There’s a dandy CSS hint on this IEBlog entry, which also discusses what’s happening in further detail.
http://blogs.msdn.com/ie/archive/2005/02/10/370721.aspx