-
Notifications
You must be signed in to change notification settings - Fork 342
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
Inconsistent behavior for VaTimeInput right icon #3922 #3933
Conversation
Hey. I was mistaken to reference naive ui. Instead I should've mentioned vuestic-ui select. https://ui-storybook-develop.vuestic.dev/?path=/story/vaselect--old-demos Naive does not close elements on click. But vuestic does. So we need to have toggle behavior for both icon and wrapper.
|
Yeah that will do the trick, I will make changes. |
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 for me, let's deal with CSS variable and merge it.
@@ -407,4 +401,8 @@ export default defineComponent({ | |||
|
|||
<style lang="scss"> | |||
@import "variables"; | |||
|
|||
.va-time-input__side-button { | |||
pointer-events: var(--va-time-input-side-button-pointer-events); |
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.
Hey, @Udaay. We use CSS variables, so it is easier for user to change component look. Do you think there is a case when user need to change pointer-events behavior?
The perfect examples of using css variables to configure border-radius, border-width, paddings, margins, etc.
What I don't like is to have css variables, that for 99% will not be changed. Like display (which is set to flex and whole component breaks if display is changed), position (which must be relative otherwise everything breaks).
We actually do not follow this rule completely, we have a lot of old stuff which was converted to css variables by a script. And I hope in future we will have less meaningless variables.
If you find pointer-events css variable helpful here, let's have it, but if not please remove the css variable. Thanks.
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.
Yes , I got your point and whole idea behind the css variables so that user can configure some specific styles.
Will remove this variable and add directly.
@@ -1,4 +1,5 @@ | |||
:root, | |||
:host { | |||
--va-time-input-min-width: var(--va-form-element-min-width); |
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.
I'm also not sure if --va-time-input-min-width
is used somewhere, so this can be removed too likely.
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.
let me check, I will remove it if it doesn't required.
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.
Thanks!
close #3922
Description
Changed the onClick handler of
va-input-wrapper
Types of changes