Skip to content

change cursor style to text for react-select multi CreatableSelect#796

Merged
ziegenberg merged 1 commit into
opencast:mainfrom
ziegenberg:fix-785
Oct 5, 2022
Merged

change cursor style to text for react-select multi CreatableSelect#796
ziegenberg merged 1 commit into
opencast:mainfrom
ziegenberg:fix-785

Conversation

@ziegenberg
Copy link
Copy Markdown
Member

The presenter and contributor fields in the metadata tab use a combined select input control with multi-select enabled. The actual is only a few pixels wide, so when hovering over the control, it's not showing a text cursor indicating the possibility to input new text.

This commit sets the cursor on the valueContainer component to text and resets it to default on the multiValue component.

For the list of available components for React-Select see: https://react-select.com/components

Fixes: #785

The presenter and contributor fields in the metadata tab use a combined
select input control with multi-select enabled. The actual <input> is
only a few pixels wide, so when hovering over the control, it's not
showing a text cursor indicating the possibility to input new text.

This commit sets the cursor on the `valueContainer` component to `text`
and resets it to `default` on the `multiValue` component.

For the list of available components for React-Select see:
https://react-select.com/components

Fixes: opencast#785

Signed-off-by: Daniel Ziegenberg <daniel@ziegenberg.at>
@ziegenberg ziegenberg added the type:usability Usability improvements label Sep 28, 2022
@Arnei
Copy link
Copy Markdown
Member

Arnei commented Sep 29, 2022

Nice, thanks for fixing this.

While you're at it, could you take a look at the dark mode for the multi-select component? The text cursor is hardly visible in dark mode, which seems to be due to the text color being wrong in general (dark grey instead of the expected white).

@ziegenberg
Copy link
Copy Markdown
Member Author

ziegenberg commented Oct 4, 2022

Why is this PR not deployed on test.editor.opencast.org?

@Arnei
Copy link
Copy Markdown
Member

Arnei commented Oct 4, 2022

Why is this PR not deployed on test.editor.opencast.org?

The github action is currently hardcoded to only work for PRs from certain repos (there are more lines than in the preview): https://github.com/opencast/opencast-editor/blob/2a17c13bd814db30f987952cbfe91ee59dfd601b/.github/workflows/update-test.yml#L12. Would make sense to extend this to all Opencast committers, I think we just kind of forgot about it.

@ziegenberg
Copy link
Copy Markdown
Member Author

I would fix the text cursor in the dark mode in a new PR.

@ziegenberg ziegenberg merged commit 6cf69e0 into opencast:main Oct 5, 2022
@ziegenberg ziegenberg deleted the fix-785 branch October 5, 2022 12:51
@Arnei
Copy link
Copy Markdown
Member

Arnei commented Oct 5, 2022

Created an issue so we don't forget #813

@ziegenberg
Copy link
Copy Markdown
Member Author

Why is this PR not deployed on test.editor.opencast.org?

The github action is currently hardcoded to only work for PRs from certain repos (there are more lines than in the preview):

https://github.com/opencast/opencast-editor/blob/2a17c13bd814db30f987952cbfe91ee59dfd601b/.github/workflows/update-test.yml#L12
. Would make sense to extend this to all Opencast committers, I think we just kind of forgot about it.

@Arnei any suggestion on how to reasonably update the workflow? I do not want to add all commiters manually and not update it automatically. Is there any way to check for the members of the developer team?

@Arnei
Copy link
Copy Markdown
Member

Arnei commented Oct 5, 2022

Why is this PR not deployed on test.editor.opencast.org?

The github action is currently hardcoded to only work for PRs from certain repos (there are more lines than in the preview):
https://github.com/opencast/opencast-editor/blob/2a17c13bd814db30f987952cbfe91ee59dfd601b/.github/workflows/update-test.yml#L12

. Would make sense to extend this to all Opencast committers, I think we just kind of forgot about it.

@Arnei any suggestion on how to reasonably update the workflow? I do not want to add all commiters manually and not update it automatically. Is there any way to check for the members of the developer team?

Tbh I do not know how to do this in a smart way, would have to look into it myself. @lkiesow might have an idea?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type:usability Usability improvements

Projects

None yet

Development

Successfully merging this pull request may close these issues.

How to insert a new presenter is not obvious

2 participants