https://bugs.documentfoundation.org/show_bug.cgi?id=140911
--- Comment #10 from Heiko Tietze <[email protected]> --- (In reply to sdc.blanco from comment #9) > 1. "True" => you agree that it would be informative for the user? Yes > 2. "but..." => it would be too difficult to do, compared to the advantage? > => worth doing (if it is not difficult)? You have to compare every single attribute that can be changed with this dialog to know whether or not the button is to enable. It's not difficult but cumbersome and error-prone (any later change needs to be tracked too). The advantage of the disabled button does not outweigh the effort for me. Keep in mind that you want to kind of document the UI rather than blocking input. > 3. Presumably "every single attribute" was meant to imply "too difficult". > 4. But does "every single attribute" refer to all attributes for a style or > only to the current tab (which is what is actually required). In any case, you have to collect all the details. And there are some attributes hidden in extra dialogs. > All attributes for a tab (alone) may be more manageable. If the attributes are tab-dependent you have to collect all plus on which tab it is located. You are welcome to implement, UX-wise it won't interrupt anyone's workflow and is an improvement :-) -- You are receiving this mail because: You are the assignee for the bug.
