Closed
Bug 1429993
Opened 7 years ago
Closed 7 years ago
When the Home Assistant sidebar is initially open and then collapsed, the header doesn't reposition itself
Categories
(Core :: DOM: Core & HTML, defect, P2)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
DUPLICATE
of bug 1430034
Tracking | Status | |
---|---|---|
firefox59 | --- | disabled |
People
(Reporter: MattN, Assigned: edgar)
References
()
Details
(Keywords: regression)
Attachments
(1 file)
95.99 KB,
image/png
|
Details |
MacOS running 59.0a1 (2018-01-11) (64-bit)
STR:
1) Ensure dom.webcomponents.customelements.enabled = true
2) Visit a demo install of Home Assistant: http://hass.thehomeserver.net:8223/states (password = mozilla, choose to remember)
3) Ensure the left sidebar is in the open/visible state by clicking the hamburger menu in the top-left
4) Do a force-reload (Command-Shift-R on Mac). The left sidebar should remember its open state and be open by default
5) Click the "<" arrow between "Home Assistant" and "Home" on the header to close the sidebar
Expected result:
The sidebar closes and the space that it occupied would be used by the main content and blue header.
Actual result:
The sidebar closes and the main content area (right side) grows but the blue header stays offset from the left (it doesn't move).
The problem doesn't occur with dom.webcomponents.customelements.enabled = false.
Reporter | ||
Updated•7 years ago
|
Summary: When the Home Assistant sidebar is initially open and then collapsed, the → When the Home Assistant sidebar is initially open and then collapsed, the header doesn't reposition itself
Assignee | ||
Updated•7 years ago
|
Priority: -- → P2
Comment 1•7 years ago
|
||
CE enabled in only 59 *nightly*, so modified the firefox59 status.
Assignee | ||
Comment 2•7 years ago
|
||
This issue doesn't happen on Firefox Nightly 59.0a1 (20180117220327).
It looks like bug 1430034 also fix this. Close as duplicated of bug 1430034.
Assignee: nobody → echen
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•