Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug Report]: Autocomplete Many Renders #1691

Open
wisamidris7 opened this issue Dec 25, 2023 · 3 comments
Open

[Bug Report]: Autocomplete Many Renders #1691

wisamidris7 opened this issue Dec 25, 2023 · 3 comments

Comments

@wisamidris7
Copy link

wisamidris7 commented Dec 25, 2023

Masa.Blazor version

latest

Describe the bug

Render Comes To 7 Renders In FirstRender
And When I Click Any Key 2 Renders This Is Not Normal At All

In DeepClone In InternalValue The Renders For Every Autocomplete It Comes 17 and sometimes 12 as minumum in Select When Having Many Autocompletes
I Maked I Report Page And Report Contains Up To 8 Autocompletes

Expected Behavior

No response

Steps To Reproduce

No response

Reproduction code

No response

.NET version

No response

What browsers are you seeing the problem on?

No response

Additional context

No response

@capdiem
Copy link
Contributor

capdiem commented Dec 26, 2023

@wisamidris7 Where is the firstrender called seven times? I think you mean seven times in OnAfterRender. Autcomplete has a lot of logic, and multiple renderings can happen. This may not be a bug, but there may be room for optimization, which I will take a look at in the future.

@wisamidris7
Copy link
Author

Where is the firstrender called seven times?

I mean without toching the autocomplete just when he loads
And I'm Waiting For Masa.Blazor To Get Better And Move On
Cause The App I'm Using Is Uses A Lot Of Autocompletes So When You Use It It's Becomes Very Very Slow And After Aot It Become Also Slow But Not The Same As Non AOT

And Thanks!

@capdiem
Copy link
Contributor

capdiem commented Dec 26, 2023

@wisamidris7 Can you provide a simple example? So I can find the problem easily.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants