robodna

Maybe it should behave like a native select element. From what I understand, onChange is only called when the user interacts with the element. ( onChange is for UI change...

I don't think adding a reason parameter will solve the issue. There needs to be a way to set the initial value programatically without triggering the onChange event. Many components...

Ok. To confirm, there is not way to set the initial value without triggering the onChange event? Also, the onChange event for solid select has different behavior than native select...

I just tested native select and input elements. The onInput and onChange events only dispatch on user interaction. Setting initial values does not dispatch those events. It would make sense...

Thanks for the additional info. I guess it comes down to how the element is initialized. Personally, I envision initializing an input element in the same way as initializing a...

Using SolidJS. I'm just starting so I have no substantial code to share at this point. ( just experimental code with pieces that have been deleted/removed as I test things...

UPDATE: To keep my question as simple as possible, is there a way to programatically trigger the onChange of the Field component to pass a new input value? I think...

Ok thanks. I'm using setValue now but how do I call it from inside of my custom component? It would be cleaner for me to use setValue in my component...

Ok thanks. Maybe there could be a new event hook for manual updates instead of relaying solely on the props.onChange? In my case, my component calculates a new input value...

The onChange needs to be called from outside of the element. It's ok and works but it would be better to have that encapsulated into the component. From what I...