Throws a XamlParseException on duplicate x:Key on RDs. This will find
duplicate in xaml, but duplicates can still happen if the RD is modified
in code. Those dupes are already detectd at runtime.
- helps, but doesn't fixes, #3512
* Test rapid MDP swaps
* [Android] Prevent white screen flash
* [Android] Prevent crashes on rapid page swaps
* Shorten test time
* Preserve old code just in case
* Remove flaky test from main run
Confirmed that it doesn't ever crash on UITest
* More info in 1601 test
* Update NavigateToTestPage to await test cases page
This lets the page render and then clean itself up when we switch to the test case, which allows the test case for 1601 to actually render with a compressed layout after my change to Platform.
* Remove call to FragmentManager.ExecutePendingTransactions in MasterDetailContainer
this code was only added to prevent the page flicker, and it caused more issues than it solved.
* SetPage will now delay removing views until the new views are in place
* Prevent crash when a leaked cell in ListView with Recycle mode has MenuItem with bindings and framework like Xamarin.Forms sets BindingContext to null after leaving the page
* Made SetupSelection static
The Completed event should be invoked when the user presses the return key only. Using NSTextField DidEndEditing is not favorable because pressing the Tab key will cause this method as well
Due to a flux in the matrix, Bindings with a TargetNullValue assigned
were always returning that value. It had the advantage of being right
sometimes, but the inconvenient for being wrong, most of the times.
By properly aligning the bits of the register with the sun at beer time,
we can avoid that side effect, and actually returns a value when the
binding is succesful, and the TargetNullValue whem the Binding returns
null.
- fixes#3467
* add ability to control smooth scrolling
* added test case
* removed test case
* add test button
* EnableGesture should be controlled by another platform specific
To allow mapping a single CSS property to multiple controls, we so far
relied on extracting the BindableProperties to static helper classes,
and implementing an interface for accessors, and eventually change
handlers.
That extraction works well, and is actually a good pattern, as long as:
- the extracted BPs share the same PropertyName,
- default value, and
- return type, obiously
As the CSS `color` property has to map to both `TextColor` and `Color`
BPs, the property extraction wasn't possible.
This change adds the capability to map a single CSS property to
multiples BPS, when extraction isn't possible. Whenever the extraction
to an interface is possible, that behavior is strongly encouraged.
Rui Marinho
Stephane Delcroix
E.Z. Hart
Samantha Houts
Samantha Houts
Shane Neuville
Javier Suárez Ruiz
E.Z. Hart
Morten Nielsen
Pavel Yakovlev
flyofsky
Mohamed CHOUCHANE
Sławomir Kulików
sung-su.kim
Vitaly Knyazev
John VanSickle
Rob Lyndon
Alan McGovern
adrianknight89
kingces95