Microsoft Technology Licensing, LLC

Microsoft Corporation

Nicholas Randall Waggoner

Ross Nathaniel Luengen

Jan-Kristian Markiewicz

Orry Wijanarko Soegiono

Rebecca J Deutsch

Holger Kuehnle

Michael J Patten

Gerrit H Hofmeester

Paul J Kwiatkowski

Robert Disano

Nicolas J Brun

Theresa B Pittappilly

William D Carr

Laurent Mouton

Paul Armistead Hoover

Harold S Gomez

Song Zou

Jon Gabriel Clapper

Michael Nelte

John Wesley Terrell

Megan Ann Bates

Yun Lin

Alex Mogilevsky

Jason L Cohen

Markus W Mielke

Christian Fortini

Michael J Ens

Matthew Allen Rakow

Benjamin T Arai

Bonny Lau

Sebastian Poulose

Sergey Z Malkin

Sandra G Roberts

Yining Chen

Eugene Veselov

Paul Stephen Gildea

Hilal Shaath

Koti Kiran Chegondi

Craig Boucher

Christopher Lyman Jones

Jose Marcos De Oliveira

Semantic zoom techniques are described. In one or more implementations, techniques are described that may be utilized by a user to navigate to content of interest. These techniques may also include a variety of different features, such as to support semantic swaps and zooming 'in' and “out.” These techniques may also include a variety of different input features, such as to support gestures, cursor-control device, and keyboard inputs. A variety of other features are also supported as further described in the detailed description and figures.

Semantic zoom animations

Semantic zoom techniques are described. In one or more implementations, techniques are described that may be utilized by a user to navigate to content of interest. These techniques may also include a variety of different features, such as to support semantic swaps and zooming 'in' and 'out.' These techniques may also include a variety of different input features, such as to support gestures, cursor-control device, and keyboard inputs. A variety of other features are also supported as further described in the detailed description and figures.

Various embodiments provide a travel log for manipulation of content. In at least some embodiments, the travel log can be presented as a visual element of a web browser and can enable a user to navigate through visited content (e.g., web pages) via manipulation of the content using touch-based and/or touchless gestures. Implementations can facilitate navigation through content by representing the travel log as a visual 'time line' of visited content that can be scrolled via manipulation through a web browser user interface. For example, a user can navigate the travel log to older content by manipulating the travel log in one direction, and can navigate the travel log to newer content by manipulating the travel log in a different direction.

Travel log for manipulation of content

This document describes techniques and apparatuses for asynchronous handling of a user interface manipulation. These techniques handle a user interface manipulation with two or more asynchronous processes. One asynchronous process, for example, may determine a position responsive to the user interface manipulation while another asynchronous process determines the pixels to render. By so doing, these techniques enable a quick and/or consistent response to a user interface manipulation.

Asynchronous handling of a user interface manipulation

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

This document describes content-based snap points and techniques that use these snap points. In some embodiments, multiple content-based snap points are used to stop at points in content that are convenient, prevent overshooting of important parts in the content, and/or aid user's in manipulating and consuming the content.

Content-based snap point

This document describes techniques and apparatuses for predictive tiling. These techniques predict tiles of content to pre-render so that an application will be ready to render content quickly in response to a user manipulation. By so doing, these techniques enable fast manipulation of content without unduly impacting drawing resources.

Predictive tiling

Content can be flowed through one or more containers that can be laid out analogously to printed material. Content is flowed into the first specified container until that container is 'full' of content. Subsequent content is then flowed through subsequent containers, each of which is individually identified, and whose ordering is specified independently of their position and visual presentation. Multiple independent sources of content can be flowed through multiple independent collections of containers. Each container can format the content presented within it independently from other containers, and each container can comprise script, or other programmatic constructs, which can operate on, and modify, the content flowed into such a container. To provide for the rich layouts, content containers can be nested inside one another such that multiple layers, or levels, of the layout can be edited independently of one another.

Content flow through containers

Display screen with animated graphical user interface

A URL reputation system may have a reputation server and a client device with a cache of reputation information. A URL reputation query from the client to the server may return reputation data along with probabilistic set membership information for several variants of the requested URL. The client may use the probabilistic set membership information to determine if the reputation server has additional information for another related URL as well as whether the classifications are inheritable from one of the variants. If the probabilistic set membership determines that the reputation server may have additional information, a query may be made to the reputation server, otherwise the reputation may be inferred from the data stored in the cache.

URL reputation system

Growing community of inventors

Newcastle, WA, United States of America

Nicholas Randall Waggoner