I’m new to the Stimulus library so apologies for the basic question. I have a controller with a version value that is mutated by a radio button list in a form. When the value of the radio button changes, I change version to what the user selected. Then I have a change callback function declared that…

My disconnect() wasn’t being triggered, restarting my Chrome solved it. Memory leak in Chrome? or Stimulus?

I have encountered a similar iuuse, where is never fired even once. I find my question is this static values = ['visible'] changed like below ,it works as intended static values = {visible:Boolean}

Change Callback Not Firing as Expected

dmitruk-v August 24, 2022, 7:37pm 2

I had the same issue in Microsoft Edge. After browser restart it works as intended.

Stimulus connect() but does not disconnect()

Topic		Replies	Views
DOM changes from backend in a turbo_frame_tag are not triggering value changes callbacks	9	1396	June 7, 2021
Stimulus connect() but does not disconnect()	1	1170	September 3, 2022
Lifecycle callback initialize called twice when DOM element is replaced	2	1831	October 14, 2019
Persist stimulus controller when moving element	14	2930	April 4, 2021
Trigger select change	4	5111	September 3, 2018

Change Callback Not Firing as Expected

Related topics