Hubert Drecker

After deep diving into the code & the problem itself, I've tried to correct the height calculation: See https://github.com/SAP/ui5-webcomponents-react/pull/1706

Hi, I had the same requirement for plain input fields: see #4620 The proposed workaround was along these lines: `e.currentTarget.shadowRoot.querySelector("input").selectionStart`

Hi @Lukas742, ### Disabling Virtualization > Dynamically removing the logic of the virtualisation is not practical as its deeply implemented in the table core and cannot be controlled by hooks....

Hi @Lukas742, ahh cool. Yeah, I think that's absolutely sufficient for that use case. Thanks! I would disagree regarding the documentation: With this issue you've already documented this feature, it's...

Hi @gitgdako, yeah this ticket mixes two issues at once: Disabling virtualization and respecting the subcomponent height in the overall height calculation. You're confronted with the second one, but it's...

This is no new proposal, but just another take on a long standing issue. The current approach "the JSX team" seems to take is *do expreesions*. See: - #88 -...

@hristop, yeah I would love to have the very same API for the input field as well. Also would stress the point of consistency. I tried to make my point...

Hi @petermuessig, I saw the [commit](https://github.com/ui5-community/babel-plugin-transform-modules-ui5/commit/4ba096b1a24d807cda2fd2f57425f3ab4b91a31b) and tried it out with decorators. It works. So this issue can be closed? And big thanks for tackling this issue!

> When splitting into multiple files, might be a good idea to also create separate folders for different namespaces. This way users wouldn't need to deal with duplicates in most...

@erik-kers & @JuncalLP, first of all, thanks for the feedback! Secondly, yes odata2ts would need to find out those dependencies and include them automatically. The idea I was trying to...