Issues
- "Getting started" webresources should be bundled in batchVSN-3529
- Scroll page title not displayed in remote systemVSN-3403Resolved issue: VSN-3403
- Publishing non translated page creates empty page in target spaceVSN-3400
- Reloading the editor when using a duplicated page title doesn't work on Confluence 5.8VSN-3398
- Exception occurs when saving a page with existing title in a space with Versions and TranslationsVSN-3396Resolved issue: VSN-3396
- Can't scroll to select level 1 page in Excerpt Include PlusVSN-3394
- Exception on API page save: Cannot operate without request contextVSN-3388Resolved issue: VSN-3388
- Improve filtering in Compare dialogsVSN-2809
- Change the field label when publishing to existing spaceVSN-2680Resolved issue: VSN-2680
- UnexpectedRollbackException when creating 2 pages at the same time.VSN-1965
10 of 10
"Getting started" webresources should be bundled in batch
Description
Environment
Confluence 6.1.3
Attachments
1
Details
Details
Assignee
Unassigned
UnassignedReporter
Sync User [K15t]
Sync User [K15t]
Labels
Components
Affects versions
Backbone Issue Sync
Backbone Issue Sync
Created October 18, 2017 at 8:39 AM
Updated March 15, 2024 at 10:37 AM
Activity
Show:
Confluence / Atlassian web resource batching makes sure that the browser clients do not swamp the network with asset (CSS/JS..) requests when viewing or editing a page.
The web resources for VSN getting started are not being batched and are requested on their own.