Abstract: An integrated approach is provided to running web applications with various compatibilities that do not require third-party extensions or sacrifice user experience. When a page of an application incompatible with a first browser is to be executed, an instance of a second browser with which the page is compatible is separately invoked and/or executed without opening a window for that second browser. Instead, the second browser opens a page within the window of the first browser. Moreover, rendering and/or contextual information for a page opened via the second browser is provided to the first browser. Such information is utilized by the first browser to provide a visual experience to the user in which the web page is being hosted by the first browser, even though it is in fact being hosted by the second browser.

Abstract: An integrated approach is provided to running web applications with various compatibilities that do not require third-party extensions or sacrifice user experience. When a page of an application incompatible with a first browser is to be executed, an instance of a second browser with which the page is compatible is separately invoked and/or executed without opening a window for that second browser. Instead, the second browser opens a page within the window of the first browser. Moreover, rendering and/or contextual information for a page opened via the second browser is provided to the first browser. Such information is utilized by the first browser to provide a visual experience to the user in which the web page is being hosted by the first browser, even though it is in fact being hosted by the second browser.

Abstract: Methods, systems, and computer program products are described herein for supporting and negotiating multiple (e.g. static) application programming interface (API) versions across multiple products. Interoperable programs, such as different web browser applications, may provide simultaneous support for multiple versions of an API. An API and program-API adapters may be versioned to manage compatibility for asynchronously developed programs and APIs that may be asynchronously installed and updated in many computing environments. An adapter may comprise a versioned portion of program source code. In-development program code and APIs may be forked to create versioned snapshots of stable interfaces. An “in-development” version of an API and adapters may coexist with versioned APIs and adapters. Compatible version negotiation may occur, for example, during process launch. Negotiation may activate the highest API version supported by both programs.

Abstract: Methods, systems, and computer program products are described herein for supporting and negotiating multiple (e.g. static) application programming interface (API) versions across multiple products. Interoperable programs, such as different web browser applications, may provide simultaneous support for multiple versions of an API. An API and program-API adapters may be versioned to manage compatibility for asynchronously developed programs and APIs that may be asynchronously installed and updated in many computing environments. An adapter may comprise a versioned portion of program source code. In-development program code and APIs may be forked to create versioned snapshots of stable interfaces. An “in-development” version of an API and adapters may coexist with versioned APIs and adapters. Compatible version negotiation may occur, for example, during process launch. Negotiation may activate the highest API version supported by both programs.

Abstract: An integrated approach is provided to running web applications with various compatibilities that do not require third-party extensions or sacrifice user experience. When a page of an application incompatible with a first browser is to be executed, an instance of a second browser with which the page is compatible is separately invoked and/or executed without opening a window for that second browser. Instead, the second browser opens a page within the window of the first browser. Moreover, rendering and/or contextual information for a page opened via the second browser is provided to the first browser. Such information is utilized by the first browser to provide a visual experience to the user in which the web page is being hosted by the first browser, even though it is in fact being hosted by the second browser.

Abstract: Web pages compatible with different web browsers are seamlessly rendered within the same tab of a single web browser window. A first browser is executed in a computing device, and has an open browser window. A request is received at the first browser to navigate to a first page. The first page is determined to be incompatible with the first browser and compatible with a second browser. Under control by the first browser, an instance of the second browser is invoked without a browser window opening for the instance of the second browser. An address of the first page is provided to the instance of the second browser. The instance of the second browser renders the first page within a tab in the open browser window of the first browser.

Abstract: Techniques for input processing based on input context are described. In at least some embodiments, a region of a display area includes multiple graphic elements that can be generated and/or managed by different components. Examples of such components include applications, plug-in modules, graphics frameworks, and so forth. Techniques discussed herein enable input to graphical elements to be handled in various ways, such as by routing the input to an appropriate component. Further, custom input contexts can be specified such that particular types and/or combinations of inputs can be interpreted.