You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a problem in the new version of v2 (it seems to me that this bug was introduced in alpha 5).
As it can be verified in the playground, the Button component does not change its property “disabled” although the parameter that receives from the parent makes that condition change.
In short, if in the SSR the button has the disabled set to “true”, then in the client it will never be disabled.
If in the SSR the button had the disable set to “false” in the client it can never be changed to disable “true”.
This can be seen by inspecting the HTML of the button
as per discord discussion this issue was created by accident. Everything here works as expected, there is missing usage of the others in the example. Closing it
Which component is affected?
Qwik Runtime
Describe the bug
There is a problem in the new version of v2 (it seems to me that this bug was introduced in alpha 5).
As it can be verified in the playground, the Button component does not change its property “disabled” although the parameter that receives from the parent makes that condition change.
In short, if in the SSR the button has the disabled set to “true”, then in the client it will never be disabled.
If in the SSR the button had the disable set to “false” in the client it can never be changed to disable “true”.
This can be seen by inspecting the HTML of the button
Reproduction
https://qwikdev-build-v2.qwik-8nx.pages.dev/playground/#v=2.0.0-alpha.5&f=7VaxCsIwEN39ipKpQhrQgmBtWhB3FzdxqGAnacWOIf%2FuJZdLU61FBzczpaG5XN693HsBaVZpOkYa3quvqxdw8Nbtax5N2ZReebbWL1B5gayAckdBcoZ2giEsLXTHe5k5t7ChlSUsoZyYIswQU4wLqPa55oOzijhWXvJ4JISwwYBiL4TGJNDLSHW0MFFm3H556Swj5uaJ%2ByGLWNMmT4uw6aQtXpIC%2BRhS0UwXB5Al76nsM%2FroJSIEuG1HqcnAKJ1bsD5VU8R1de0uJuyULXRYeiujwrNwDM8S0P5A2KTVN1MnM%2FRcB3cc26CJkaHVfN87FuvAHX%2FTOwZ0%2FHeOX3SOBw
Steps to reproduce
No response
System Info
Additional Information
No response
The text was updated successfully, but these errors were encountered: