Skip to content

[63889] Move toggle button to the sidebar #19170

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

HDinger
Copy link
Contributor

@HDinger HDinger commented Jun 13, 2025

Ticket

https://community.openproject.org/wp/63889
https://community.openproject.org/wp/64847
https://community.openproject.org/wp/64832

What are you trying to accomplish?

  • Move the toggle button to the sidebar
  • Remove main-menu-bg-hover-color from list of configurable design variables
  • Move logo to the left

Screenshots

Bildschirmfoto 2025-06-17 um 15 13 52

@HDinger HDinger added this to the 16.2.x milestone Jun 13, 2025
@HDinger HDinger force-pushed the implementation/63889-move-toggle-button-to-the-sidebar branch 9 times, most recently from d7fa135 to 5552e88 Compare June 17, 2025 13:35
@myabc myabc self-requested a review June 18, 2025 09:18
@myabc myabc self-requested a review June 18, 2025 11:32
Copy link
Contributor

@myabc myabc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A good start, but there are a few things I think we should address:

Close/Collapse button

Screen.Recording.2025-06-18.at.11.52.07.mov
  • the close/collapse button renders underneath some form components, e.g. rich text areas/CKeditor instances.
  • I think the close/collapse button would also benefit from being opaque (i.e. scheme: secondary). We might even consider a small drop shadow:
Screenshot 2025-06-18 at 12 30 09

Alternatively, we could hide the close/collapse button on scroll?

Project select trigger button

The trigger button renders a title tag - it would be good to use the tooltip here - to be consistent with the open/expand button directly to the right.

N.B. calling ToolTipElement from Angular components should be feasible once this upstream fix is merged: primer/view_components#3558

Screenshot 2025-06-18 at 11 47 49

Misc

  • I've left various inline comments about being more consistent with naming. ✅
  • Just as with my comment here, shouldn't we use try to use the Primer scale and CSS variables rather than hard-coding px values?
  • I've been trying to get in the habit of writing component specs. While admittedly they're a bit of a pain at first, it would be good to get our test coverage up. They are orders of magnitude faster than feature specs when we just want to verify that we're rendering the right HTML (server-side at least) rather than simulating full user interactions. ✅

Comment on lines 52 to 54
def scheme
:invisible
end
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Per my main review comment:

Suggested change
def scheme
:invisible
end
def scheme
@opened ? :invisible : :secondary
end

#menu-toggler--closer
position: absolute
top: 18px
left: 11px
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Per main review comment, something like this?

Suggested change
left: 11px
left: 11px
z-index: 5000
filter: drop-shadow(var(--bgColor-default) 2px 2px 2px)

@HDinger HDinger force-pushed the 63888-move-project-selector-to-the-sidebar branch from 5240242 to 7dde84b Compare June 19, 2025 07:20
@HDinger HDinger force-pushed the implementation/63889-move-toggle-button-to-the-sidebar branch 2 times, most recently from fef9fd4 to c0c8dba Compare June 19, 2025 07:28
@HDinger HDinger force-pushed the 63888-move-project-selector-to-the-sidebar branch from 7dde84b to 15ececb Compare June 24, 2025 07:49
@HDinger HDinger force-pushed the implementation/63889-move-toggle-button-to-the-sidebar branch from c0c8dba to 17589d9 Compare June 24, 2025 07:50
@HDinger HDinger force-pushed the 63888-move-project-selector-to-the-sidebar branch from 15ececb to a00b1ac Compare June 25, 2025 13:43
@HDinger HDinger force-pushed the implementation/63889-move-toggle-button-to-the-sidebar branch 2 times, most recently from 9181511 to 08206e0 Compare June 25, 2025 13:58
…ed/expanded

Clean-up sass code

Avoid that the type selector in the WP from is scrolled two far when being activated. Currently, it is scrolled twice (one time when activating it and once again when selecting an item). Thus the dropdown overlaps the actual input

Move logo to the left side

Make naming consistent for MainMenuToggleComponent and add a component test

Let menu toggle button scroll with the rest of the page

Move modules menu to the left and show it on mobile
@HDinger HDinger force-pushed the implementation/63889-move-toggle-button-to-the-sidebar branch from 08206e0 to cc90002 Compare June 27, 2025 09:10
@HDinger HDinger marked this pull request as ready for review June 27, 2025 09:10
@HDinger
Copy link
Contributor Author

HDinger commented Jun 27, 2025

Hi @myabc

with the product team, we decided for now to let the button scroll on mobile together with the content. We will further improve on this with https://community.openproject.org/wp/65118

@HDinger HDinger requested a review from myabc June 27, 2025 09:12
HDinger and others added 3 commits June 30, 2025 11:16
The user itself doesn't update when a new attribute help text or role is
added to them
…t the autocompleter dropdown overlaps the input
@HDinger HDinger merged commit 20446d2 into 63888-move-project-selector-to-the-sidebar Jun 30, 2025
11 of 13 checks passed
@HDinger HDinger deleted the implementation/63889-move-toggle-button-to-the-sidebar branch June 30, 2025 13:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

3 participants