Microsoft Technology Licensing, LLC

Scott S Sheehan

Xiao Tu

Chee Chen Tong

Sebastian Poulose

Praveen Kumar Muralidhar Rao

Changsin Lee

Michael Z Stephens

Oren Freiberg

Alan W Stephenson

Robert K Mickle

Andrew Messick

Brandon Walderman

Techniques are presented for providing seamless extension porting. A second browser of a client device can receive a call to execute extension code containing function calls for a first browser. The extension code can further include a preload manifest key, which can include at least one bridge script property providing a bridge between function calls for the first browser and function calls for the second browser. In response to receiving the call to execute the extension code, the at least one bridge script property of the preload manifest key may be performed to execute the referenced bridge. Subsequently, remaining code of the extension code may then be executed. The bridge can receive function calls by the extension code. When a function call for the first browser is received, the bridge can map the function call for the first browser to a corresponding function call supported by the second browser.

Seamless extension porting

A primary user input mechanism is recommended to an application that executes on a computing device which supports a plurality of different user input mechanisms that users of the computing device can utilize to input information into the computing device. The utilization of each of the user input mechanisms is monitored on an ongoing basis, where this monitoring includes weighting each of the user input mechanisms based on its frequency of use. Upon receiving an indication to launch the application on the computing device, a one of the user input mechanisms currently having the highest weight is recommended to the application as being the primary user input mechanism. The weighting of each of the user input mechanisms is also provided to the application.

Input optimization based on frequency of use

APIs to test a device are described. In one or more implementations, a device includes a housing, one or more sensors supported by the housing, and one or more modules disposed within the housing that are implemented at least partially in hardware. The one or more modules are configured to process inputs detected using the one or more sensors and expose one or more application programming interfaces to a robot to cause the robot to perform one or more operations that are detectable by the one or more sensors, the one or more operations usable to test detection performed by the one or more sensors and the processing of the inputs performed by the one or more modules.

APIs to test a device

Growing community of inventors

Redmond, WA, United States of America

Scott S Sheehan