-
Notifications
You must be signed in to change notification settings - Fork 10.7k
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
feat: Contextualbar
resizable
#29461
Conversation
🦋 Changeset detectedLatest commit: c0b9706 The changes in this PR will be included in the next version bump. This PR includes changesets to release 32 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #29461 +/- ##
===========================================
- Coverage 54.83% 54.74% -0.10%
===========================================
Files 2302 2303 +1
Lines 50828 50794 -34
Branches 10413 10388 -25
===========================================
- Hits 27874 27805 -69
- Misses 20443 20512 +69
+ Partials 2511 2477 -34
Flags with carried forward coverage won't be shown. Click here to find out more. |
Contextualbar
resizableContextualbar
resizable
@Gummikavalier Thanks for the heads up, we'll consider it on delivering this feature! |
Looks like this PR is not ready to merge, because of the following issues:
|
Via GitHub (2) and Guilherme Gazzo (1) * develop: (40 commits) chore: Fix some check/lint warnings (#32048) Revert "fix!: api login should not suggest which credential is wrong" (#32156) test: Prevent playwright from unselecting options by mistake (#32158) chore(meteor/packages): apply code style (#32145) fix: New messages export overwrites previous one from the same day when using Amazon S3 (#32062) Release 6.7.0 chore: bump to 6.8.0 (#32153) chore: remove unused onStartup function (#32149) Release 6.7.0-rc.4 chore: remove collections when db watcher is disabled (#32150) chore: Bump Apps-Engine version (#32144) regression(fuselage-ui-kit): Use default translation namespace for `-core` apps (#32105) regression(fuselage-ui-kit): Use default translation namespace for `-core` apps (#32105) chore: move imported `Apps` to proxy (#32142) feat: allowing forward to offline dep (#31976) ci: fix services container not building in build step (#32075) feat: `Contextualbar` resizable (#29461) fix: Missing space between name and user name on system messages (#32136) fix: livechat room desync on different windows (#32135) fix: livechat room desync on different windows (#32135) ...
This one is currently broken in RC 6.8.0; Hovering mouse over the contextual bar edge simply does nothing. I cleared our custom CSS first for this test. I tested also at open.rocket.chat with the same result. |
@Gummikavalier it was released as a feature preview, in order to be able to use it you have to enable the feature under User Account > Feature preview. And of course, the feature preview should be active on the workspace also (it's active on open.rocket.chat, so you can check this feature there). |
@dougfabris Ahh, I eyeballed for it under admin settings but couldn't find it first. Found the Resizing works a treat now. Thanks! 😍 |
@Gummikavalier We're running some experiments, would appreciate your feedback for the whole feature and mainly for the possibility to not having the thread expanded anymore, since user can resize for all contexts |
@dougfabris I'll be updating one production system this week to RC 6.8.0 so we may get some comments after that. A forewarning though; We've spoiled our users for years with that a lot more extended custom Most rejoicing would be heard from option to resize both thread views. And extra hugs from ability to tune the channel listing bar as well. 🤗 (Yes, appetite grows from these small tasters. 😁 ) |
@Gummikavalier Thanks for replying! I've been planning to discuss with the design team the ability to increase the max size over 50%, do you think with this ability, your users will still miss the extended view? I think the main goal here is to have a unique mechanism to improve the contextual bar view using personalization |
@dougfabris Actually even my personal preference is the Expanded view as it darkens the main channel and focuses the eyes on the thread. It stands out better and the general esthetics is less cluttered. Meaning that the user is more focused to the discussion. Several exactly same looking parallel text columns is quite confusing (to me at least). Looking at Discord often makes me vince how bad it can be. 🤢 With regular view if you were able to increase the size to higher than 50%, it'd probably also reformat the messages in the main channel view quite thin. Not sure, would probably need some prototyping to see how it'd work. If only regular mode is the way to go in the future to simplify design, maybe some coloring or hue changes to either main channel or thread background could help with that. |
@Gummikavalier Yeah, maybe a focus mode option that makes the main channel darker instead of extended. Thank your for bring your opinion, I will add it to the discussion with the design team |
@dougfabris No problem and thank you. Regarding on comments on resized contextual bar; it is great that particularly message search, threads listing and members list views can be extended; it making them easier to read. |
@dougfabris FYI: Not reporting this as an official bug, as the feature is in preview. If you hover the mouse in expanded view over a line where the divider would be in collapsed view, it shows through as a blue line. This flashes to the uses every now and then when the mouse travels exactly over the line. Probably not worth fixing if expanded view would be going away, though. |
@Gummikavalier This is a know issue indeed, thank you for reporting. But yeah, we have to check first about the usage of the extended view. If we doesn't keep it, there is no why fix it. |
Proposed changes (including videos or screenshots)
Issue(s)
Closes RocketChat/feature-requests#159
Steps to test or reproduce
Further comments
CORE-282