UX spec: https://www.figma.com/design/XT0eDYh4RtbMNWaYQi0efM/Chrome-Sidebar-UX-Specifications--Sprint-1-?node-id=9631-131050&t=8JmJB8LIHAYiDTm9-0 This bug does not include the Smart Tab Groups parts of the tab group menu. Notable changes: - smaller header - no separators - color swatches move to the top and get restyled
Bug 2023695 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
UX spec: https://www.figma.com/design/XT0eDYh4RtbMNWaYQi0efM/Chrome-Sidebar-UX-Specifications--Sprint-1-?node-id=9631-131050&t=8JmJB8LIHAYiDTm9-0 This bug does not include the Smart Tab Groups parts of the tab group menu. Notable changes: - smaller header - no separators - color swatches move to the top and get restyled There was some work to update the color swatches in bug 2023691, but based on the report in bug 2052177, this is not working correctly. The tabgroup-menu.js code builds the swatches once when it connects to the DOM. If you start the browser without Nova and then enable it, it will continue to use the pre-Nova tab group color tokens. The tab group color swatches in this menu should always use `--tab-group-color-${colorCode}` and `--tab-group-color-${colorCode}-invert` when Nova is disabled and always use `--tab-group-${colorCode}` when Nova is enabled.