News for hackers. Stuff that matters.
Re:Love letter to Vue by nogridbag on Tuesday July 17, 2018 @05:26PM (#17553580)
Did you consider using individual components instead of adopting an entire component framework? Interestingly, I just picked a random Vuetify component from your list, Autocomplete, and the demo is broken in Chrome (cannot type or click trigger - only keyboard down arrow works):

https://vuetifyjs.com/en/components/autocompletes

Re:Love letter to Vue by Tade0 on Tuesday July 17, 2018 @06:04PM (#17553866)
> Did you consider using individual components instead of adopting an entire component framework?

Yes and it's a headache. Mostly because they have separate docs and CSS. The other day I had to change the appearance of all the labels - with a single framework I could just add a simple, single selector(because Vuetify as opposed to Angular Material uses BEM) and be done with it.

I may have to use an individual component for uploading since it hasn't landed in Vuetify yet: https://github.com/vuetifyjs/vuetify/issues/238

> (cannot type or click trigger - only keyboard down arrow works):

Control question: did you click the icon on the left or on the right?

Re:Love letter to Vue by nogridbag on Wednesday July 18, 2018 @09:52AM (#17558335)
> Control question: did you click the icon on the left or on the right?

This is the first time I've ever been stumped by a simple read-only field. I think my confusion was due to the floating label animation on focus which I would expect only if the field was editable. You typically don't encounter read-only fields in mobile apps but they're common place in enterprise desktop apps.

Regardless, there is a bug since clicking the down arrow on the keyboard still allows me to select a state even though the field is read-only.