WO2017181619A1

WO2017181619A1 - Page response method and device

Info

Publication number: WO2017181619A1
Application number: PCT/CN2016/101686
Authority: WO
Inventors: 曹刚
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-04-20
Filing date: 2016-10-10
Publication date: 2017-10-26
Also published as: CN107306308A; CN107306308B

Abstract

Provided are a page response method and device. The method comprises: during a page loading process, converting the registration of a touch screen event in a page into the registration of a button event; after page loading is completed, acquiring a first focusable element applied to the touch screen in a web page, and converting the first focusable element into a second focusable element applied to a button; and by means of the button event, triggering a response operation on the second focusable element. By means of the technical solution, the problem in the relevant art that, with regard to a mobile phone with a physical button, a button event of the physical button cannot be used to browser a touch screen based web page, and thus, although a user uses a low-end mobile phone with only a physical button, a response can still be made to most touch screen based web pages in the current market, thereby greatly improving the user experience.

Description

Page response method and device

Technical field

The present invention relates to the field of communications, and in particular to a page response method and apparatus.

Background technique

Although current touch screen-based mobile phones dominate the market, keyboard-based push buttons still occupy a very broad user market. However, one of the biggest problems with the current use of button presses is that it is very difficult to access the Internet in the normal browser of the phone. This is because when browsing websites on the keyboard, it often receives a variety of touch screen-based web pages (such as URLs containing " \touch", etc.). Since the attributes and events related to each element in these web pages are designed based on the current touch screen gesture triggering, according to the traditional browser button focus navigation method, these web pages cannot be browsed normally, for example, can not focus on a link to open a New web pages can't focus on the input box for input and submit operations, and so on.

In the browsers that support the keyboard machine in the early days, the following methods are mainly used to navigate through the webpage by keyboard operation: an A tag containing a URL link, an INPUT tag can be input, and a keyboard confirmation event (such as an OK key event) is registered. That is, the ENTER key event) other tags of the response transaction (such as DIV, BUTTON, etc.) are marked as focusable elements; when the user navigates through the webpage using the keyboard direction keys, the focus display is performed on the focusable elements in turn; When a button confirmation event occurs, the event transaction registered by the element can be responded to, such as opening a new link, submitting an input, and the like;

Ordinary browsers, such as button navigation methods, generally have no problem for early simple mobile web browsing. However, with the development of Hypertext Markup Language (HTML) 5, mobile web pages have become more and more complex and diverse. Especially a lot The webpage designed for the touch screen terminal completely abandons the previous design that supports keyboard navigation. First, the event registration of the event is no longer performed for each element that needs to respond to the event, but the touch event is managed through its own JS framework. The second is to no longer use the keyboard to confirm the event and only focus on touch events (such as TOUCHU START, TOUCHU END). In this way, it is impossible to capture the elements with the focus attribute using the conventional method, and even if the focus can not respond to the key events, the buttons cannot be navigated on the web pages of these touch screens.

In the related art, for a mobile phone with a physical key, it is not possible to use a button event of a physical key to browse a touch screen-based web page, and an effective solution has not been proposed.

Summary of the invention

The embodiment of the invention provides a page response method and device, so as to solve at least the problem of browsing a touch screen-based webpage by using a button event of a physical key for a mobile phone with a physical key in the related art.

According to an embodiment of the present invention, a page response method is provided, including:

During the page loading process, the registration of the touch screen event in the page is converted into the registration of the key event; after the page loading is completed, the first focusable element applied to the touch screen in the web page is acquired, and the first focusable element is converted a second focusable element applied to the button; triggering a response operation to the second focusable element by the button event.

Optionally, converting the registration of the touch screen event in the page to the registration of the key event includes:

When the page is monitored for event transaction registration, it is determined whether the event transaction registration is a registration of a touch screen event;

If so, the current event transaction registration process is stopped and the registration of the key event is loaded into the event transaction registration.

Optionally, determining whether the event transaction registration is a registration of a touch screen event comprises:

Determining whether the event transaction registration exists in a preset feature set;

If so, determining that the event transaction is registered as a registration of a touch screen event;

If not, it is determined that the event transaction is registered as a registration of a button event.

Optionally, before acquiring the first focusable element applied to the touch screen in the webpage, the method further includes:

Filtering the focusable elements located in a preset feature set from the focusable elements of all the labels of the webpage;

The filtered focusable element is used as the first focusable element of the touch screen.

Optionally, the feature set at least includes: a gesture event indicated by the touch screen event, an attribute feature of the first focusable element, wherein the attribute feature comprises: key information in response to the event.

Optionally, the feature set is updated when a predetermined time comes.

According to another embodiment of the present invention, a page response apparatus is further provided, including:

The conversion module is configured to convert the registration of the touch screen event in the page into the registration of the key event during the page loading process; the obtaining module is configured to obtain the first focusable element applied to the touch screen in the webpage after the page is loaded, And converting the first focusable element into a second focusable element applied to the button; the triggering module is configured to trigger a response operation to the second focusable element by the button event.

Optionally, the conversion module includes: a determining unit, configured to: when the page is monitored for event transaction registration, determine whether the event transaction registration is a registration of a touch screen event; and the stopping unit is set to register as an event transaction. When the registration of the touch screen event is stopped, the current event transaction registration process is stopped; the loading unit is set to load the registration of the key event into the event transaction registration.

Optionally, the determining unit is further configured to determine whether the event transaction registration exists in a preset feature set; if yes, determine that the event transaction is registered as a registration of a touch screen event; if not, determine the Event transactions are registered as registrations for key events.

Optionally, the device further includes: a screening module, configured to filter, from the focusable elements of all the labels of the webpage, the focusable elements located in the preset feature set; the determining module, Used to use the filtered focusable element as the first focusable element of the touch screen.

In the embodiment of the present invention, a computer storage medium is further provided, and the computer storage medium may store an execution instruction for executing the implementation of the page response method in the foregoing embodiment.

Through the embodiment of the present invention, the registration of the touch screen event in the page is converted into the registration of the key event; after the page loading is completed, the first focusable element applied to the touch screen in the webpage is acquired, and the first focusable element is converted For the second focusable element applied to the button, and then the technical solution for triggering the response operation to the second focusable element by the button event, solving the related art for the mobile phone with the physical key, the physical key cannot be used. The button event is used to browse the touch screen-based webpage, thereby realizing that even if the user uses a low-end mobile phone with only physical keys, it can still respond to most of the touch screen-based pages on the market, greatly improving the user. Experience.

DRAWINGS

The drawings described herein are intended to provide a further understanding of the invention, and are intended to be a part of the invention. In the drawing:

1 is a flowchart of a page response method according to an embodiment of the present invention;

2 is a block diagram showing the structure of a page response apparatus according to an embodiment of the present invention;

FIG. 3 is a structural block diagram of a conversion module 20 of a page response apparatus according to an embodiment of the present invention; FIG.

4 is a block diagram showing another structure of a page response apparatus according to an embodiment of the present invention;

Figure 5 is a block diagram showing the overall structure of a preferred embodiment 1 of the present invention;

6 is a flowchart of main processing of touch screen event registration conversion according to a preferred embodiment 1 of the present invention;

7 is a flow chart showing the main processing of capturing a focusable element when a direction key of a preferred embodiment 1 is navigated in a web page according to the preferred embodiment of the present invention.

detailed description

The invention will be described in detail below with reference to the drawings in conjunction with the embodiments. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.

It is to be understood that the terms "first", "second" and the like in the specification and claims of the present invention are used to distinguish similar objects, and are not necessarily used to describe a particular order or order.

A page response method is provided in this embodiment. FIG. 1 is a flowchart of a page response method according to an embodiment of the present invention. As shown in FIG. 1 , the process includes the following steps:

Step S102, in the page loading process, converting the registration of the touch screen event in the page into the registration of the button event;

Step S104, after the page loading is completed, acquiring a first focusable element applied to the touch screen in the webpage, and converting the first focusable element into a second focusable element applied to the button;

Step S106, triggering a response operation to the second focusable element by a button event.

Through the above steps, the registration of the touch screen event in the page is converted into the registration of the key event; after the page loading is completed, the first focusable element applied to the touch screen in the webpage is acquired, and the first focusable element is converted into the application. The second focusable element of the button, and then the technical solution for triggering the response operation of the second focusable element by the button event, solving the related art technology for the mobile phone with the physical key, the button event of the physical key cannot be used for the touch screen based webpage The problem of browsing enables the user to respond to most of the current touch screen-based pages on the market, even if the user uses a low-end mobile phone with only physical keys, which greatly improves the user experience.

There may be multiple implementations for step S102. In an optional example of the embodiment of the present invention, converting the registration of the touch screen event in the page to the registration of the key event may be implemented by: when the page is monitored for event transaction registration. Whether the event transaction registration is a registration of the touch screen event; if yes, the current event transaction registration process is stopped, and the registration of the key event is registered in the event transaction registration, that is, the registration of the touch screen event during the page loading process is uniformly converted into a button. The registration of the event enables subsequent key events to be responded to.

In the embodiment of the present invention, it is determined whether the event transaction registration is a registration of a touch screen event by:

It is necessary to set a feature set in advance, and all possible touch screen events are included in the feature set. Of course, the content of the feature set can be updated in real time as needed. If there is an event transaction registration that is of course being executed in a preset feature set, It indicates that the event transaction is registered as a touch screen event registration. If there is no feature set in this feature set, it is determined that the event transaction is registered as a registration of a button event. Of course, in actual circumstances, it is possible to register an event transaction that does not exist in the feature set, and may not be a button. The event, which is described herein, is also within the scope of the embodiments of the present invention.

Optionally, before acquiring the first focusable element applied to the touch screen in the webpage, the method further includes: filtering out the focusable elements located in the preset feature set from the focusable elements of all the labels of the webpage; The focusable element is the first focusable element of the touch screen, that is, the focusable element located in the feature set is also filtered out from the focusable elements of all the labels in the webpage according to the preset feature set.

The feature set includes at least: a gesture event indicated by the touch screen event, an attribute feature of the first focusable element, wherein the attribute feature includes: key information in response to the event.

Further, the feature set is updated when the predetermined time comes.

In summary, the browser supports button navigation in the webpage. The most important thing is to capture the focusable elements in the webpage. However, the previous method can only detect the regular focusable elements (such as the A-tag with the URL link, you can input INPUT). Labels, other tags with registered keyboard click event responses, etc., can't do anything about the focusable elements in a large number of touchscreen web pages. The technical solution of the embodiment of the present invention proposes a method based on an element touch event and a feature feature set to focus and process an element of a touch screen webpage according to the feature of the focusable element in the touch screen, so that the webpage can be normally used on various webpages. The use of button browsing breaks through the bottleneck problem that the traditional button machine cannot access the touch screen webpage, and has high technical value and commercial value.

The touch screen test webpage including the touch gesture event and the attribute feature mentioned in the embodiment of the present invention is accessed on the server by comparing the browser, and if the normal navigation operation can be performed on the webpage through the keyboard, that is, in the present invention Within the scope of protection.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, The optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods of various embodiments of the present invention.

Example 2

In the embodiment, a page response device is also provided, which is used to implement the above-mentioned embodiments and preferred embodiments, and details are not described herein. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

2 is a structural block diagram of a page response apparatus according to an embodiment of the present invention. As shown in FIG. 2, the apparatus includes:

The conversion module 20 is configured to convert the registration of the touch screen event in the page into the registration of the button event during the page loading process;

The obtaining module 22 is configured to: after the page loading is completed, acquire a first focusable element applied to the touch screen in the webpage, and convert the first focusable element into a second focusable element applied to the button;

The triggering module 24 is configured to trigger a response operation to the second focusable element by a button event.

Through the comprehensive function of each module described above, the registration of the touch screen event in the page is converted into the registration of the key event; after the page loading is completed, the first focusable element applied to the touch screen in the webpage is acquired, and the first focusable element is converted. For the second focusable element applied to the button, and then the technical solution for triggering the response operation to the second focusable element by the button event, solving the related art for the mobile phone with the physical key, the button event pair that cannot use the physical key is based on touch screen The problem of browsing the webpage further realizes that even if the user uses a low-end mobile phone with only physical keys, it can still respond to most of the touch screen-based pages currently on the market, greatly improving the user experience.

FIG. 3 is a structural block diagram of a conversion module 20 of a page response apparatus according to an embodiment of the present invention. As shown in FIG. 3, the conversion module 20 includes: a determining unit 200 configured to perform event transaction registration when a page is detected, and determine an event transaction. Whether the registration is a registration of a touch screen event; the stopping unit 202 is configured to stop the current event transaction registration process when the event transaction is registered as a registration of the touch screen event; the loading unit 204 is configured to register the registration event event of the key event.

Optionally, the determining unit 200 is further configured to determine whether an event transaction registration exists in the preset feature set; if yes, determine that the event transaction is registered as a registration of the touch screen event; if not, determine that the event transaction is registered as a key event registered.

4 is a block diagram of another structure of a page response apparatus according to an embodiment of the present invention. As shown in FIG. 4, the apparatus further includes: a screening module 26 configured to filter out the pre-sets of the focusable elements of all the labels of the webpage. A focusable element in the set of features; a determination module 28 configured to use the filtered focusable element as the first focusable element of the touch screen.

The page response method in the above technical solution is described below in conjunction with the preferred embodiment, but is not intended to limit the embodiments of the present invention.

Preferred embodiment 1

The apparatus for improving the preferred embodiment 1 of the present invention can be understood to be mainly composed of six parts. FIG. 5 is a block diagram showing the overall structure of a preferred embodiment 1 according to the present invention. As shown in FIG. 5, the main control module 50 and the focus element capturing module are included. 52. The touch screen event conversion module 54, the focus navigation module 56, the feature set query module 58, and the feature set update module 60. The role of each core module is roughly described as follows:

The focus element capture module 52 (corresponding to the acquisition module 22 of the above embodiment), in addition to capturing elements of a conventional focus attribute (such as an A-tag with a URL link, an INPUT tag, another tag with a registered keyboard click event response, etc.), Also need to capture the query system based on feature set Determining the focusable elements on the touch screen;

The touch screen event conversion module 54 (corresponding to the conversion module 20 of the above embodiment) also converts the touch event registration of the touch screen webpage into a keyboard event registration according to the feature set query system, so that only the response triggered by the touch event can be triggered by the keyboard event instead. ;

The focus navigation module 56 is the next focusable element that is closest to the focused element in the current web page in the direction when the mobile phone direction key is triggered;

The feature set query module 58 includes a query of touch screen events and an attribute feature query of the touch screen focusable elements. The touch screen event mainly refers to a gesture event that can only be triggered on the touch screen, and whether the event registered by the web page belongs to a touch screen event to determine the registration converted into a button event. The attribute feature of the touch screen focusable element means that although some elements do not have regular focus features (A-tag, INPUT tag, with registered keyboard confirmation event response), some attribute fields of the element contain key information for response event processing, these attributes. The fields form the attribute feature set of the touch screen focusable elements (such as data-src, data-href, data-url, data-target, etc.). Although these elements are not directly registered for event processing, when an event occurs on a touch screen web page, the web page dynamically constructs the transaction that the element needs to process based on the attributes of the corresponding element in the event. So with this attribute feature set, you can determine the elements that can be focused on the touch screen;

The feature set update module 60 mainly considers that in addition to the attribute fields associated with the event processing included in the most common touch screen focusable elements, some web pages may also have other attribute fields associated with the event processing. Therefore, it is necessary to automatically update this feature set at any time in order to include as much as possible the attribute fields associated with event processing on all touch screen web pages;

A preferred embodiment 1 of the present invention provides a method for navigating through a button on a touch screen web page based on a touch screen web page focusable element feature set in a browser. FIG. 5 is a schematic diagram of an overall structure of a button webpage navigation method provided by the embodiment, and includes a main control module 50, a focus element capture module 52, a touch screen event conversion module 54, a focus navigation module 56, and a feature set. The query module 58 and the feature set update module 60. As can be seen from FIG. 5, during the web page loading process, the main control module 50 activates the touch screen event conversion module 54 to convert the registration of the web page touch screen event into a registration of the key confirmation event. The main control module 50 when the user presses the direction key The focus navigation module 56 is again activated to navigate through the web page. The most critical focus element detection step in the navigation process is mainly that the module captures the elements of the web page with the focus attribute through another focus element capture module 52. The above touch screen event conversion module 54 and focus element capture module 52 both rely on the feature set query module 58 to find corresponding features to perform touch screen event conversion and touch screen focus element detection, respectively. The feature data in the feature set query module 58 is that the master module 50 periodically updates the features through the feature set update module 60. In the preferred embodiment of the invention, the updating of the feature set and the focus processing after capturing the focusable elements are conventional methods and will not be described in detail herein. The following focuses on two key technical processing steps, touch screen event registration conversion and touch screen focus element detection.

6 is a flowchart of main processing of touch screen event registration conversion according to a preferred embodiment 1 of the present invention. As shown in FIG. 6, the steps are as follows:

Step S602: monitoring the webpage for event transaction registration during the webpage loading phase or other interaction phase;

Step S604: Determine whether the event belongs to a touch screen event in the feature set query module. The feature set mainly includes touchstart, touchend, mousedown, mouseup, etc., which can be continuously updated and supplemented by the update module. If the event does not belong to the touch screen event, proceed to step S608, otherwise proceed to the next step S606;

Step S606: Acquire a registration transaction corresponding to the event, and register a button confirmation event into the transaction, that is, the transaction is processed when a button confirmation event occurs on the webpage;

Step S608: registering the event according to the original registration process;

In addition to the processing flow of the original touch event, the above steps can mainly achieve two advantages: First, those elements that only register the touch event without registering the button confirmation event can be regarded as the focusable element and thus navigated on the button. The middle can be focused, and the second is that when the button confirms that the event occurs, the transaction that the original touch event wishes to trigger can also occur.

FIG. 7 is a flowchart of main processes for capturing a focusable element when a direction key is navigated in a webpage according to a preferred embodiment of the present invention. As shown in FIG. 7, the main steps are as follows:

Step S702: When the user presses the direction key to start navigation in the webpage, first traverse the network Individual element nodes in the page DOM tree;

Decision S704: determining whether the element node belongs to a conventional focusable node, and if the element node is a conventional focusable node, proceeding to step S712, otherwise proceeding to the next step S706. The primary condition for determining whether it is a regular focusable node is that the element is an A-tag or an INPUT tag or a transaction registration with a registered keyboard confirmation event on the element;

Decision S706: determining whether the ancestor node of the element node has a transaction registration registering a keyboard confirmation event, if not, proceeding to step S710, otherwise proceeding to the next step S708. The judgment of this step is mainly to consider that the touch screen webpage is to uniformly register the event response of multiple elements on an ancestor node;

Step S708: The attribute feature field of each touch screen focusable element in the feature set query module is sequentially searched as the attribute field of the element. If one of the corresponding element attributes is not empty, the process proceeds to step S712, otherwise Go to the next step S710 for processing. The attribute feature field of the touch screen focusable element mainly includes href, url, data-src, data-href, data-url, data-target, etc., and these feature fields can be continuously updated and supplemented by the update module;

Step S710: Obtain the next element node in the DOM tree and then re-enter the process in step S702;

Step S712: The element node is included in the focusable element processing, that is, in the navigation processing module, it is determined whether to focus on the element according to the position of the element from the current focus element. This process ends.

Through the above steps, those elements on the touch screen webpage that do not have the normal focus attribute can be detected in the button navigation to complete the focus processing of the element only if the focus is needed.

In summary, the embodiment of the present invention achieves the following technical effects: solving the problem that the touch screen-based webpage cannot be browsed by the button event of the physical key for the mobile phone with the physical key in the related art, thereby realizing even the user to use The low-end mobile phone with only physical keys can still respond to most of the touch screen-based pages on the market, greatly improving the use. User experience.

Embodiments of the present invention also provide a storage medium. Optionally, in the embodiment, the foregoing storage medium may be configured to store program code for performing the following steps:

S1, during the page loading process, converting the registration of the touch screen event in the page into the registration of the button event;

S2, after the page loading is completed, acquiring a first focusable element applied to the touch screen in the webpage, and converting the first focusable element into a second focusable element applied to the button;

S3, triggering a response operation to the second focusable element by a button event.

Optionally, in this embodiment, the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory. A variety of media that can store program code, such as a disc or a disc.

For example, the specific examples in this embodiment may refer to the examples described in the foregoing embodiments and the optional embodiments, and details are not described herein again.

It will be apparent to those skilled in the art that the various modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.

The above description is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Industrial applicability

Claims

A page response method, including:

During the page loading process, the registration of the touch screen event in the page is converted into the registration of the button event;

After the page loading is completed, acquiring a first focusable element applied to the touch screen in the webpage, and converting the first focusable element into a second focusable element applied to the button;

A response operation to the second focusable element is triggered by the button event.
The method of claim 1 wherein converting the registration of the touch screen event in the page to the registration of the key event comprises:

When the page is monitored for event transaction registration, it is determined whether the event transaction registration is a registration of a touch screen event;

If so, the current event transaction registration process is stopped and the registration of the key event is loaded into the event transaction registration.
The method of claim 2, wherein determining whether the event transaction registration is a registration of a touch screen event comprises:

Determining whether the event transaction registration exists in a preset feature set;

If so, determining that the event transaction is registered as a registration of a touch screen event;

If not, it is determined that the event transaction is registered as a registration of a button event.
The method of claim 1, wherein before acquiring the first focusable element applied to the touch screen in the webpage, the method further comprises:

Filtering the focusable elements located in a preset feature set from the focusable elements of all the labels of the webpage;

The filtered focusable element is used as the first focusable element of the touch screen.
The method according to claim 3 or 4, wherein

The feature set includes at least: a gesture event indicated by the touch screen event, an attribute feature of the first focusable element, wherein the attribute feature includes: key information in response to the event.
The method according to claim 3 or 4, wherein the feature set is updated when a predetermined time comes.
A page response device comprising:

The conversion module is configured to convert the registration of the touch screen event in the page into the registration of the key event during the page loading process;

Obtaining a module, configured to: after the page loading is completed, acquire a first focusable element applied to the touch screen in the webpage, and convert the first focusable element into a second focusable element applied to the button;

A triggering module is configured to trigger a response operation to the second focusable element by the button event.
The apparatus of claim 7, wherein the conversion module comprises:

a determining unit, configured to: when the page is monitored for event transaction registration, determine whether the event transaction registration is a registration of a touch screen event;

Stop unit, set to stop the current event transaction registration process when the event transaction is registered as a registration of a touch screen event;

a load unit configured to load the registration of the key event into the event transaction registration.
The apparatus according to claim 8, wherein the determining unit is further configured to determine whether the event transaction registration exists in a feature set set in advance; if yes, determine that the event transaction is registered as a registration of a touch screen event; If not, it is determined that the event transaction is registered as a registration of a button event.
The apparatus of claim 7 wherein said apparatus further comprises:

a screening module configured to filter out focusable elements located in a preset feature set from focusable elements of all tags of the web page;

A determining module is arranged to use the filtered focusable element as the first focusable element of the touch screen.