Repository navigation
fix(ColorPicker): Use v-model for color picker instead of :value - #12230
Merged
ChristophWurst merged 1 commit intoJan 12, 2026
Merged
Conversation
…icker Signed-off-by: David Dreschner <github-2017@dreschner.net>
DerDreschner
requested review from
ChristophWurst,
GretaD and
kesselb
as code owners
January 12, 2026 11:30
ChristophWurst
approved these changes
Jan 12, 2026
Member
|
/backport to stable5.6 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The color picker doesn't work correctly right now, as upstream is using a
v-modelright now instead of:valuefor the whole logic. This is the same issue as nextcloud/calendar#7719 and nextcloud/deck#7447. This PR changes the used attribute as well.Resolves #12158. During development, I found the following bug/inconsistency: #12231.