Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 52464 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 19796 [details]
Per the attached repro, a SearchCommand that returns false for CanExecute disables the text input on the search bar. This means that if you want a command that can only execute when text is entered, the bar disables when there is no text, hence preventing the user from actually entering text. I believe the SearchBar should simply refuse to execute the command when it is unavailable, not change prevent text entry.
This is something that will need to be discussed as there is a similar report (#51147) which appears to expect the opposite behavior and that the UI element should be disabled when CanExecute is false. For things such as this we should probably hold some level of consistency for what the user can expect and document it accordingly.
@Paul I'm not sure I agree #51147 is a duplicate. It argues the "button" should be disabled, whereas I'm arguing the "textbox" should not be. Limitations of the native platform may mean they are one and the same, but the visual distinction remains and I suspect is the underlying cause for the differing expectations.