The chat dock is meant to be the persistent way to work with Archie from any page, and stays floating for that reason. Expanded, it covers the centre of the page, so asking about a blocked task hides the task.
Wanted:
The expanded dock can be dragged and resized, and remembers its position and size per browser.
A pin control docks it to the left or right edge; pinned, the page content reflows beside it instead of under it.
Collapsed behaviour is unchanged.
Done when an operator can read the Needs attention list and the expanded chat at the same time on a desktop-width screen, and phone width keeps the current full-width dock.
The chat dock is meant to be the persistent way to work with Archie from any page, and stays floating for that reason. Expanded, it covers the centre of the page, so asking about a blocked task hides the task.
Wanted:
- The expanded dock can be dragged and resized, and remembers its position and size per browser.
- A pin control docks it to the left or right edge; pinned, the page content reflows beside it instead of under it.
- Collapsed behaviour is unchanged.
Done when an operator can read the Needs attention list and the expanded chat at the same time on a desktop-width screen, and phone width keeps the current full-width dock.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The chat dock is meant to be the persistent way to work with Archie from any page, and stays floating for that reason. Expanded, it covers the centre of the page, so asking about a blocked task hides the task.
Wanted:
Done when an operator can read the Needs attention list and the expanded chat at the same time on a desktop-width screen, and phone width keeps the current full-width dock.