Skip to content
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

2548: Split up web feedback at the first level into two smileys again #3004

Merged
merged 7 commits into from
Dec 2, 2024

Conversation

LeandraH
Copy link
Contributor

Short description

The municipalities have been receiving way less feedback since we made some changes there about half a year ago. In this PR, I changed the sidebar in web desktop / the footer in web mobile to show the two smileys instead of the button saying Feedback.

Proposed changes

  • Instead of showing the FeedbackIcon in the sidebar / footer, this shows the HappySmileyIcon and the SadSmileyIcon
  • A click on either of those icons opens the feedback overlay with the clicked icon selected
  • I added a Portal around the sidebar in web desktop to avoid the sidebar poking through when the language selection screen is open

Side effects

  • If the device is narrower than 408px, the sad smiley jumps to a new row. Do we have a minimum width that we support?

Testing

  • Check that sending feedback still works
  • Check that the sidebar isn't hidden behind things it shouldn't be
  • Check that the sidebar isn't hiding other things that it shouldn't be hiding

Resolved issues

Fixes: #2548


@LeandraH LeandraH marked this pull request as ready for review November 23, 2024 19:24
@bahaaTuffaha
Copy link
Contributor

bahaaTuffaha commented Nov 25, 2024

image
here's how it looks from my screen...

@LeandraH
Copy link
Contributor Author

Oooooh, good catch, thanks!

Copy link
Contributor

@bahaaTuffaha bahaaTuffaha left a comment

Choose a reason for hiding this comment

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

It Looks great 👍
There is some observations .. At iPad Air screen for example: it's too close to the content:
Main:
main
This PR:
2548

web/src/components/Layout.tsx Show resolved Hide resolved
web/src/styles/Aside.css Outdated Show resolved Hide resolved
Copy link
Member

@ztefanie ztefanie left a comment

Choose a reason for hiding this comment

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

Thanks for this PR. Tested on firefox with big and small size, works as expected 🚀

web/src/components/SearchFeedback.tsx Outdated Show resolved Hide resolved
web/src/components/FeedbackToolbarItem.tsx Outdated Show resolved Hide resolved
@LeandraH LeandraH enabled auto-merge December 2, 2024 11:28
@LeandraH LeandraH merged commit 4b87183 into main Dec 2, 2024
9 checks passed
@LeandraH LeandraH deleted the 2548-Split-up-web-feedback branch December 2, 2024 11:36
Comment on lines +42 to +57
<ToolbarItem
icon={HappySmileyIcon}
text={t('useful')}
onClick={() => {
setIsFeedbackOpen(true)
setIsPositiveRating(true)
}}
/>
<ToolbarItem
icon={SadSmileyIcon}
text={t('notUseful')}
onClick={() => {
setIsFeedbackOpen(true)
setIsPositiveRating(false)
}}
/>
Copy link
Member

Choose a reason for hiding this comment

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

❓ Wouldn't it make more sense to just render the FeedbackToolbarItem twice? I think this way its pretty confusing that one feedback toolbar item renders two toolbar items. That way, there would also be no need to raise the ispositiveRating state to this compoennt

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hmm, interesting idea, I guess we could do that? Or at least rename the component. I guess I'll open another PR for that 😅

Copy link
Member

Choose a reason for hiding this comment

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

Sorry, I didn't get that the PR is already merged. If you feel motivated, otherwise this is alright as well.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

All good, you're right, it's a good idea :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Feedback functionality too hard to find and less used
4 participants