Comment on attachment 703503 [details] UC-75 Activate the find in page app bar > The tabs app bar, navigation app bar, and context app bar all roll up > and are replaced by a find in page app bar which sits at the top of the > screen and the soft keyboard that sits at the bottom of the screen. Generally, Windows will not show the on-screen keyboard unless the user taps in a text input box. It even puts technical restrictions in place to prevent apps from showing the keyboard at any other time. (And while it *might* be technically possible to hack around those restrictions, it would be in direct conflict with the Metro UX guidelines.) "The invocation model of the touch keyboard is designed to put the user in control of the keyboard. Users indicate to the system that they want to input text by tapping on an input control instead of having an application make that decision on their behalf. This reduces to zero the scenarios where the keyboard is invoked unexpectedly, which can be a painful source of UI churn because the keyboard can consume up to 50% of the screen and mar the application's user experience. To enable user-driven invocation, we track the coordinates of the last touch event and compare them to the location of the bounding rectangle of the element that currently has focus. If the point is contained within the bounding rectangle, the touch keyboard is invoked. "This means that applications cannot programmatically invoke the touch keyboard via manipulation of focus... There are certain scenarios where it doesn't feel great to have to tap to get the keyboard, such as when a user has started a new email message or has opened the Search pane. However, we feel that requiring the user to tap the input field is an acceptable compromise." http://msdn.microsoft.com/en-us/library/windows/apps/hh465404.aspx#user-driven_invocation

OK. Let's drop the "and the soft keyboard that sits at the bottom of the screen." The user will have to tap the actual find in page text field in the find in page app bar before the OSK will be retrieved.

Based on bug 838242 comment 4, the story should be updated to say the find bar is at the *bottom* of the screen (rather than the top).

What's left here to do before closing this story? It has no further active dependencies.

There is the on screen keyboard overlapping the find bar but that's blocking the find first instance of text in a page story. (See Bug 857437 - Defect - OSK overlapping "Find" app bar). So I think this can be closed.