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]: Different behavior of autocomplete in production #5770

Open
tacoWanneeJama opened this issue Oct 8, 2024 · 0 comments
Open

[Bug]: Different behavior of autocomplete in production #5770

tacoWanneeJama opened this issue Oct 8, 2024 · 0 comments
Labels
Type: Bug 🐞 Something isn't working

Comments

@tacoWanneeJama
Copy link

tacoWanneeJama commented Oct 8, 2024

Blazorise Version

latest

What Blazorise provider are you running on?

None

Link to minimal reproduction or a simple code snippet

When I run my program in development environment I see this correct behavior:
Image
But when I deploy it on a Linux Azure website I get this strange result:
Image

Steps to reproduce

I did just before a forced clear of caches on both sites

What is expected?

In production the same behavior as in development

What is actually happening?

Wrong filter result

What browsers do you see the problem on?

Chrome (latest)

Any additional comments?

Where should I look for the possible difference between development and production?

@tacoWanneeJama tacoWanneeJama added the Type: Bug 🐞 Something isn't working label Oct 8, 2024
@tacoWanneeJama tacoWanneeJama changed the title [Bug]: DIfferent behahior of autocomplete in production [Bug]: Different behavior of autocomplete in production Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug 🐞 Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant