Details
-
Bug
-
Resolution: Fixed
-
Critical
-
15.10.10, 16.4.0
-
None
-
Unknown
-
N/A
-
N/A
-
Description
Follow these steps to reproduce:
- edit a new page in realtime (tab one)
- edit the same page in a second browser tab
- in the first tab insert a table and then an info box inside one of the table cells
- open the Network tab and clear the request log
- switch to the second tab and type something in the table or after it, but outside the info macro
- switch to the first tab and check the request log
There shouldn't be any requests to HTMLConverter to reload the content because the second tab modifies only content outside the macro. Still, we can see a re-render request for each change produced on the second tab.
This is a serious issue because it prevents the user on the first tab to edit: the content gets refreshed each time the second user types. Not to mention the performance penalty to re-render the content on each keystroke.