Microsoft Technology Licensing, LLC

Matthew Allen Rakow

Justin Rogers

Tony Edward Schreiner

Kevin Michael Babbitt

Bradley Joseph Litterell

Praveen Kumar Muralidhar Rao

Christian Fortini

Stephen Harry Wright

Michael J Ens

Jacob Rossi

Arron J Eicholz

Sandra G Roberts

Yining Chen

Sylvain Pierre Galineau

Jane T Kim

Michael J Patten

Mirko Mandic

Nicholas Randall Waggoner

Rossen Atanassov

Sergey Z Malkin

Raju Ramanathan

Clark L Masterson

Amos Eshel

Rahul Arakeri

Aditya Vijay Govindarajan

Che-Wen Lo

Charu Chandiram

Siddhartha Prakash

Matthew J Esquivel

Techniques for web-based collaborative inking sessions via a computer network are described in this document. In one embodiment, a first computer can serialize detected pointer input at a first computer into data representing one or more ink objects individually representing an image or animation corresponding to the detected pointer input. The first computer can then transmit the data representing the serialized ink objects to the second computer via the computer network. Upon receiving the transmitted data, the second computer can de-serialize the received serialized ink objects, reconstruct the image or animation corresponding to the detected pointer input at the first computer, and surface, to a second user, the image or animation of the detected pointer input on a second web browser surfacing the same webpage on the second computer, thereby enabling a web-based collaboration session between the first and second users.

Web-based collaborative inking via computer networks

In at least some embodiments, a mechanism is provided for web developers to request specific default behaviors, such as touch behaviors, on their webpages. In at least some implementations, a Cascading Style Sheets (CSS) rule is utilized to enable or disable manipulations such as panning, pinch zoom, and double-tap-zoom manipulations. The mechanism can be extensible to accommodate additional default behaviors that are added in the future. In various embodiments, the behaviors are declared up front and thus differ from solutions which employ an imperative model. The declarative nature of this approach allows achievement of full independence from the main thread and deciding the correct response using independent hit testing.

Declarative style rules for default touch behaviors

Techniques for scale factor based on viewing distance are described. In at least some embodiments, a viewing distance refers to a distance at which a user typically views and/or is viewing a display device. For instance, different displays can be used in different ways and for different purposes, and thus may have different viewing distances. Techniques discussed herein consider the estimated viewing distance of a particular display in determining a scale factor to be applied to visual elements (e.g., graphics) for output via the particular display. A scale factor, for instance, can specify that visual elements are to zoomed-out or zoomed-in prior to be displayed. As detailed herein, this enables a consistent viewing experience to be maintained across different devices with different display sizes and different viewing distances.

Scale factor based on viewing distance

Various embodiments utilize a layout viewport and a visual viewport separate from the layout viewport. The layout viewport is utilized for such things as page layout operations and reporting Document Object Model values to script. The layout viewport can be thought of as an initial rectangle which is equivalent in size to the initial containing block. The initial containing block is a containing block that contains web content that is initially visible to the user. The visual viewport is separate from the layout viewport and is allowed to be freely manipulated relative to the layout viewport. For example, the visual viewport may 'push' the layout viewport around when it collides with the layout viewport boundaries. The visual viewport can be thought of as the rectangle that is visible to the user.

Virtual viewport and fixed positioning with optical zoom

Instantiable gesture object techniques are described in which native gesture functionality is abstracted to applications using a script-based recognition interface. Gesture objects may be instantiated for different interaction contexts at the direction of applications programmed using dynamic scripting languages. Gesture objects can be configured to designate particular touch contacts and/or other inputs to consider for gesture recognition and a target element of content to which corresponding recognized gestures are applicable. After creation, gesture objects manage gesture processing operations on behalf of the applications including creating recognizers with the native gesture system, feeding input data for processing, and transforming raw gesture data into formats appropriate for the application and/or a target element. Accordingly, script-based applications may use the gesture objects to offload processing tasks associated with gesture recognition and take advantage of native gesture functionality.

Instantiable gesture objects

In one or more embodiments, a hit test thread which is separate from the main thread, e.g. the user interface thread, is utilized for hit testing on web content. Using a separate thread for hit testing can allow targets to be quickly ascertained. In cases where the appropriate response is handled by a separate thread, such as a manipulation thread that can be used for touch manipulations such as panning and pinch zooming, manipulation can occur without blocking on the main thread. This results in the response time that is consistently quick even on low-end hardware over a variety of scenarios.

Independent hit testing

In at least some embodiments, a mechanism is provided for web developers to request specific default behaviors, such as touch behaviors, on their webpages. In at least some implementations, a Cascading Style Sheets (CSS) rule is utilized to enable or disable manipulations such as panning, pinch zoom, and double-tap-zoom manipulations. The mechanism can be extensible to accommodate additional default behaviors that are added in the future. In various embodiments, the behaviors are declared upfront and thus differ from solutions which employ an imperative model. The declarative nature of this approach allows achievement of full independence from the main thread and deciding the correct response using independent hit testing.

Various embodiments enable repetitive gestures, such as multiple serial gestures, to be implemented efficiently so as to enhance the user experience. Other embodiments provide various approaches to zoom operations that consider a particular element's contextual surroundings in making a zoom decision that is designed to enhance the user experience and provide efficiently-zoomed content given a device's or rendering container's form factor.

Input pointer delay and zoom logic

Growing community of inventors

Seattle, WA, United States of America

Matthew Allen Rakow