`run_method` and `getElement` return inconsistent types of elements about nicegui HOT 1 OPEN

Hi @chrschorn,

That's a great observation. When implementing and extending getElement, we tried to (almost) always return something "useful", but we introduced an annoying inconsistency. We thought, from the user's perspective, it shouldn't matter if a NiceGUI element is based on a Vue component or a plain HTML element. But of course, if you want to do something with it, the difference matters. One could argue that, if you know that an element is based on Vue, you can step into the HTML element using $el, as you did. But this isn't very intuitive, let alone documented.

To support explicit access to Vue components or HTML elements - without breaking the existing API -, we might want to introduce new functions like getHtmlElement and getVueComponent, and deprecate or at least discourage using getElement.

But besides that, what can we do about ui.input? Quasar takes the q-input tag and replaces it with a whole tree of HTML with a <label> as root, but without setting the "id" attribute. I'm not sure what we could do about it, but it would be great to get some kind of consistency with other UI elements.

from nicegui.