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 provided for detecting a browser hang condition and causing the browser to enter into a mitigation state. For instance, a window or tab of the browser executes via a first thread of the browser, and third-party code executes via a second thread of the browser. The first thread issues a hang resistance message to the second thread and waits for a response from the second thread. The second thread processes the hang resistance message after processing all other messages in its queue. Thus, if the first thread receives the response, the first thread determines that the second thread has not entered into a hang condition. However, if the first thread does not receive the response, the first thread determines that the second thread has entered into a hang condition and subsequently causes the browser to enter the mitigation state.

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 provided for detecting a browser hang condition and causing the browser to enter into a mitigation state. For instance, a window or tab of the browser executes via a first thread of the browser, and third-party code executes via a second thread of the browser. The first thread issues a hang resistance message to the second thread and waits for a response from the second thread. The second thread processes the hang resistance message after processing all other messages in its queue. Thus, if the first thread receives the response, the first thread determines that the second thread has not entered into a hang condition. However, if the first thread does not receive the response, the first thread determines that the second thread has entered into a hang condition and subsequently causes the browser to enter the mitigation state.