-
Notifications
You must be signed in to change notification settings - Fork 94
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
Bring back menubar without formatting on plain text mode #2757
Conversation
df061f3
to
5f05fb1
Compare
9adc0e0
to
44ad290
Compare
44ad290
to
4f58e4c
Compare
5f05fb1
to
7b24b8a
Compare
Rebased and ready for review :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All in all looks good. I think we do not need to render the menu bubble unless we are editing a richtext document.
With the change to renderMenus
it would now be rendered for text. Since it even has it's own dynamic import might be worthwhile having two computed conditions renderMenubar
and renderMenububble
or so.
7b24b8a
to
34ec7df
Compare
Adjusted the behavior a bit to also bring back the menu bar items on read only files. We probably could refactor the menubar (with regards to the Status component) a bit to not pass all the individual props twice but I kept the changes smaller in order to still have this backportable for now. |
Another conflict, will look into that |
34ec7df
to
e2179b7
Compare
Rebased and ready for review again :) |
Test summaryRun details
View run in Cypress Dashboard ➡️ Flakiness
This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard |
e2179b7
to
37d17c1
Compare
Signed-off-by: Julius Härtl <jus@bitgrid.net>
Signed-off-by: Julius Härtl <jus@bitgrid.net>
853f3a6
to
ebc05a5
Compare
/compile |
Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Just one function that i think is not needed anymore. But that should not block a merge.
cypress was failing earlier - curious to see if this still happens. |
/backport to stable25 |
/backport to stable24 |
Not sure if a backport to 23 is needed. We need the one to stable 24 for sure as a customer complained about this (in ios but i think it's this issue.) |
Looks like for the keyboard shortcut tests retries run into file version conflicts |
The backport to stable24 failed. Please do this backport manually. |
/backport 6657642 to stable24 |
The backport to stable24 failed. Please do this backport manually. |
Not really a backport but rather a reimplementation of #2757. Signed-off-by: Max <max@nextcloud.com>
Fixes #2625