I'm syncing up with the new starterkit (from March of this year) and radio buttons are now acting strange.
The attached image shows the state after clicking on the File button twice and the AMQP 1.0 button once. The AMQP 1.0 option is selected, and the rest of the application behaves as though it is (the value bound to the targetValue for each radio button is changing). Clicking on a button first adds the thin blue outline (like the AMQP 1.0 button), clicking on it a second time changes it to the thick blue inset (like the File button). If a button has the thick inlay selecting another button will not remove it, as shown in this picture:
There's no jsfiddle for the radio button but I was able to get it to work easily months ago and it worked fine with the flame library from the previous starterkit. Any idea what's going on here?
I'm syncing up with the new starterkit (from March of this year) and radio buttons are now acting strange. The attached image shows the state after clicking on the File button twice and the AMQP 1.0 button once. The AMQP 1.0 option is selected, and the rest of the application behaves as though it is (the value bound to the targetValue for each radio button is changing). Clicking on a button first adds the thin blue outline (like the AMQP 1.0 button), clicking on it a second time changes it to the thick blue inset (like the File button). If a button has the thick inlay selecting another button will not remove it, as shown in this picture:
There's no jsfiddle for the radio button but I was able to get it to work easily months ago and it worked fine with the flame library from the previous starterkit. Any idea what's going on here?