Tags: MaterialDesignInXAML/MaterialDesignInXamlToolkit
Tags
Fix horizontal ScrollBar placement for multi-line TextBox (#3934) * Add simple issue repro to Home page * WIP on fix. Scroll position is now synced correctly, but the visibility property still needs to be respected properly. * TextBox.HorizontalScrollBarVisibility is now respected * Add null guards and possibly not-needed method SizeChanged() invoke * Remove not needed invocation and null forgiving operators * Place custom scrollbar correctly using converters * Cleanup * Take hover/focus state into account + ignore margins on hidden elements * Only consider hover/focus when style is outlined * Removing simple repro from Home page * Update demo app with TextBox.TextWrapping option on Field page * Fix initial state of custom ScrollBar * Renames property for clarity. Renames `isOutlinedStyle` to `hasOutlinedTextField` in `TextBoxHorizontalScrollBarMarginConverter` for better clarity and consistency. * Improves UI test reliability Adds retry logic to clear button click in date picker test; captures a screenshot of the split button popup during UI test. * Moved converters into "internal" namespace * Moved behavior into new "internals" namespace for behaviors --------- Co-authored-by: Kevin Bost <[email protected]>
[SmartHint] Hint placement for "readonly" controls (#3764) * Demo app workaround/hack for initial miscalculation of hint placement * Ensure ComboBox smart hint behaves according to MD spec According to the "Behavior" section of the "Menus" page in the link below, the hint should float even when there is no selection, but the popup is open. https://m2.material.io/components/menus#exposed-dropdown-menu * Fix hint positioning issue when "readonly" element The issue was present for all controls once they are in "readonly" state. Special handling of the case where the element is readonly, and the hint should follow the prefix/suffix needed to be added because of the "business rule" that prefix/suffix is always visible when the element is "readonly". * Fixing so the hack is no longer needed * Fix AutoSuggestBox as well --------- Co-authored-by: Kevin Bost <[email protected]>
Grammatical fixes to App.xaml (#3468) Reformatted comment lines to adhere to correct English grammar: - Included some colons - Changed 'setup' (a noun) to 'set up' (a verb) - 'built-in' is hyphenated - 'as well' is not needed when existing sentence has the word 'also'
Fix PasswordBox keyboard focus traversal issue (#3096) * Extend SmartHint demo page with new features * Handle forward/backward keyboard focus on reveal style PasswordBox * Add UI test to verify tabbing works * Fix issue with backwards focus traversal when hiding a revealed password * Update UI test with syntax feature which is hopefully added to XAMLTest * Rev'ing XAMLTest --------- Co-authored-by: Kevin Bost <[email protected]>
Add option for custom popup placement for ComboBox (#3005) * Add special ComboBox popup handling for 90 degrees rotation Popup placement was wrong in case a LayoutTransform was applied to rotate the ComboBox. The default WPF ComboBox does respect this, and thus so should MDIX. To RotateTransfrom.Angle is compared against values of 90 and -90 (10 digit precision) to determine whether this is a rotation where the special handling should be applied. * Refactor custom popup placement into publicly exposed callback Rather than handling arbitrary rotations in the library itself, we expose a callback which can then be used to rotate the popup shown by the combobox such that it matches the users needs. * Update MaterialDesignThemes.Wpf/ComboBoxPopup.cs Co-authored-by: Kevin B <[email protected]> * Fix compile error Co-authored-by: Kevin B <[email protected]>
PreviousNext