Falko Schindler

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...

Hi @chrschorn, After quite a while I just stumbled upon this issue. Meanwhile, the `getHtmlElement` function has been implemented by #4087 and PR #4123. And 965be6f519ba2f69917e939be008f8b0c660397d fixes the missing ID...

Hi @TsaiTung-Chen, A number of 48000 * 5 datapoints results in a message of 60MB, which causes the browser to struggle quite a bit. Have you tried creating a plain...

I just tested with the following HTML code. It is killing the browser. 😄 ```html const n = 48000 * 50; let x = new Array(n); let y = new...

Ok, I think I finally understand: - Filling the plot with 48000*50 datapoints on button click freezes the UI. - Reloading the browser tab does render the datapoints. So it...

@mohsenminaei Using your code, I can't reproduce a problem with `100_000` samples. Even `1_000_000` samples are displayed after loading for a few seconds.

@mohsenminaei @krashdifferent Yes, point click events can cause a huge amount of data to be sent back and forth. You can limit it by specifying the event arguments like so:...

@eddie3ruff Looks interesting, but I don't know how easy it integrates with `ui.plotly`. Maybe something for a new feature or pull request?

@evnchn It's clear that there is a limit of how many points can reasonably well be transferred and rendered. There are workarounds as discussed in #4493, but in principle there...

Hi @ghbm-itk, thanks for reporting this issue! The inconsistency is indeed unexpected. It basically boils down to this: ```py ui.link.default_classes(remove='nicegui-link') ui.link("Link 1", "/one") # is still underlined ui.link("Link 2", "/two").classes(remove='nicegui-link')...