Block configuration adjustments#12851
Conversation
|
Hi there @bjarnef, thank you for this contribution! 👍 While we wait for one of the Core Collaborators team to have a look at your work, we wanted to let you know about that we have a checklist for some of the things we will consider during review:
Don't worry if you got something wrong. We like to think of a pull request as the start of a conversation, we're happy to provide guidance on improving your contribution. If you realize that you might want to make some changes then you can do that by adding new commits to the branch you created for this work and pushing new commits. They should then automatically show up as updates to this pull request. Thanks, from your friendly Umbraco GitHub bot 🤖 🙂 |
|
@nielslyngsoe @nathanwoulfe I found a workaround to my old question here #9062 (comment) Maybe not ideal, but it works 😄🎉 Or the hacky workaround by @nathanwoulfe here: ef63fb7 .. |
|
Big thanks @bjarnef really important things to get corrected! |
|
@nielslyngsoe can we close this one if it has been resolved in this PR? #13220 |
|
Just merged this with the latest to see the effect on this PR and indeed everything was already up to date as Niels said, so closing this one. |
Prerequisites
Description
A few adjustments to the block configuration.
for="iconcolor"which didn't make sense. For-attribute target the equivalent value inidattribute. Currently it doesn't really work for color picker component - ideally it should be a button element.ng-click="$event.stopPropagation()"on parent wrapper +tabindex="-1"to not focus this element when navigating via keyboard. It seems to work as expected.Before
chrome_VIcv9TY4De.mp4
After
chrome_MNyxtF55z1.mp4