Details
Bug
Description
See lib/ajax/section_classes.js
When AJAX is switched on (site and course level), the course view implementation is brittle and buggy. The script waits for the whole page to be loaded, then "repaints" elements like icons and drag handles. This is causing a number of user interface bugs (see linked issues), and males the javascript a pain to maintain.
The proposed solution is to implement code that lets the course export its state (sections, resources, blocks) as JSON data, which YUI can then use to build the interface, independent of HTML output. This forces a branching in how the interfaces are designed, and may involve some duplication of code, but should resolve most of the interface bugs, and may improve the speed and usability (especially drag and drop).
Issue Links
| This issue will help resolve: | ||||
| MDL-11746 | Page breaks when editing turned on - only first section displays |
|
|
|
| MDL-12198 | AJAX drag and drop is broken for topic sections |
|
|
|
| MDL-12625 | AJAX editing stops halfway down the page |
|
|
|
| MDL-11539 | AJAX Shifting of Blocks Incorrect - Movement doesn't match DB activity |
|
|
|
| MDL-13710 | AJAX editing jams browser for 5 seconds and slows page down - separate button for it? |
|
|
|
| This issue has a non-specific relationship to: | ||||
| MDL-24897 | Set AJAX course editing to 'ON' |
|
|
|
I don't agree that this will resolve the specific problems described in
MDL-11539/MDL-12198. The primary problem there is the discrepancy between the visual feedback provided in the browser and the actual changes performed in the server.MDL-11539/MDL-12198. The primary problem there is the discrepancy between the visual feedback provided in the browser and the actual changes performed in the server.