Abstract: Implementations discussed herein provide a way for an application to host a graphical element from another application in its own window, such as in its graphical user interface (GUI). A host application that hosts a component graphical element of a component application can control the lifetime and visual appearance of the component graphical element, while the component application provides content for display within the component graphical element.

Abstract: A security element is displayed that provides information to a user to help ensure that they are not confused or misled into believing that content originates from a trusted source when in fact it does not. The security element shows the user the source of the content and is displayed in such a manner that the source of the content is easily viewable. For example, according to one embodiment, the security element is shown within the title bar of a window. The security element may also be temporarily shown. Providing the user with more information about the site being accessed helps them to make an intelligent decision about their browsing experience. The security element includes at least part of a domain name that identifies the source of the content. The security element may also include the entire domain name. For example, the security element may overlay the screen.

Abstract: The subject disclosure pertains to systems and methods for providing an improved user interface for mobile devices. A user interface can obtain content including data and associated tasks from a set of software applications. Consequently, users can access content from multiple applications without navigating away from the user interface. The system architecture is extensible, providing for the addition of applications and user interfaces without requiring modification of the existing applications or user interfaces. Applications can register data suppliers capable of retrieving data from the underlying data store for the application and task executors capable of acting on the data. A user interface can generate a query requesting a class of data and specifying a context used to filter possible results. The system can determine the appropriate data suppliers, distribute queries and return the assembled results to the user interface.

Abstract: A determination is made as to when to display and hide obstructive user interface elements. Obstructive user interface elements are removed from the display when not needed by the user and displayed when needed by the user. When the obstructive interface elements are removed from the display, the user has more viewable area that is not obstructed. For example, in some browser applications, when the title bar, address bar and menu bar are removed, the user is provided with a view that shows much more of the web page. When the obstructive user interface elements are needed, they are temporarily displayed on the device. Once the task has been completed, the obstructive user elements are then hidden again automatically, which allows the user to continue viewing in full screen mode.

Abstract: A security element is displayed that provides information to a user to help ensure that they are not confused or misled into believing that content originates from a trusted source when in fact it does not. The security element shows the user the source of the content and is displayed in such a manner that the source of the content is easily viewable. For example, according to one embodiment, the security element is shown within the title bar of a window. The security element may also be temporarily shown. Providing the user with more information about the site being accessed helps them to make an intelligent decision about their browsing experience. The security element includes at least part of a domain name that identifies the source of the content. The security element may also include the entire domain name. For example, the security element may overlay the screen.

Abstract: A main processing thread in a handheld computer processes user input messages and e-mail messages. A second thread is created from the main thread. The main thread has a user input queue for user input messages, and the second thread having a notification queue for e-mail notification messages. The user input messages in the user input queue are processed until the user input queue is empty. A notification send ON signal is sent from the main thread to the second thread after the user input queue is empty. The notification send ON signal indicates when the main thread is available to process e-mail notification messages. The main thread retrieves and processes e-mail notification messages sent from the second thread after the notification send ON signal has been sent from the main thread until the user input queue is no longer empty. When the user input queue is no longer empty, a notification send OFF signal is sent from the main thread, and user input messages are processed by the main thread.