Abstract: A digital assistant includes an extensibility client that interfaces with application extensions that are built by third-party developers so that various aspects of application user experiences, content, or features may be integrated into the digital assistant and rendered as native digital assistant experiences. Application extensions can use a variety of services provided from cloud-based and/or local sources such as language/vocabulary, user preferences, and context services that add intelligence and contextual relevance while enabling the extensions to plug in and operate seamlessly within the digital assistant context. Application extensions may also access and utilize general digital assistant functions, data structures, and libraries exposed by the services and implement application domain-specific context and behaviors using the programming features captured in the extension.

Abstract: 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.

Abstract: A lock includes a housing, a cylindrical core body and a tumbler unit. The core body is rotatably mounted in the housing, and includes a core axle, and a core tube sleeved on the core axle. The core axle has a helical keyway. The tumbler unit includes a housing pin hole formed in the housing, a tube through hole formed through the core tube, a pin assembly movably mounted in the housing pin hole and the tube through hole, a hole-defining surface defining the tube through hole and having a shoulder surface portion, and a resilient member disposed in the housing and resiliently biasing the pin assembly to abut against the shoulder surface portion and extend into the helical keyway.

Abstract: A lock includes a housing, a cylindrical core body and a tumbler unit. The core body is rotatably mounted in the housing, and includes a core axle, and a core tube sleeved on the core axle. The core axle has a helical keyway. The tumbler unit includes a housing pin hole formed in the housing, a tube through hole formed through the core tube, a pin assembly movably mounted in the housing pin hole and the tube through hole, a hole-defining surface defining the tube through hole and having a shoulder surface portion, and a resilient member disposed in the housing and resiliently biasing the pin assembly to abut against the shoulder surface portion and extend into the helical keyway.

Abstract: A digital assistant includes an extensibility client that interfaces with application extensions that are built by third-party developers so that various aspects of application user experiences, content, or features may be integrated into the digital assistant and rendered as native digital assistant experiences. Application extensions can use a variety of services provided from cloud-based and/or local sources such as language/vocabulary, user preferences, and context services that add intelligence and contextual relevance while enabling the extensions to plug in and operate seamlessly within the digital assistant context. Application extensions may also access and utilize general digital assistant functions, data structures, and libraries exposed by the services and implement application domain-specific context and behaviors using the programming features captured in the extension.

Abstract: Techniques for extension interaction with applications are described. Generally, an extension represents functionality for extending, modifying, customizing, and/or supplementing native functionality of an application. Techniques discussed herein provide a common extension platform that enables an extension to interact with multiple different applications utilizing components of the platform. The common extension platform, for instance, exposes a set of common extension application programming interfaces (APIs) that provide a common interaction surface between extensions and applications.

Abstract: A digital assistant includes an extensibility client that interfaces with application extensions that are built by third-party developers so that various aspects of application user experiences, content, or features may be integrated into the digital assistant and rendered as native digital assistant experiences. Application extensions can use a variety of services provided from cloud-based and/or local sources such as language/vocabulary, user preferences, and context services that add intelligence and contextual relevance while enabling the extensions to plug in and operate seamlessly within the digital assistant context. Application extensions may also access and utilize general digital assistant functions, data structures, and libraries exposed by the services and implement application domain-specific context and behaviors using the programming features captured in the extension.

Abstract: 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.

Abstract: Techniques for extension interaction with applications are described. Generally, an extension represents functionality for extending, modifying, customizing, and/or supplementing native functionality of an application. Techniques discussed herein provide a common extension platform that enables an extension to interact with multiple different applications utilizing components of the platform. The common extension platform, for instance, exposes a set of common extension application programming interfaces (APIs) that provide a common interaction surface between extensions and applications.

Abstract: A model for presenting non-installed applications that enable the user to share the type of content that a user is accessing. For instance, the application might be a computing program, a web service, and so forth. The model may present both installed and not installed content sharing applications in a user interface menu. For a given user interface menu, there would be a list of visualizations, each of which is associated with one of the content sharing applications. The user may select one or more non-installed applications to share the content. Furthermore, the model may select the applications to be presented in the list based on a number of different factors; for instance, the location of the user, a language of the content, a web service the user accessed, an application that is installed by a user's contacts, and so forth.

Abstract: Techniques for extension interaction with applications are described. Generally, an extension represents functionality for extending, modifying, customizing, and/or supplementing native functionality of an application. Techniques discussed herein provide a common extension platform that enables an extension to interact with multiple different applications utilizing components of the platform. The common extension platform, for instance, exposes a set of common extension application programming interfaces (APIs) that provide a common interaction surface between extensions and applications.

Abstract: Techniques are described for improving language translation of content (e.g., web content) on computing devices (e.g., mobile computing devices). For example, automatic translation can be performed when entering reading view in association with displayed web content by determining that the displayed web content is not in a language that is understood by the user (e.g., as indicated by language settings). As another example, language-related meta-data can be passed between applications and used in language detection of content, such as web content.

Abstract: A digital assistant includes an extensibility client that interfaces with application extensions that are built by third-party developers so that various aspects of application user experiences, content, or features may be integrated into the digital assistant and rendered as native digital assistant experiences. Application extensions can use a variety of services provided from cloud-based and/or local sources such as language/vocabulary, user preferences, and context services that add intelligence and contextual relevance while enabling the extensions to plug in and operate seamlessly within the digital assistant context. Application extensions may also access and utilize general digital assistant functions, data structures, and libraries exposed by the services and implement application domain-specific context and behaviors using the programming features captured in the extension.

Abstract: Techniques for extension interaction with applications are described. Generally, an extension represents functionality for extending, modifying, customizing, and/or supplementing native functionality of an application. Techniques discussed herein provide a common extension platform that enables an extension to interact with multiple different applications utilizing components of the platform. The common extension platform, for instance, exposes a set of common extension application programming interfaces (APIs) that provide a common interaction surface between extensions and applications.

Abstract: Techniques for extension interaction with applications are described. Generally, an extension represents functionality for extending, modifying, customizing, and/or supplementing native functionality of an application. Techniques discussed herein provide a common extension platform that enables an extension to interact with multiple different applications utilizing components of the platform. The common extension platform, for instance, exposes a set of common extension application programming interfaces (APIs) that provide a common interaction surface between extensions and applications.

Abstract: A web browser has a user interface that includes a content rendering area within the web browser user interface and a control layout area adjacent the content rendering area. The control layout area includes a user-selectable icon that is always available to the user in the control layout area and which is user-configurable. For example, the user-configurable icon may be configured with one of two pre-defined functions. In one illustrative implementation the two pre-defined functions may be a tabs function and a favorites function.

Abstract: Techniques are described for improving language translation of content (e.g., web content) on computing devices (e.g., mobile computing devices). For example, automatic translation can be performed when entering reading view in association with displayed web content by determining that the displayed web content is not in a language that is understood by the user (e.g., as indicated by language settings). As another example, language-related meta-data can be passed between applications and used in language detection of content, such as web content.

Abstract: A web browser has a user interface that includes a content rendering area within the web browser user interface and a control layout area adjacent the content rendering area. The control layout area includes a user-selectable icon that is always available to the user in the control layout area and which is user-configurable. For example, the user-configurable icon may be configured with one of two pre-defined functions. In one illustrative implementation the two pre-defined functions may be a tabs function and a favorites function.

Abstract: Embodiments of the present invention provide a die stack including a first substrate, a first die bonded to the first substrate, a second substrate having a cavity sized and shaped to fit over the first die, and a second die bonded to at least a portion of a rim of the cavity.

Abstract: In one embodiment, the present invention includes a semiconductor package having a substrate, a semiconductor die with a first surface opposing the substrate and a second surface, a metal layer formed on the second surface of the semiconductor die, and a mold layer formed on the substrate. In some embodiments, the mold layer is substantially coplanar with the metal layer to improve package performance. Other embodiments are described and claimed.