modal icon indicating copy to clipboard operation
modal copied to clipboard

Modals not displaying after AlpineJs Update

Open MarioGattolla opened this issue 1 year ago • 7 comments

Hello , i just updated AlpineJs from 3.14.3 to 3.14.5 (using Livewire 2). There seems to be a problem with the “display: none” attribute not being removed from here:

image

I checked the issue history and found a very similar problem here but it was fixed in the next version.

https://github.com/wire-elements/modal/issues/423

Can anyone tell me if it is the same bug?

Thank you very much

MarioGattolla avatar Dec 03 '24 15:12 MarioGattolla

Same as #487

fefo-p avatar Dec 03 '24 15:12 fefo-p

Same here !

dgillier avatar Dec 09 '24 15:12 dgillier

Same!

fabio-ivona avatar Dec 20 '24 08:12 fabio-ivona

same problem, any solution?

insulae avatar Jan 06 '25 13:01 insulae

Seems to work when using Livewire v3, not quite sure what the issue is in Livewire v2. Any chance upgrading to Livewire v3 is an option? Livewire v2 adoption is going down rapidly so I prefer not to spend hours trying to solve this. Happy to accept PR's with a fix of course in case someone already pinned down the cause. In the mean time it might be easier to pin Alpine to version v3.13.7 until switching to Livewire v3.

PhiloNL avatar Feb 20 '25 13:02 PhiloNL

it appears that this issue is occurring with all versions of alpinejs under Livewire v2.

@PhiloNL, I understand the desire to avoid putting much work into Livewire V2 however the workaround of pinning it to v3.13.7 does not appear to suffice any longer. I also attempted v3.14.9 of alpine and that didn't help either.

Do you have any recommendations of where I should look if I am to find a way to resolve this? I am not seeing any errors in the console or when running npm run dev so I am at a bit of a loss for where to start when it comes to addressing this...

As mentioned in the initial report of this issue, it appears that display:none is not getting properly removed but that is not helping me identify the source of the issue.

ryangurn avatar Jul 27 '25 02:07 ryangurn

Update: I was not pinning the version properly. My mistake. I will try to make some headway to figure out why this is occurring with Livewire V2, so I still feel that an answer to the following would be quite helpful to me

Do you have any recommendations of where I should look if I am to find a way to resolve this? I am not seeing any errors in the console or when running npm run dev so I am at a bit of a loss for where to start when it comes to addressing this...

ryangurn avatar Jul 27 '25 02:07 ryangurn