Skip to content

Follow up/navigation QUICK-FIX chat

MS requested to merge FollowUp/navigation-message-adjustment into master

What does this MR do?

This follow up, disabled the mobile part of the chat page – so it is a bit friendlier to use.

Also disabled some only dev relevant console.log outputs

How confident are you it won't break things if deployed?

🤷

How to test

  1. Checkout branch locally
  2. Login as foodsaver
  3. Try to reach the chat on the Navigation
  4. Try to chat on desktop
  5. Try to chat on mobile

Screenshots (if applicable)

BEFORE AFTER
localhost_18080__page_msg_cid_1147_iPhone_SE___1_ localhost_18080__page_msg_cid_1147_iPhone_SE_

Checklist

  • added a test, or explain why one is not needed/possible...
  • no unrelated changes
  • asked someone for a code review
  • set a "for:" label to indicate who will be affected by this change
  • added to the next milestone (see https://gitlab.com/foodsharing-dev/foodsharing/-/milestones, unless it has a "for:Dev" label)
  • added an entry to CHANGELOG.md
  • added a short text that can be used in the release notes
  • Once your MR has been merged, you are responsible to create a testing issue in the Beta Testing forum: https://foodsharing.de/?page=bezirk&bid=734&sub=forum. Please change the MRs label to "state:Beta testing".
    • Consider writing a detailed description in German.
    • Describe in a few sentences, what should be tested from a user perspective.
    • Also mention different settings (e.g. different browsers, roles, ...) how this change can be tested.
    • Be aware, that also non technical people should understand.

Release notes text in German

Merge request reports