Abstract: This application describes, in part, system and methods for reducing unintentional performance of actions, such as orders, on a computing device. In some implementations, ordering may be controlled by identifying an input within an action region and determining that the input is an intentional input before completing an order. For example, to be considered an intentional input, the input may need to remain in an action region for a predetermined time duration, or may need to move across a majority of the action region.

Abstract: A test device may include an application that accesses online content. In some examples, a test intermediary and/or a test user interface (UI) are downloaded to the test device in response to a request by the application for obtaining the content from a network location. The test intermediary may be positioned to receive communications between the application and the content during testing of the content and/or the application. For example, the test intermediary may intercept metrics and other callbacks passed between the content and the application during manual or automated testing. In some instances, the test intermediary may provide the metrics and/or other test outputs for display in the test user UI rendered on the test device. The content may be rendered to be functional within the test UI, and the existence of the test intermediary and/or the test UI may be transparent to the application and the content.

Abstract: This application describes, in part, system and methods for reducing unintentional performance of actions, such as orders, on a computing device. In some implementations, ordering may be controlled by identifying an input within an action region and determining that the input is an intentional input before completing an order. For example, to be considered an intentional input, the input may need to remain in an action region for a predetermined time duration, or may need to move across a majority of the action region.

Abstract: Before delivery to a user device, a document such as a hypertext markup language (HTML) file which includes one or more scripting elements is pre-processed by a processing server. The processing server renders the document to generate a processed document. The processing includes execution of one or more scripts in the document, including loading and initializing. This execution generates HTML fragments which are inserted into a document object model (“DOM”) tree. The processed document is sent along to the user device, which may quickly render the processed document and paint to a display or otherwise present output.

Abstract: A test device may include an application that accesses online content. In some examples, a test intermediary and/or a test user interface (UI) are downloaded to the test device in response to a request by the application for obtaining the content from a network location. The test intermediary may be positioned to receive communications between the application and the content during testing of the content and/or the application. For example, the test intermediary may intercept metrics and other callbacks passed between the content and the application during manual or automated testing. In some instances, the test intermediary may provide the metrics and/or other test outputs for display in the test user UI rendered on the test device. The content may be rendered to be functional within the test UI, and the existence of the test intermediary and/or the test UI may be transparent to the application and the content.

Abstract: A test device may include an application that accesses online content. In some examples, a test intermediary and/or a test user interface (UI) are downloaded to the test device in response to a request by the application for obtaining the content from a network location. The test intermediary may be positioned to receive communications between the application and the content during testing of the content and/or the application. For example, the test intermediary may intercept metrics and other callbacks passed between the content and the application during manual or automated testing. In some instances, the test intermediary may provide the metrics and/or other test outputs for display in the test user UI rendered on the test device. The content may be rendered to be functional within the test UI, and the existence of the test intermediary and/or the test UI may be transparent to the application and the content.

Abstract: A test device may include an application that accesses online content. In some examples, a test intermediary and/or a test user interface (UI) are downloaded to the test device in response to a request by the application for obtaining the content from a network location. The test intermediary may be positioned to receive communications between the application and the content during testing of the content and/or the application. For example, the test intermediary may intercept metrics and other callbacks passed between the content and the application during manual or automated testing. In some instances, the test intermediary may provide the metrics and/or other test outputs for display in the test user UI rendered on the test device. The content may be rendered to be functional within the test UI, and the existence of the test intermediary and/or the test UI may be transparent to the application and the content.