Bug #21316
closed
left panel collapse issues
Added by Lisa Knox about 1 year ago.
Updated almost 1 year ago.
Release relationship:
Auto
Description
- It is possible to make the side panel collapsed without switching to the collapsed sidepanel component. It happens when the viewport is less than a certain width, then have the side panel open and then trigger the details panel.
- The collapsed side panel resizes when the details panel is opened and looks janky
- Target version set to Development 2024-01-17 sprint
- Category set to Workbench2
developer-run-tests-services-workbench2: #129
It is possible to make the side panel collapsed without switching to the collapsed sidepanel component. It happens when the viewport is less than a certain width, then have the side panel open and then trigger the details panel.
The collapsed side panel resizes when the details panel is opened and looks janky
- Fixed the second issue by making it so the panel splitter doesn't move at all when side panel is collapsed. This allowed me to remove an excess `applyCollapsedState()` call, which was the source of the first issue.
commit fabc97343f1b74c66890c00295c5c1911d5e096a on branch 21316-left-panel-collapse
- All agreed upon points are implemented / addressed.
- Anything not implemented (discovered or discussed during work) has a follow-up story.
- Code is tested and passing, both automated and manual, what manual testing was done is described
- couldn't replicate the issues after the fix
- Documentation has been updated.
- Behaves appropriately at the intended scale (describe intended scale).
- Considered backwards and forwards compatibility issues between client and server.
- Follows our coding standards and GUI style guidelines.
Lisa Knox wrote in #note-4:
commit fabc97343f1b74c66890c00295c5c1911d5e096a on branch 21316-left-panel-collapse
- All agreed upon points are implemented / addressed.
- Anything not implemented (discovered or discussed during work) has a follow-up story.
- Code is tested and passing, both automated and manual, what manual testing was done is described
- couldn't replicate the issues after the fix
- Documentation has been updated.
- Behaves appropriately at the intended scale (describe intended scale).
- Considered backwards and forwards compatibility issues between client and server.
- Follows our coding standards and GUI style guidelines.
I played with it and didn't see the previous buggy behavior, this LGTM.
- Status changed from New to In Progress
- Status changed from In Progress to Resolved
Also available in: Atom
PDF