[LiveComponent] Demo : The search input does not filter the list with Firefox on a smartphone

symfony / ux

Symfony UX initiative: a JavaScript ecosystem for Symfony

https://ux.symfony.com/

MIT License

811 stars 295 forks source link

[LiveComponent] Demo : The search input does not filter the list with Firefox on a smartphone #1432

Open Coleyra opened 7 months ago

Coleyra commented 7 months ago

The search input on the Live Component demo page have a strange behaviour with firefox on smartphone. But it works with Firefox (115.7) on Windows.

Step to reproduce :

Go to https://ux.symfony.com/live-component with a smartphone.
Type something in the Live Components search input.

Expected :

The list is filtered and the text you typed in stay in the input.

Results :

The list is briefly filtered.
Then the list come back to the original state (all of the components are listed).
The input field is empty.

Software used to reproduce :

Smartphone : Redmi Note 7
OS : MIUI 12.0.3
Firefox 122.0

smnandre commented 7 months ago

Hi @Coleyra : do you experience the same bug on this page https://ux.symfony.com/demos/live-component/chartjs ?

Is there any "dev console" on your Firefox mobile ? If yes do you see any errors ?

weaverryan commented 7 months ago

FYI - I can't repeat in 122.1 Firefox on an iPhone.

Coleyra commented 7 months ago

This demo seems to work fine, as well as all the others except https://ux.symfony.com/demos/live-component/product-form The Product name input in this demo have the same behaviour as the https://ux.symfony.com/live-component one.

I installed the MobiDevTool extension on my Firefox mobile, but i don't see any error.

smnandre commented 7 months ago

First thought... do you use any Adblocker / cookie auto-remover ?

Coleyra commented 6 months ago

Hi,

Sorry for the late answer i haven't seen the notification of your answer. I didn't use adblocker or cookie remover.

But the good news is since the 2.15 release, the problem is solved for me.

carsonbot commented 1 week ago

Hey, thanks for your report! There has not been a lot of activity here for a while. Is this bug still relevant? Have you managed to find a workaround?