Patent Grant
9529779
The present invention is in the field of systems, devices, methods, and computer program products for the detection and repositioning of pop-up dialogs.
Many mobile devices, such as smart phones and tablet computers, have the capability of accessing and displaying files, applications, and/or web pages. Due to the portable sizes of such mobile devices, display screens often display only a portion of the web page. In order to navigate or zoom in or out of a web page, a user can enter input, for example, via arrow keys, scroll bars, or touch screen commands. Display screens can also be adjusted by tilting or rotating the mobile devices.
An embodiment of the invention provides a method where a file is displayed on a display screen of a mobile device; and, a pop-up is identified outside of the visible area on the display screen of the mobile device. The identification of the pop-up includes detecting a document object model change in the file, the presence of one or more non-active elements in the file, and/or a change in luminance in an area outside of the visible area on the display screen. A controller moves the pop-up to the visible area on the display screen, or the visible area on the display screen is moved to the pop-up.
The present invention is described with reference to the accompanying drawings. In the drawings, like reference numbers indicate identical or functionally similar elements.
Exemplary, non-limiting, embodiments of the present invention are discussed in detail below. While specific configurations are discussed to provide a clear understanding, it should be understood that the disclosed configurations are provided for illustration purposes only. A person of ordinary skill in the art will recognize that other configurations may be used without departing from the spirit and scope of the invention.
An embodiment of the invention provides a method to detect when a web page pop-up (also referred to as a “pop-up dialog”, “pop-up window”, or “secondary window”) has been created outside of a user's visible area on a mobile device (e.g., smart phone, tablet computer). After detecting the creation of a non-visible pop-up, the mobile device can either intercept and redirect the pop-up to a visible area on the mobile device's display screen, or redirect the visible area on the display screen to the area of the web page that contains the pop-up. As used herein, the terms “visible area” and “viewable area” include the portion of the file, application, or web page that is displayed on the display screen of the mobile device.
Another embodiment of the invention provides a system that a pop-up dialog that has opened or is attempting to open. The system can also calculate the screen resolution, detect any special mode(s) that the device is in (e.g., zoom factor), detect the coordinates of the pop-up dialog, detect the coordinates that the pop-up dialog is trying to open to, detect whether the pop-up dialog is out of focus, redirect the pop-up dialog to the active viewable area, or move the active viewable area to the pop-up dialog. In at least one embodiment, an information dialog is presented to the user in the active viewable area, where the information dialog informs the user that a pop-up dialog was created elsewhere and gives the user an option to move the viewable area of the screen. In another embodiment, the system utilizes user preferences for pop-up placement and/or viewable area shifting. The system allows an application developer to focus on application logic without requiring device specific application windows placement logic inside the code. Moreover, the system reduces the development time and increases the usability for the consumer.
The creation of a non-visible pop-up dialog can be detected by detecting a document object model (DOM) change through a browser modification or plugin. In another embodiment, the creation of a non-visible pop-up dialog can be detected by detecting a model pop-up (by inference) and by probing for non-active elements (e.g., fields, scroll bars, buttons). The creation of a non-visible pop-up dialog can also be detected by detecting luminance changes within a display screen.
In order to detect pop-up dialogs, the system can obtain the current screen resolution, the current window placement user preferences, and perform either a cooperative process, an active process, or a luminance change process. The cooperative process sets a global variable for the HyperText Markup Language (HTML) page (e.g., via javascript), which indicates the current visible window placement and size/zoom factor. This process monitors for an HTML pop-up window event, determines whether the pop-up window script honors the global variable, and voluntarily sets the pop-up window location.
In at least one embodiment, the cooperative process detects multiple DOM values and state changes. The DOM values can include the height and width, the location of the visible area, and the scale, etc.; and, the state changes can include window resize and device rotation. The cooperative process can also detect the disabling of certain browser capabilities, which can include scrolling, resizing (unless the device rotates), the right mouse button, and/or the back button.
The active process can monitor for an HTML pop-up window event (e.g., by inference) by probing for non-active elements, such as fields, scroll bars, and buttons. In at least one embodiment, the luminance change process measures and records the luminance of pixels on the web page at load time (i.e., the instance where the web page is loaded onto the mobile device) across the viewport. As used herein, the term “viewport” includes the total area of a web page, file, or document. Thus, the viewport can be larger than the area that is visible on the display screen. In at least one embodiment, the luminance of all of the pixels in the viewport is measured and recorded.
The luminance of the pixels can be measured periodically, when a web page is refreshed, and/or when a new web page is loaded. If the luminance of a threshold number and/or percentage of pixels has changed (e.g., 2%), then the pixels(s) and/or area of the viewport where the change occurred can be recorded. The coordinates of the unchanged area(s) can also be recorded. If the pixels where the luminance change occurred are proximate one another or in a consecutive area (i.e., no intermediate areas of no luminance change), then the area can be tagged as a pop-up. Consecutive areas of luminance change are typically in the shape of a rectangle. If exact coordinates of the changed pixels cannot be identified, the system can estimate the coordinates of the changed pixels and/or identify the quadrant of luminance change.
To move the pop-up to the visible area, the current visible area of the file (e.g., x and y coordinates) is determined after a pop-up is detected. A script injection technique can be used or a function can be embedded into the rendering engine that replaces the pop-up location coordinates with a value that is in the relative center of the visible area. For example, the Firefox script monkey (available from Mozilla Corporation, Mountain View, Calif., USA) can be used as a script injection technique.
To move the visible area of the display screen to the pop-up, the pop-up's rendered location (e.g., x and y coordinates) and/or relative center location can be determined. The viewable area window is moved to overlap the pop-up. In other words, the center of the visible area of the display screen is modified to match the coordinates of the pop-up center.
In at least one embodiment of the invention, if the pop-up extends beyond the visible window, then the zoom factor of the display screen is adjusted to incorporate the entire pop-up. In another embodiment, the visible window is moved to display the pop-up window title bar and/or the first editable field and/or button.
For example, as illustrated in
In at least one embodiment, the pop-up is identified by detecting a document object model change in the file 122. The document object model change can be a browser modification and/or a browser plug-in. Additionally, the document object model change can be a change in the height of the file, the width of the file, the scale of the file, the screen resolution of the file, and/or the location of the visible area of the file. The document object model change can also be a change in browser capability (e.g., scrolling, resizing, key commands, and/or button commands).
The document object model change can be detected by setting a global variable for a HyperText Markup Language (HTML) page, wherein the global variable indicates the current visible window placement, a size factor, and a zoom factor. The web page can be compared to the global variable such that it can be determined that the document object model has changed if the web page does not match the global variable.
In another embodiment, the pop-up is identified by detecting the presence of one or more non-active elements in the file 124. The non-active elements can include fields, scroll bars, buttons, and/or icons in the file. In yet another embodiment, the pop-up is identified by detecting a change in luminance in the area outside of the visible area on the display screen 126.
More specifically, in at least one embodiment, the luminance of the pixels in the file is determined at the time the file is loaded onto the mobile device; and, the luminance of the pixels in the file is determined at a subsequent time. The subsequent time can be a predetermined time from the time that the file was loaded onto the mobile device. For example, the luminance of the pixels in the file can be measured every 60 seconds (or some other predetermined sampling period) after the file is downloaded and displayed on the mobile device. In another embodiment, the luminance of the pixels in the file can be measured every time that the file is refreshed. The luminance of the pixels in the file at the time the file was loaded onto the mobile device is compared with the luminance of pixels in the file at the subsequent time. The pixels in the file that are detected as having a luminance change are identified as a pop-up.
In at least one embodiment of the invention, a controller moves the pop-up to the visible area on the display screen 130A. For example, as illustrated in
The processor 520 detects a document object model change in the file, the presence of one or more non-active elements in the file (e.g., fields, scroll bars, and/or buttons), and/or a change in luminance in an area outside of the visible area on the display screen 510. More specifically, the processor 520 can detect a browser modification and/or a browser plug-in. Furthermore, the processor 520 can detect a change in the height of the file, the width of the file, the location of the visible area of the file, the scale of the file, the resolution of the file, and/or a change in a browser capability (e.g., scrolling, resizing, key commands, and/or button commands).
In at least one embodiment of the invention, the processor 520 sets a global variable for a HyperText Markup Language page and determines whether a webpage matches the global variable. The global variable can indicate the current visible window placement, the size factor, and/or the zoom factor.
In another embodiment, the processor 520 determines the luminance of the pixels in the file at the time that the file is loaded onto the mobile device, and determines the luminance of the pixels in the file at a subsequent time. The subsequent time can be a predetermined time from the time that the file was loaded onto the mobile device and/or a time when the file is refreshed. The processor 520 can compare the luminance of the pixels in the file at the subsequent time with the luminance of pixels in the file at the time the file was loaded onto the device. Thus, the processor 520 can identify pixels in the file having a luminance change as a pop-up.
The processor 520 is connected to a controller 530. As used herein, the term “controller” includes a hardware computing device that can move the pop-up to the visible area on the display screen 510 or move the visible area on the display screen 510 to the pop-up.
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.
Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
Aspects of the present invention are described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
Referring now to
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the root terms “include” and/or “have”, 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 at least one other feature, integer, step, operation, element, component, and/or groups thereof.
The corresponding structures, materials, acts, and equivalents of all means plus function elements in the claims below are intended to include any structure, or material, for performing the function in combination with other claimed elements as specifically claimed. The description of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention. The embodiment was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.
This patent application is a continuation application of U.S. patent application Ser. No. 13/725,694 filed on Dec. 21, 2012, which is hereby incorporated by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 20030112278 | Driskell | Jun 2003 | A1 |
| 20060271861 | Yolleck | Nov 2006 | A1 |
| 20080295025 | Gyure | Nov 2008 | A1 |
| 20110246880 | Horton | Oct 2011 | A1 |
| 20110311408 | Azimi | Dec 2011 | A1 |
| 20110314408 | Yolleck | Dec 2011 | A1 |
| 20120002149 | Katoh | Jan 2012 | A1 |
| 20120062622 | Koyama | Mar 2012 | A1 |
| 20130033618 | Kato | Feb 2013 | A1 |
| 20140240377 | Matsui | Aug 2014 | A1 |
| Entry |
|---|
| Vojnovic, S., et al., “Control Access Kernel Functionality Verification in Set-Tip Boxes via Popup Detection,” 2011, pp. 1-4. |
| Anonymous, “An Operable Pop-Up Preview Feature for Scroll Bar,” ip.com, May 10, 2011, pp. 1-6. |
| Anonymous, “Scroll Bar with Web Page Elements Indicators,” Oct. 14, 2010, pp. 1-8. |
| Number | Date | Country | |
|---|---|---|---|
| 20140181638 A1 | Jun 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13725694 | Dec 2012 | US |
| Child | 13788875 | US |
