Patent Application
20230031103
The present disclosure relates generally to computer user interfaces, and more specifically to techniques for managing browser tabs.
Modern electronic devices and communications systems allow users to be more connected than ever to people, information, entertainment, and shopping. A substantial amount of information is available to users utilizing the Internet, and this information is typically accessed through a web browser such as the Safari® web browser of Apple Inc. of Cupertino, California. A browser typically can display multiple webpages in a single window, where each webpage is associated with a single tab. Users may have many webpages active at once. Those webpages each may be associated with a tab in a single browser window, or those webpages may be open in different tabs in different browser windows.
Often, users wish to interact with particular websites on a frequent basis. Moreover, users often consume content from a webpage over multiple sessions, after having interacted with the webpage (e.g., scrolling the website or navigating to a subdomain). In such instances, a user may be required, in a subsequent session, to repeat one or more the same interactions in order to continue their consumption of content. Additionally, it may become difficult for a user to keep track of which active webpages are open. Further, a user may have begun to enter data in one webpage, become distracted by content in a different webpage, and then forgotten he or she had already started to enter data in the first webpage. As a result, the user may open the web page in a different tab and start from the beginning, not realizing that an active webpage in a different tab already includes information entered by the user. Such repetitive entry causes additional work and consumes more of the user's time.
Some techniques for providing and managing browser tabs using electronic devices, however, are generally cumbersome and inefficient. For example, existing techniques use a complex and time-consuming user interface, which may include multiple key presses or keystrokes. Existing techniques require more time than necessary, wasting user time and device energy. This latter consideration is particularly important in battery-operated devices. Existing techniques rely on the user's attention and memory, which can vary with time of day and stress, and which may be unreliable.
Accordingly, the present application provides for electronic devices with faster, more efficient methods and interfaces for providing and managing browser tabs. Such methods and interfaces optionally complement or replace other methods for providing and managing browser tabs. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges.
In some embodiments, a method for providing and managing browser tabs at an electronic device, while a webpage is open in a first tab in a browser application, includes: receiving one or more inputs corresponding to the webpage; and in response to the one or more inputs, changing a state of the webpage in the first tab; after changing the state of the webpage in the first tab, receiving a request to open the webpage in a second tab that is different from the first tab; and in response to the request to open the webpage in the second tab, determining whether the first tab is a docked tab and whether the webpage is associated with a docked tab: in accordance with a determination that the webpage is associated with a docked tab and that the first tab is a docked tab, presenting the webpage with the state of the webpage in the first tab; in accordance with a determination that the webpage is associated with a standard tab and that the first tab is not a docked tab, presenting the webpage in the second tab with a state different from the state of the webpage in the first tab.
In some embodiments, an electronic device includes a display; a memory; one or more processors coupled to the display and the memory; and a browser application stored in the memory and executable by the processor; the processor configured to: while a webpage is open in a first tab in a browser application: receive one or more inputs corresponding to the webpage; and in response to receipt of the one or more inputs, change a state of the webpage in the first tab; after the change of the state of the webpage in the first tab: receive a request to open the webpage in a second tab that is different from the first tab; and in response to receipt of the request to open the webpage in the second tab, determine whether the first tab is a docked tab and whether the webpage is associated with a docked tab: in accordance with a determination that the webpage is associated with a docked tab and that the first tab is a docked tab, present the webpage with the state of the webpage in the first tab; in accordance with a determination that the webpage is associated with a standard tab and that the first tab is not a docked tab, present the webpage in the second tab with a state different from the state of the webpage in the first tab.
In some embodiments, a non-transitory computer-readable storage medium stores one or more programs, the one or more programs comprising instructions, which when executed by an electronic device, cause the electronic device to: while a webpage is open in a first tab in a browser application: receive one or more inputs corresponding to the webpage; and in response to receipt of the one or more inputs, change a state of the webpage in the first tab; after the change of the state of the webpage in the first tab: receive a request to open the webpage in a second tab that is different from the first tab; and in response to receipt of the request to open the webpage in the second tab, determine whether the first tab is a docked tab and whether the webpage is associated with a docked tab: in accordance with a determination that the webpage is associated with a docked tab and that the first tab is a docked tab, present the webpage with the state of the webpage in the first tab; in accordance with a determination that the webpage is associated with a standard tab and that the first tab is not a docked tab, present the webpage in the second tab with a state different from the state of the webpage in the first tab.
In some embodiments, a transitory computer-readable medium stores one or more programs, the one or more programs comprising instructions, which when executed by an electronic device, cause the electronic device to: while a webpage is open in a first tab in a browser application: receive one or more inputs corresponding to the webpage; and in response to receipt of the one or more inputs, change a state of the webpage in the first tab; after the change of the state of the webpage in the first tab: receive a request to open the webpage in a second tab that is different from the first tab; and in response to receipt of the request to open the webpage in the second tab, determine whether the first tab is a docked tab and whether the webpage is associated with a docked tab: in accordance with a determination that the webpage is associated with a docked tab and that the first tab is a docked tab, present the webpage with the state of the webpage in the first tab; in accordance with a determination that the webpage is associated with a standard tab and that the first tab is not a docked tab, present the webpage in the second tab with a state different from the state of the webpage in the first tab.
In some embodiments, a system utilizes an electronic device with a display, the system comprising: while a webpage is open in a first tab in a browser application: means for receiving one or more inputs corresponding to the webpage; and means, in response to the one or more inputs, for changing a state of the webpage in the first tab; after changing the state of the webpage in the first tab: means for receiving a request to open the webpage in a second tab that is different from the first tab; and means, in response to the request to open the webpage in the second tab, for determining whether the first tab is a docked tab and whether the webpage is associated with a docked tab: means, in accordance with a determination that the webpage is associated with a docked tab and that the first tab is a docked tab, for presenting the webpage with the state of the webpage in the first tab; means, in accordance with a determination that the webpage is associated with a standard tab and that the first tab is not a docked tab, for presenting the webpage in the second tab with a state different from the state of the webpage in the first tab.
In some embodiments, an electronic device includes: a processing unit that includes a determining unit, a display enabling unit, and a receiving unit, the processing unit configured to: while a webpage is open in a first tab in a browser application: receive, using the receiving unit, one or more inputs corresponding to the webpage; and in response to the one or more inputs, change a state of the webpage in the first tab; after the change to the state of the webpage in the first tab: receive, using the receiving unit, a request to open the webpage in a second tab that is different from the first tab; and in response to the request to open the webpage in the second tab, determine, using the determining unit, whether the first tab is a docked tab and whether the webpage is associated with a docked tab: in accordance with a determination that the webpage is associated with and that the first tab is a docked tab, present, using the display enabling unit, the webpage with the state of the webpage in the first tab; in accordance with a determination that the webpage is associated with a standard tab and that the first tab is not a docked tab, present, using the display enabling unit, the webpage in the second tab with a state different from the state of the webpage in the first tab.
Thus, devices are provided with faster, more efficient methods and interfaces for providing and managing docked browser tabs, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces complement or replace other methods for providing and managing browser tabs.
For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
The following description sets forth exemplary methods, parameters, and the like. It should be recognized, however, that such description is not intended as a limitation on the scope of the present disclosure but is instead provided as a description of exemplary embodiments.
As noted above, the present invention provides for electronic devices that provide efficient methods and interfaces for providing and managing browser tabs, such as to decrease reliance on user attention and memory. Such techniques can reduce the cognitive burden on a user who access event notifications, thereby enhancing productivity. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs.
Below,
Although the following description uses terms “first,” “second,” etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch could be termed a second touch, and, similarly, a second touch could be termed a first touch, without departing from the scope of the various described embodiments. The first touch and the second touch are both touches, but they are not the same touch.
The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a”, “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof
The term “if” may be construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” may be construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad).
In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick.
The device may support a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.
Attention is now directed toward embodiments of portable devices with touch-sensitive displays.
As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button).
As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.
It should be appreciated that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in
Memory 102 optionally can include one or more computer-readable storage mediums. The computer-readable storage mediums optionally can be tangible and non-transitory. Memory 102 can optionally include high-speed random access memory and optionally also can include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 122 optionally can control access to memory 102 by other components of device 100.
Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data. In some embodiments, peripherals interface 118, CPU 120, and memory controller 122 optionally can be implemented on a single chip, such as chip 104. In some other embodiments, they optionally can be implemented on separate chips.
RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data optionally can be retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212,
I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208,
A quick press of the push button optionally can disengage a lock of touch screen 112 or begin a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 206) optionally can turn power to device 100 on or off. The user optionally can be able to customize a functionality of one or more of the buttons. Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.
Touch-sensitive display 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch screen 112. Touch screen 112 displays visual output to the user. The visual output optionally can include graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output optionally can correspond to user-interface objects.
Touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 and convert the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages, or images) that are displayed on touch screen 112. In an exemplary embodiment, a point of contact between touch screen 112 and the user corresponds to a finger of the user.
Touch screen 112 optionally can use LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies optionally can be used in other embodiments. Touch screen 112 and display controller 156 optionally can detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, California.
A touch-sensitive display in some embodiments of touch screen 112 optionally can be analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.
A touch-sensitive display in some embodiments of touch screen 112 optionally can be as described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety.
Touch screen 112 optionally can have a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user optionally can make contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
In some embodiments, in addition to the touch screen, device 100 optionally can include a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad optionally can be a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.
Device 100 also includes power system 162 for powering the various components. Power system 162 optionally can include a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
Device 100 also optionally can include one or more optical sensors 164.
Device 100 optionally also includes one or more contact intensity sensors 165.
Device 100 also optionally can include one or more proximity sensors 166.
Device 100 optionally also includes one or more tactile output generators 167.
Device 100 optionally can also include one or more accelerometers 168.
In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments, memory 102 (
Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices. Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.
In some embodiments, contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter).
Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (liftoff) event.
Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including ,without limitation, text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations, and the like.
In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.
Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 167 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.
Text input module 134, which optionally can be a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).
GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing; to camera 143 as picture/video metadata; and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
Applications 136 optionally can include the following modules (or sets of instructions), or a subset or superset thereof:
Examples of other applications 136 that optionally can be stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, contacts module 137 optionally can be used to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference module 139, e-mail 140, or IM 141; and so forth.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, telephone module 138 optionally can be used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally can use any of a plurality of communications standards, protocols, and technologies.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, video conference module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally can include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data.
In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact/motion module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that optionally can be downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 optionally can be used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present, or otherwise play back videos (e.g., on touch screen 112 or on an external, connected display via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to-do lists, and the like in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 optionally can be used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data on stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the contents of which are hereby incorporated by reference in their entirety.
Each of the above-identified modules and applications corresponds to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules optionally can be combined or otherwise rearranged in various embodiments. For example, video player module optionally can be combined with music player module into a single module (e.g., video and music player module 152,
In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 optionally can be reduced.
The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.
Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.
In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.
Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.
In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).
In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.
Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views when touch-sensitive display 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.
Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected optionally can correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected optionally can be called the hit view, and the set of events that are recognized as proper inputs optionally can be determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.
Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.
Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver 182.
In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally can utilize or call data updater 176, object updater 177, or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.
A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which optionally can include sub-event delivery instructions).
Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information also optionally can include speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.
Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event (187) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display 112, and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.
In some embodiments, event definition 187 includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.
In some embodiments, the definition for a respective event (187) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.
When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.
In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers optionally can interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.
In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.
In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.
In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.
In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on touchpads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.
Device 100 optionally also can include one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 optionally can be used to navigate to any application 136 in a set of applications that optionally can be executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.
In some embodiments, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch screen 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.
Each of the above-identified elements in
Attention is now directed towards embodiments of user interfaces that optionally can be implemented on, for example, portable multifunction device 100.
It should be noted that the icon labels illustrated in
Although some of the examples which follow will be given with reference to inputs on touch screen display 112 (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in
Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse-based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.
Techniques for detecting and processing touch intensity optionally can be found, for example, in related applications: International Patent Application Serial No. PCT/US2013/040061, titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, and International Patent Application Serial No. PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed Nov. 11, 2013, each of which is hereby incorporated by reference in their entirety.
In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device 500 with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms optionally can permit device 500 to be worn by a user.
Input mechanism 508 optionally can be a microphone, in some examples. Personal electronic device 500 can include various sensors, such as GPS sensor 532, accelerometer 534, directional sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and/or a combination thereof, all of which can be operatively connected to I/O section 514.
Memory 518 of personal electronic device 500 can be a non-transitory computer-readable storage medium, for storing computer-executable instructions, which, when executed by one or more computer processors 516, for example, can cause the computer processors to perform the techniques described above, including process 700 (
As used here, the term “affordance” refers to a user-interactive graphical user interface object that optionally can be displayed on the display screen of devices 100, 300, and/or 500 (
As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in
As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user. For example, the set of one or more intensity thresholds optionally can include a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation) rather than being used to determine whether to perform a first operation or a second operation.
In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface optionally can receive a continuous swipe contact transitioning from a start location and reaching an end location, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location optionally can be based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm optionally can be applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity.
The intensity of a contact on the touch-sensitive surface optionally can be characterized relative to one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures.
An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments, the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero.
In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., an “up stroke” of the respective press input).
In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances).
For ease of explanation, the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold.
As used herein, an “installed application” refers to a software application that has been downloaded onto an electronic device (e.g., devices 100, 300, and/or 500) and is ready to be launched (e.g., become opened) on the device. In some embodiments, a downloaded application becomes an installed application by way of an installation program that extracts program portions from a downloaded package and integrates the extracted portions with the operating system of the computer system.
As used herein, the term “open application” or “executing application” refers to a software application with retained state information (e.g., as part of device/global internal state 157 and/or application internal state 192). An open or executing application optionally can be any one of the following types of applications:
As used herein, the term “closed application” refers to software applications without retained state information (e.g., state information for closed applications is not stored in a memory of the device). Accordingly, closing an application includes stopping and/or removing application processes for the application and removing state information for the application from the memory of the device. Generally, opening a second application while in a first application does not close the first application. When the second application is displayed and the first application ceases to be displayed, the first application becomes a background application.
Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that optionally can be implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.
Referring to
Browser interface 601 includes a first portion 602 and a second portion 604 distinct from the first portion 602. First portion 602 is configured to display content of webpages opened in tabs of the browser interface. In some embodiments, the first portion 602 includes a body of the webpages without one or more control affordances. Second portion 604 includes one or more control affordances and is sometimes referred to as the “chrome” of the browser. For example, second portion 604 includes one or more control affordances 608, address bar 606, and/or a tab bar 618.
In a non-limiting example, the one or more control affordances 608 include one or more of an exit affordance, a previous webpage affordance, and/or a forward webpage affordance. The address bar 606 includes a current uniform resource locator (URL) and accepts an entered URL that navigates the user to a chosen webpage in browser interface 601. That is, the address bar 606 includes a web address entry region of the browser interface 601. In some embodiments the web address entry region is also configured to receive search queries and display bookmarks. Further, the tab bar 618 includes a first docked tab 610, a second docked tab 611, a first standard tab 612, and a second standard tab 614. In
In some embodiments (e.g., as in
As shown in
As shown, the state of webpage 603 is based on the mark-up language associated with the webpage and the settings of browser interface 601. That is, webpage 603 is presented in a “default” state, as seen when a webpage is initially opened by browser interface 601. For example, in the default state, the progress bar of video section 624 is in a starting position and the video remains unplayed. Similarly, search field 628 is empty.
While webpage 603 (here, Webpage 1) is open in foreground tab 612 of browser interface 601, electronic device 600 receives one or more inputs (e.g., mouse, keyboard, or touch inputs such as mouse input 622 on zoom controller 622 in
After changing the state of the webpage in tab 612 (e.g., a first tab) (and optionally, after ceasing to display the first tab or while the webpage in the first tab maintains the changed state), electronic device 600 receives a request (e.g., mouse, keyboard, or touch inputs) to open the webpage in a second tab that is different from the first tab. As seen in
Turning to
While webpage 603A is open in foreground docked tab 610A of browser interface 601, electronic device 600 receives one or more inputs (e.g., mouse, keyboard, or touch inputs such as mouse input 622 on zoom controller 622A in
After changing the state of the webpage in tab 610A (e.g., a first tab) (and optionally, after ceasing to display the first tab or while the webpage in the first tab maintains the changed state), electronic device 600 receives a request (e.g., mouse, keyboard, or touch inputs) to open the webpage in a second tab that is different from the first tab. As seen in
In some embodiments, the state of the webpage (e.g., 603) is selected from one or more of page position state, zoom level state, entered text state, sub-domain state (e.g., navigating from www.apple.com to www.apple.com/iphone), and media playback state. In some embodiments, the state of the webpage is any state that can be controlled using a web browser.
Turning to
Turning to
In some embodiments, when a docked tab is displayed, the user may attempt to open in a second tab, such as a standard tab, a webpage that is in the same domain as (or in the subdomain of) a domain associated with a docked tab. If so, the browser application will open the docked tab and optionally close the second tab, such that two tabs will not be open in the browser at once where both are in the same domain as (or in the subdomain of) a domain associated with a docked tab. In some embodiments, the first tab is in a first window of the browser application, and the second tab is in the same browser window as the first tab.
In some embodiments, a standard tab optionally can be converted to a docked tab. Turning to
In some embodiments, a standard tab optionally can be converted to a docked tab using a contextual menu. Turning to
In some embodiments, a standard tab optionally can be converted to a docked tab via a menu of a browser interface. For example, a “bookmark” menu of a browser interface optionally can include an option to convert the foreground tab to a docked tab, if it is a standard tab.
In some embodiments, a second tab (e.g., tab 614 in
In some embodiments, where a webpage is associated with a docked tab (e.g., webpage 603 displayed in tab 610 in FIG.6AA), a visual indication is provided that the webpage 603 is associated with a docked tab. For example, as seen in
In some embodiments, a characteristic of the visual indication that the webpage 603 is associated with a docked tab is based on at least one characteristic of the content associated with the webpage 603. In some embodiments, the at least one characteristic of the content associated with the webpage 603 is included in the mark-up language associated with the webpage. Such at least one characteristic of the content associated with the webpage 603 is located in structured data in mark-up language, allowing the browser interface 601 to find and utilize that characteristic of the content associated with the webpage 603 to display a visual indication that the webpage 603 is associated with a docked tab. Color is one example of a characteristic of the content associated with the webpage 603. Exemplary tab bars 618 from a browser interface 601, such as shown in
In some embodiments, the browser interface displays, for the docked tab or tabs, an icon (e.g., a monogram). One function of the icon (e.g., a monogram) is to provide a visual indication that a webpage 603 is associated with a docked tab. A low-resolution bitmap icon is optionally associated with the webpage 603, and is received by the browser interface 601 along with the webpage 603. As set forth above, the browser interface 601 can determine a color characteristic for the webpage 603. Further, the browser interface 601 determines text associated with the webpage, which is selected from a plurality of sources based on one or more rules for selecting text. For example, for the website www.apple.com, the browser application 601 selects the first letter of the domain, “A”. In some embodiments, where a domain begins with “the” or similar words, “the” or such similar words are not considered, and the first letter thereafter is used. For example, for a website having a URL that begins www.thev . . . , after throwing out the first letters “the,” the browser application 601 selects the letter V. In other examples, text associated with the webpage is a resource identifier of the webpage, a title of the webpage, a title of the webpage with one or more types of common words removed, and/or text from another metadata field associated with the webpage, such as a mobile webclip name. Heuristic rules are utilized in some embodiments to select the text associated with the webpage. Based on this information, the browser application generates a monogram. In some embodiments, the monogram is a vector graphic, which is higher resolution and quality than a bitmap icon. A high-resolution monogram is desirable in higher-resolution displays. As computer monitors, laptop screens, tablet displays and smartphone displays increase in quality, such as those utilizing the Retina® display of Apple Inc. of Cupertino, California, higher-resolution monograms are needed so that existing low-resolution bitmap icons do not ruin the high-resolution look of the display with low-quality graphics. In some embodiments, the browser application 601 generates a monogram using the previously-determined text associated with the webpage 603, and the color characteristic of the webpage 603. As one example, the monogram includes the first letter of text, against a background having the color characteristic of the webpage 603. As another example, a shape is generated, with the first letter of text inside the shape, and with the shape filled with the color of the color characteristic. As another example, where a low-resolution bitmap icon is associated with the webpage 603, that bitmap icon is redrawn as a vector graphic at higher resolution, and that vector graphic is used along with a monogram generated as described above, or instead of the monogram generated as described above. The redrawn vector graphic optionally includes the color characteristic and/or the first letter of the webpage, as described above. As another example, the browser application 601 checks a remote server to determine if a vector graphic exists for that website, and if so uses that vector graphic as the monogram. Referring to
As described above with reference to
As displayed in
In some embodiments, a user navigates from the third tab 614 to a third webpage associated with a docked tab. For example, the electronic device detects that the user clicks on a button 636 displayed on the webpage 603 in order to navigate to a third webpage. Electronic device 600 determines that the webpage 603 to which the button 636 points is associated with a docked tab. In response to receiving the request to navigate within the third tab to a third webpage associated with a docked tab, the browser interface 601 displays the webpage 603 in the fourth tab 616, where the fourth tab 616 is a docked tab. As described above with regard to
In some embodiments, the browser interface 601receives a request to navigate within a third tab 614 to a third webpage associated with a docked tab. Starting with
Referring to
In some embodiments, the electronic device optionally can detect input corresponding to a user dragging a docked tab rightward. The electronic device detects that a user has clicked and dragged, such as with the cursor 615, the docked tab to the right within the browser interface window 601, such as to the right side of the tab bar 618, or rightward past a designated boundary in the browser interface 601. Inversely to the method described above, the docked tab then optionally can be converted to a standard tab, which is displayed in the tab bar 618 at a location to the right of the docked tabs, or if no docked tabs are present, at a location to the right of the position the docked tabs would occupy. The standard tabs optionally can be located elsewhere in the browser interface 601 if desired.
Correspondingly, the browser interface 601 receives the request to select the fourth tab 616 and move the fourth tab 616 to a conversion area 638 of the browser interface 601. In response to receiving the request to select the fourth tab 616and move the fourth tab 616to the left side of the tab bar 618, the fourth tab 616is converted to a docked tab, and the webpage 603 is associated with the docked tab. The visual appearance of the fourth tab 616 has been altered to be consistent with the appearance of a docked tab. For example, as shown in
In some embodiments, as described above with reference to
In some embodiments, referring back to exemplary
In some embodiments, as described above with reference to
In some embodiments, the electronic device optionally can use a standard tab (e.g., an available blank standard tab (e.g., one without an open webpage) or a standard tab that is auto-generated when a browser interface is first opened) for displaying webpages on a different domain that are requested from requests (e.g., selection of hyperlinks) made from a docked tab. Turning to
As described below, method 700 provides an intuitive way for providing and managing docked browser tabs. The method reduces the cognitive burden on a user for providing and managing browser tabs, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user manage and utilize docked browser tabs faster and more efficiently conserves power and increases the time between battery charges.
The electronic device (e.g., 100, 300, 500) includes a display (e.g., 112, 340, 504). A browser application is installed on the electronic device (e.g., 100, 300, 500). A browser application is software with a graphical user interface for displaying files, used to navigate the World Wide Web. An exemplary web browser is the Safari® web browser of Apple Corporation, Cupertino, California. In some embodiments, the browser application (e.g., the browser module 147 shown in
Referring also to
In response to receiving one or more inputs, the electronic device (e.g., 100, 300, 500) changes (704) the state of the webpage (603) that is displayed in the first tab (610), as seen in
After changing the state of the webpage (e.g., 603) displayed in the first tab (e.g., 610), the browser interface (e.g., 601) receives (706) a user request to open the webpage (e.g., 603) in a second tab different from the first tab (e.g., 610). The request to open the webpage (e.g., 603) optionally is made in the same browser interface window, or in a second browser application window (e.g., 601-1;
The electronic device (e.g., 100, 300, 500) determines (708) whether the first tab (e.g., 610) is a docked tab, and whether the webpage (603) is associated with a docked tab. A webpage (603) is associated with a docked tab when the webpage (e.g., 603) is a domain associated with the docked tab, or is a subdomain of that domain. As used in this document, the term “docked tab” refers to a tab in a browser interface (e.g., 601) that provides for the storage and/or transmission of information regarding the state of the webpage (e.g., 603), in the manner set forth herein. In this document, the term “persistent tab” or “pinned tab” are also used interchangeably to refer to a docked tab. In some embodiments, each docked tab exists in every open window of the browser interface (e.g., 601). Accordingly, when the browser interface (e.g., 601) is open, each docked tab is shown. Optionally, a docked tab cannot be closed in the same manner as a standard tab. For example, there is not an affordance on a docked tab associated with closing the docked tab. Instead, the browser interface (e.g., 601) optionally requires the user to navigate to a menu or perform some other action in order to close a docked tab.
In accordance with a determination that the webpage (e.g., 603) is associated with a standard tab and that the first tab (e.g., 610) is not a docked tab, the browser interface (e.g., 601) presents (712) the webpage (e.g.,
In accordance with a determination that the webpage (e.g., 603A) is associated with a docked tab and that the first tab (610A) is a docked tab, a browser interface presents (710) the webpage (e.g., 603A) with the state of the webpage (e.g., 603A) in the first tab (e.g., 610A). As one example, where the first tab (e.g., 610) is presented in the browser interface (e.g., 601) and the user requests to open the webpage in a second tab (e.g., 610A-1;
In some embodiments (e.g.,
In some embodiments (e.g.,
In some embodiments, the browser application interfaces (e.g., 601 or 601-1) need not be displayed on the same electronic device, and are located on different electronic devices from one another. In some embodiments, the second tab (e.g., 612) is presented with a different visual appearance than the first tab (e.g., 610). That is, where the second tab (e.g., 612) is located in a background window relate to the first tab (e.g., 610), the second tab (e.g., 612) is “grayed out”, presented with a lessened brightness or contrast, presented with a decreased color saturation, decreased in size, or otherwise presented differently than the first tab (e.g., 610).
In some embodiments, referring to exemplary
In some embodiments, a docked tab is larger than a standard tab, is presented with a heightened brightness or contrast, presented with an increased color saturation, presented with a different shape, and/or is presented in any other suitable manner. In some embodiments, a characteristic of the visual indication is determined (736) based on at least one characteristic of content associated with the webpage (e.g., 603). Optionally such at least one characteristic is determined based on structured data, such as HTML fields, present in the webpage (e.g., 603). For example, the characteristic is a color associated with the webpage (e.g., 603), and that color is used to generate a color of the docked tab and/or a color of an icon displayed in the docked tab.
In some embodiments, after a determination that the webpage (e.g., 603) is associated with a docked tab and that the first tab (e.g., 610) is a docked tab, the electronic device (e.g., 100, 300, 500) associates (730) the state of the webpage (e.g., 603) with a user identifier. The user identifier is a login ID associated with a mobile electronic device, an email address of the user, or any other identifying data. The electronic device (e.g., 100, 300, 500) then transmits to a second electronic device, a cloud server, or other machine the user identifier and the state of the webpage (e.g., 603) associated with the user identifier. In this way, transfer of the state of a webpage across different electronic devices is facilitated.
In some embodiments, after a determination that the webpage (e.g., 603) is associated with a docked tab and that the first tab (e.g., 610) is a docked tab, the browser interface (601) receives (742) a request to open a second webpage in a third tab. Referring to exemplary
In some embodiments, after a determination that the webpage (e.g., 603) is associated with a docked tab and that the first tab (e.g., 610) and/or second tab (e.g., 612) is a docked tab, the user selects (754) the first tab (e.g., 610) or the second tab (612). Referring to
In some embodiments, after a determination that the webpage (e.g., 603) is associated with a docked tab and that the first tab (e.g., 610) and/or second tab (e.g., 612) is a docked tab, the browser interface (e.g., 601) receives (764) the selection of a link (e.g., 646;
In contrast, selection of a link that navigates to a domain (e.g., a subdomain) associated with the webpage (e.g., 603) navigates to that domain, and presents a webpage associated with that domain in the same tab in which the link was displayed.
Referring to
Referring to
In accordance with some embodiments,
As shown in
The processing unit (806) includes a determining unit (812) and a receiving unit (810), and is coupled to a display enabling unit (802). The processing unit (806) is configured to, while a webpage is open in a first tab in a browser application, receive (e.g., with the receiving unit 810) one or more inputs corresponding to the webpage; and in response to the one or more inputs, change (e.g., with the processing unit 806) a state of the webpage in the first tab; after the change to the state of the webpage in the first tab: receive (e.g., with the receiving unit 810) a request to open the webpage in a second tab that is different from the first tab; and in response to the request to open the webpage in the second tab, determine (e.g., with the determining unit 812) whether the first tab is a docked tab and whether the webpage is associated with a docked tab: in accordance with a determination that the webpage is associated with and that the first tab is a docked tab, present (e.g., with the display enabling unit 802) the webpage with the state of the webpage in the first tab; in accordance with a determination that the webpage is associated with a standard tab and that the first tab is not a docked tab, present (e.g., with the display enabling unit 802) the webpage in the second tab with a state different from the state of the webpage in the first tab. The state of the webpage is selected from the group consisting of one or more of page position state, zoom level state, entered text state, sub-domain state, and media playback state.
The processing unit (806) is further configured to, further in accordance with the determination that the webpage is associated with a docked tab and that the first tab is a docked tab, and where the processing unit further comprising a storing unit, receive (e.g., with the receiving unit 810) a request to close the webpage in the first tab or the second tab; in response to the request to close the webpage in the first tab or the second tab, determine (e.g., with the determining unit 812) whether the request to close the webpage in the first tab or the second tab is concurrent with a termination of the browser application; in accordance with a determination that the request to close the webpage in the first tab or the second tab is not concurrent with a termination of the browser application, store(e.g., with the storing unit 818) the state information associated with the webpage; in accordance with a determination that the request to close the webpage in the first tab or the second tab is concurrent with a termination of the browser application, forgo storing (e.g., with the storing unit 818) the state information associated with the webpage.
The processing unit (806) is further configured to after storage of the state information associated with the webpage, receive (e.g., with the receiving unit 810) a request to open the webpage in a third tab; and in response to the request to open the webpage in a third tab, present (e.g., with the display enabling unit 802), the webpage in the third tab with the stored state information associated with the webpage. The first tab is in a first window of the browser application, and the second tab is in the same browser window as the first tab. In other embodiments, the first tab is in a first window of the browser application, and where the second tab is in a different browser window from the first tab.
The processing unit (806) is further configured to, where the webpage is associated with a docked tab, and where the processing unit further comprises a detecting unit, detect (e.g., with the detecting unit 814) a change of the state of the webpage displayed in the first tab; and in response to detection of a change of the state of the webpage displayed in the first tab, update (e.g., with the processing unit 806) the state of the webpage displayed in the second tab to reflect the change of the state of the webpage displayed in the first tab.
The display enabling unit (802) is further configured to present the second tab with a different visual appearance from the first tab. Where the webpage is associated with a docked tab, the display enabling unit (802) is further configured to provide a visual indication that the webpage is associated with the docked tab. The determining unit is further configured to determine (e.g., with the determining unit 812) a characteristic of the visual indication based on at least one characteristic of content associated with the webpage.
The processing unit (806) is further configured to, where the webpage is associated with a docked tab, where the processing unit is further configured to associate (e.g., with the processing unit 806) the state of the webpage with a user identifier; and transmit (e.g., with the transmitting unit), to a second electronic device, the user identifier and the state of the webpage associated with the user identifier.
The processing unit (806) is further configured to, where the webpage is associated with a docked tab, receive (e.g., with the receiving unit 810) a request to open a second webpage in a third tab; in response to the request to open the second webpage in a third tab, in accordance with a determination that the second webpage is associated with a standard tab, present (e.g., with the display enabling unit 802) the webpage in the third tab, where the third tab is a standard tab; and display (e.g., with the display enabling unit 802), in the browser application, the docked and standard tabs in a predefined order relative to one another.
The processing unit (806) is further configured to receive (e.g., with the receiving unit 810) a request to navigate within the third tab to a third webpage associated with a docked tab; in response to the request to navigate within the third tab to a third webpage associated with a docked tab, open a fourth tab and display (e.g., with the display enabling unit 802) the webpage in the fourth tab, where the fourth tab is a docked tab.
The processing unit (806) is further configured to, further in response to the request to navigate within the third tab to a third webpage associated with a docked tab, close the third tab and open the fourth tab.
The processing unit (806) is further configured to, where the webpage is associated with a standard tab, receive (e.g., with the receiving unit 810), a request to select the second tab and move the second tab to a defined region of the browser; in response to the request to select the second tab and move the second tab to a defined region of the browser: convert (e.g., with the processing unit 806) the second tab into a docked tab; and associate (e.g., with the processing unit 806) the webpage with the docked tab.
The electronic device of any of claims 24-38, where the webpage is associated with a docked tab, where the processing unit is further configured to: receive (e.g., with the receiving unit 810) a user selection of the first tab or the second tab; receive (e.g., with the receiving unit 810) a user action of dragging the selected tab out of the browser, where the state of the webpage associated with the selected tab includes media playback information, and where media playback occurs during the dragging; and receive (e.g., with the receiving unit 810) a user action of releasing the selected tab at a defined location on a desktop; retaining (e.g., with the storing unit 818) the media playback information associated with the selected tab; and continuing (e.g., with the processing unit 806) media playback after the releasing.
The processing unit (806) is further configured to, where the webpage is associated with a docked tab, receive (e.g., with the receiving unit 810) on the webpage displayed in one of the first tab and the second tab, a selection of a link that navigates away from a domain associated with the webpage; in response to selection of the link that navigates away from the domain associated with the webpage, open (e.g., with the processing unit 806) a third tab and displaying in the third tab a second webpage associated with the link; present (e.g., with the display enabling unit 802) in association with the browser, a back button; receive (e.g., with the receiving unit 810) a selection of the back button; and in response to the selection of the back button: close the third tab, and present (e.g., with the display enabling unit 802) the webpage associated with the first and second tabs.
In accordance with some embodiments,
As shown in FIG.9, an electronic device 900 includes a display enabling unit 902 configured to display a graphic user interface, optionally, a touch-sensitive surface unit 904 configured to receive contacts, and a processing unit 906 coupled to the display unit 902 and, optionally, the touch-sensitive surface unit 904. In some embodiments, the processing unit 906 includes a receiving unit 910, a determining unit 912, an identifying unit 914,and a generating unit 916.
The processing unit (906) includes a receiving unit (910), a determining unit (912), an identifying unit (914), and a generating unit (916), and is coupled to a display enabling unit (902). The processing unit (906) is configured to, while displaying (e.g., using the display enabling unit 902), a web browser, receiving (e.g., using the receiving unit 910) a request to display an icon representation of a webpage; in response to receiving the request to display the icon representation of the webpage, determining (e.g., using the determining unit 912), whether the webpage provides access to an image that meets predefined quality standards: in accordance with a determination that the webpage provides access to an image that meets predefined quality standards for use as an icon, displaying (e.g., using the display enabling unit 902) the high-quality image as an icon associated with the webpage at a respective location in the web browser; and in accordance with a determination that the webpage does not provide access to an image that meets the predefined quality standards: identify (e.g., using the identifying unit 914) other content associated with the webpage; generate (e.g., using the generating unit 916) a generated icon based on the content associated with the webpage; and display (e.g., using the display enabling unit 902) the generated icon at a respective location in the web browser.
In some embodiments, the generating unit (916) optionally can be further configured to: identify (e.g., using the identifying unit 914) text associated with the webpage; identify (e.g., using the identifying unit 914) a color associated with the webpage; and generate (e.g., using the generating unit 916) the generated icon that uses a predefined portion of the text associated with the webpage and incorporates the color associated with the webpage.
In some embodiments, the generated icon includes the first letter of the text associated with the webpage overlaid on a background that is the color associated with the webpage.
In some embodiments, the text associated with the webpage is selected from a plurality of sources based on one or more rules for selecting text.
In some embodiments, the text associated with the webpage is selected from one or more of the following: a resource identifier of the webpage; a title of the webpage; text retrieved from the webpage; a title of the webpage with one or more types of common words removed; and text from another metadata field associated with the webpage.
In some embodiments, the color associated with the webpage is generated (e.g., using the generating unit 916) based on one or more of: a predominant color of an icon associated with the webpage that does not meet the predefined quality standard; and a predominant color of the webpage.
In some embodiments, the webpage is associated with a low-quality icon that does not meet the predefined quality standards, and the generated icon is displayed (e.g., using the display enabling unit 902) for the webpage instead of displaying (e.g., using the display enabling unit 902) the low-quality icon.
In some embodiments, the low-quality icon is a bitmap icon.
In some embodiments, the high-quality image is a vector graphic.
The operations described above with reference to
The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the techniques and their practical applications. Others skilled in the art are thereby enabled to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated.
Although the disclosure and examples have been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of the disclosure and examples as defined by the claims.
As described above, one aspect of the present technology is the gathering and use of data available from various sources to improve the delivery to users of invitational content or any other content that may be of interest to them. The present disclosure contemplates that in some instances, this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, home addresses, or any other identifying information.
The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. For example, the personal information data can be used to deliver targeted content that is of greater interest to the user. Accordingly, use of such personal information data enables calculated control of the delivered content. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure.
The present disclosure further contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure. For example, personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection should occur only after receiving the informed consent of the users. Additionally, such entities would take any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices.
Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, in the case of advertisement delivery services, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services. In another example, users can select not to provide location information for targeted content delivery services. In yet another example, users can select to not provide precise location information, but permit the transfer of location zone information.
Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data. For example, content can be selected and delivered to users by inferring preferences based on non-personal information data or a bare minimum amount of personal information, such as the content being requested by the device associated with a user, other non-personal information available to the content delivery services, or publically available information.
This application is a continuation of U.S. patent application Ser. No. 17/126,571, entitled “Browser with Docked Tabs,” filed Dec. 18, 2020, which is a continuation of U.S. patent application Ser. No. 16/363,945 (now U.S. Pat. No. 10,877,720), entitled “Browser with Docked Tabs,” filed Mar. 25, 2019, which is a continuation of U.S. patent application Ser. No. 14/864,759 (now U.S. Pat. No. 10,275,116), entitled “Browser with Docked Tabs,” filed Sep. 24, 2015, which claims priority to U.S. Provisional Patent Application No. 62/172,227, entitled “Browser with Docked Tabs,” filed Jun. 7, 2015, the contents of which are hereby incorporated by reference in their entirety for all purposes.
| Number | Date | Country | |
|---|---|---|---|
| 62172227 | Jun 2015 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17126571 | Dec 2020 | US |
| Child | 17862097 | US | |
| Parent | 16363945 | Mar 2019 | US |
| Child | 17126571 | US | |
| Parent | 14864759 | Sep 2015 | US |
| Child | 16363945 | US |
