Description of problem: Deleting pages in other order than "newest first" will cause JavaScript exception. See steps to reproduce. Version-Release number of selected component (if applicable): 6.0.0.ER4-5 How reproducible: 100% Steps to Reproduce: 1. Create new pages with names for example "1", "2", "3" (in this order) 2. Delete page "1" and it will be deleted 3. Delete page "2", the page will be still present and the exception will be logged into javascript console 4. The page "2" is still present, but can't be accessed until the refresh of the web-console Actual results: Expected results: Additional info:
The gadget server was tracking the (server-side) page ID of a tab using the index of that tab (it's position relative to other tabs). This was problematic when a tab was deleted, because the mappings would de-synch. The right way to fix this would be to store the page ID on an attribute in the UI itself, and pass that along when the user clicks the delete button for a tab. However, the shortest path to fixing this was to simply update the mappings whenever a tab is deleted. Since we're likely chucking gadget server in the future, in favor of some alternative UI, I went with the shortest path to completion.
Hello, verified on ER7-2