Open LynnScarlett opened 5 years ago
Translation of this issue:
yes
Cascader
What is the reason why a refactoring of 2.9.0 cancels change-on-select?
Can the new feature checkStrictly cover the previous functionality? Why do checkStrictly and el-ratio force binding?
Why change-on-select'was removed by a called
refactor'?
Can checkStrictly
perfectly replace `change-on-select'?
Why checkStrictly = true
means'el-ratio?
到 2.12.0, 不知道怎么禁止点选指定层级的 radio,而以前的 change-on-select 可以实现。
同问,感觉把单选层级与 radio关联起来好丑,希望有属性可以禁止显示radio小圆圈
这个用户体验没有之前的合理
这个问题是不打算处理了吗?这样一点也不好用哦
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Existing Component
是
Component Name
Cascader
Description
请问2.9.0的一次重构取消掉change-on-select是出于什么考虑?
新特性 checkStrictly 能否覆盖之前的功能?
checkStrictly 和 el-ratio 为什么强制绑定?
why
change-on-select
was removed by a called "refactor"?can
checkStrictly
perfectly replacechange-on-select
?why
checkStrictly=true
means "el-ratio"?