Bring Narrator focus to XAML island#15611
Conversation
protikbiswas100
left a comment
protikbiswas100
left a comment
There was a problem hiding this comment.
Are member fields like m_fragmentRootAutomationProviderRequestedToken still present? If so, should they be removed to avoid dead code/ confusion ?
Good eyes. Removed now. |
* Use automationoption as frameworkbased for childsite * Change files * remove tokens associated with fragment based
* Use automationoption as frameworkbased for childsite * Change files * remove tokens associated with fragment based
|
@vineethkuttan The fix itself is okay, but let's switch b/w fragment-based and framework-based implementation depending on the flag This would make this fix wholistic. The RNW core itself would continue to be generic (agnostic of XAML). This would be useful if we've a new derivate of CC: @acoates-ms, @vivekkhare31 |
5 participants
Description
Earlier for childsite link automation we were fragment-based option. Since XAML island will take care of it automation on its own , we are using framework-based option
Type of Change
Erase all that don't apply.
Why
To bring narrator focus to the XAML island cause of community modules native components are using XAML Island.
Resolves [ #15320 ]
What
Changed automation option for child site to be framework based.
Screenshots
xaml2.mp4
Testing
Tested in playground.
Changelog
Should this change be included in the release notes: yes
Bring Narrator focus to the XAML island