Abstract: In various embodiments, a web browser user interface includes a subset of selected controls distributed along a single line at the top of the web browser user interface. Layouts of the controls can be in a left-to-right or a right-to-left fashion. Specifically, in a left-to-right layout, selected controls meeting certain criteria can appear to the left of other controls. Similarly, in a right-to-left layout, selected controls meeting certain criteria can appear to the right of other controls. In at least some embodiments, at least some of the controls that appear distributed along the single line are controls that are related to navigation of some type. Such controls can include those that enable textual input to be provided by user.

Abstract: Various embodiments provide a notification bar user interface control that is designed to help users maintain focus on their browsing activities, while offering notifications in the form of suggestions. In at least some embodiments, the notification bar user interface control is non-modal and is presented at a location within the browsing field-of-view that is selected to reduce user distraction. Further, in at least some embodiments, the notification bar user interface control is presented in a manner which overlays content of the web page and thus, does not cause layout of the web page to be changed.

Abstract: Various embodiments provide a mechanism to allow end users to install web applications and websites onto their desktop. In accordance with one or more embodiments, client-side code can be utilized to allow developers associated with a website to define boundaries associated with user interaction, and have those boundaries enforced by a run-time engine. In at least some embodiments, developers can provide, through JavaScript code and/or HTML markup, various configurations for the creation of a start menu shortcut, navigation, and so-called jumplist integration.

Abstract: Various embodiments provide a mechanism to allow end users to install web applications and websites onto their desktop. In accordance with one or more embodiments, client-side code can be utilized to allow developers associated with a website to define boundaries associated with user interaction, and have those boundaries enforced by a run-time engine. In at least some embodiments, developers can provide, through JavaScript code and/or HTML markup, various configurations for the creation of a start menu shortcut, navigation, and so-called jumplist integration.

Abstract: An application programming interface (API) layer is implemented on a computing device. The API layer allows a local application(s) executing on the computing device to access web data in a data store layer, and further allows a remote application(s) that is executing on some other computing device to access the web data in the data store layer. Additionally, this web data can include web pages, some of which may include structured data and some of which may not include structured data. A web browser is permitted to access the web data store via the object model, and generate a user interface based at least in part on these web pages.

Abstract: The embodiments described above utilize and leverage RSS to enable a user to interact more easily with different types of data, or data from different sources that are available over the web. In accordance with at least some embodiments, a hostable and/or customizable control is provided and gives the user the ability to interact with RSS feeds to store and further manipulate collections of items from different RSS feeds.

Abstract: A tag management system that enables consolidation, aggregation and/or synchronization of tags between local and remote sources. Further, the system provides users with a single rich view of client and Internet data related to appropriate tagging schemes. The system allows users to import and export tags and taxonomies from online service providers and provides a central location for users to store their tags. The central location is accessible to the user both on the client and for use online.

Abstract: An application programming interface (API) layer is implemented on a computing device. The API layer allows a local application(s) executing on the computing device to access web data in a data store layer, and further allows a remote application(s) that is executing on some other computing device to access the web data in the data store layer. Additionally, this web data can include web pages, some of which may include structured data and some of which may not include structured data. A web browser is permitted to access the web data store via the object model, and generate a user interface based at least in part on these web pages.

Abstract: System(s) and/or method(s) (“tools”) are described that present content in a user interface tailored to trait(s) of the content. The tools can analyze content to determine its traits, classify the content based on its traits, and present the content in a user interface tailored to the classification. The tools can also organize content items into groups based on a common trait and enable a user to select content items through their group. Responsive to the user's selection of a group, the tools can present content, render enclosures, and alter traits of the content items in the group.

Abstract: Various embodiments can provide a convenient way of sending selected online content to one or more applications, such as an application running on a local machine, a web application, a web service, and so on. In at least some embodiments, one or more accelerators can be presented to a user based at least in part on a user having selected content and the nature of the content that the user has selected. An accelerator can serve as a pipeline that can send the selected content to one or more applications. A variety of different accelerators can be utilized, and each accelerator can be suited to handle a particular type or types of content. A user can select a particular accelerator, which can cause an application associated with the accelerator to be launched and selected content to be provided to the application.

Abstract: Systems and methods are described that enable handwriting into a data-entry field on a screen without independently selecting that data-entry field. These systems and methods can also provide a handwriting guide geographically associated with a data-entry field into which a user is intending to write that permits substantially all of a computing device's screen to be viewed.

Abstract: Live update display techniques associated with displaying subscribable content live consumed outside of a Web page are described. In at least some embodiments, information received on the device is used to determine that subscribable content from a Web source has been updated. This information, however, may not represent the source to be used for consumption. Therefore, the content to be used for consumption that includes display markup can be retrieved from a source other than the device, such as a display Web page, and used to display subscribable content on the device.

Abstract: Various embodiments enable discovery of functionality associated with a webpage's content. In at least some embodiments, a user interface instrumentality can be automatically presented to a user to inform the user of functionality associated with content appearing on a webpage. The user interface instrumentality can, in some instances, reside in the form of a clickable button that is automatically presented when a user moves their cursor on or near a particular piece of webpage content. By clicking on the presented button, the user can access functionality associated with the particular piece of webpage content. In at least some other embodiments, a browser's chrome includes a discovery button that provides a listing of items that have functionality that can be performed relative to the items.

Abstract: Various embodiments can enable a webpage publisher to describe structured data on a webpage in a manner that enables a Web browser to intelligently present activities that pertain to user selections relative to the structured data appearing on the webpage. In at least some embodiments, a webpage publisher can provide markup that identifies structured data on a webpage. A service provider can provide a representation that describes the types of structured data in which it is interested, and how to handle the structured data responsive to a user selection. The Web browser can then use the markup in the webpage and the service provider's representation to identify and present activities associated with structured data selected by the user.

Abstract: In one or more embodiments, a Web browser is configured to enable a user to open a new tab and, responsively, display one or more activities in a new tab page for the user. The user can then select, from the new tab page, one or more activities to be performed. In at least some embodiments, a user can select an object in a first tab page, open a new tab page, and select an activity on the new tab page that is to be performed relative to the selected object.

Abstract: Service initiation techniques are described. In at least one implementation, a computing device receives a selection of text that is displayed in a user interface by an application. Selection is detected of one of a plurality of services that are displayed in the user interface. Responsive to the detection, the selection of text is provided to the selected service without further user intervention.

Abstract: Various embodiments provide a model through which service providers can describe offered services using a standardized format. In one or more embodiments, the standardized format is declarative and enables service providers to describe their associated services in a standardized way. In at least some embodiments, the standardized format includes a set of common service properties that are shared across multiple different services. Additionally, service specific properties can be described in addition to the common service properties. In one or more embodiments, existing services can be extended by including, in the standardized format, a description of an extension. In one or more other embodiments, new services can be added for consumption by simply including a description of the new service using the standardized format.

Abstract: In one or more embodiments, users are able to access small previews of a service from within their present application context. For example, users can install various services in an application, such as a Web browser. Based upon a user action within the application, a user interface instrumentality can be presented to the user to enable them to access a list of services that are installed in the application. By taking an action with respect to the list of services, a user can access a preview of the service. Further service functionality can be accessed from a preview by interacting with the preview in a particular way.

Abstract: Systems and/or methods that enable creation and/or use of an action for an electronic form dependent on a role of a user are described.