-
Bug
-
Resolution: Not a bug
-
Low
-
None
-
9.1.0, 9.1.1
-
4
-
Severity 3 - Minor
-
6
-
Issue Summary
After Upgrading Confluence from 9.0.x to 9.1.x, Default Theme "Match System" shows overlapping of the Page content while scrolling the Page down.
This is reproducible on Data Center: (yes)
Steps to Reproduce
- Set up Confluence 8.5 and create content with a large Page size. (create multiple Users for testing)
- Go to Admin > Layouts > Main Layout > Create Custom > Save
- Upgrade Confluence from 8.5 to 9.1.1
- Confluence 9.1.1 has the default Theme Set to "Match System"
- Login with "admin" user, When you scroll down the Pages, it overlaps the Page content with the title bar. Issue Replicated locally.
- But If I switch back from Dark/Light Theme to Match System, the issue is gone. I am not able to replicate it anymore with the User- "admin".
- Then I switch the user to "test1" it is still replicable.
- Then I restarted the Confluence - It is not reproducible for the admin (because I have switched the theme, but it is replicable with user "test1".
- The issue is not reproducible with plain vanilla 9.1.1, only reproducible with the upgraded instance.
Customer Impact: Themes are user-specific, and Confluence 9.1.x has the default Theme is "System Match" and all the users are reporting the issue.
Expected Results
Page content should not overlap with "Header-banner" or Title Bar.
Actual Results
Page Content are getting overlapped while scrolling down.
Workaround
Backup custom existing layout then click Reset Default. Reapply individual changes made from custom into new layout.
Switching between the Theme to Light or Dark will fix the issue for the User.
This issue is caused by the custom layouts.
The customised layout is overriding the default HTML rendered by Confluence.
In case the custom layout was created in the version of Confluence older than 9.0 prior to the introduction of theming support, it will not have the HTML attributes and styles in it.
To fix that issue, either use the workaround from the issue description above, or assure the following code exists in the custom layout: