Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Commands pane sometimes does not react to changes in commands' states #83

Open
oleq opened this issue May 25, 2020 · 0 comments
Open

Commands pane sometimes does not react to changes in commands' states #83

oleq opened this issue May 25, 2020 · 0 comments
Labels
domain:dx squad:core Issue to be handled by the Core team. type:bug

Comments

@oleq
Copy link
Member

oleq commented May 25, 2020 •
edited
Loading

For instance, when the editor becomes read–only or forceDisabled is used. This is because the commands pane listens to change:range only instead of individual command properties. This saves a lot of effort because instead of hundreds of listeners (dozens of commands × [ isEnabled, value ]) but it falls short in some cases.
@oleq oleq added the type:bug label May 25, 2020
@jodator jodator added this to the nice-to-have milestone Aug 26, 2020
@Reinmar Reinmar added squad:core Issue to be handled by the Core team. and removed squad:ux labels Sep 27, 2021
@pomek pomek removed this from the nice-to-have milestone Feb 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
domain:dx squad:core Issue to be handled by the Core team. type:bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@Reinmar @jodator @oleq @pomek