CN112733064B - Page display method and device - Google Patents
Page display method and device Download PDFInfo
- Publication number
- CN112733064B CN112733064B CN202110056118.6A CN202110056118A CN112733064B CN 112733064 B CN112733064 B CN 112733064B CN 202110056118 A CN202110056118 A CN 202110056118A CN 112733064 B CN112733064 B CN 112733064B
- Authority
- CN
- China
- Prior art keywords
- page
- url link
- website
- request
- link address
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
- G06F16/972—Access to data in other repository systems, e.g. legacy data or dynamic Web page generation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/957—Browsing optimisation, e.g. caching or content distillation
- G06F16/9574—Browsing optimisation, e.g. caching or content distillation of access to content, e.g. by caching
Abstract
An embodiment of the present disclosure provides a method and an apparatus for displaying a page, where the method is applied to a browser in a mobile terminal, and includes: responding to a website access request of a user, judging whether the website is located in a preset website white list, if so, monitoring a URL link click event in the website, acquiring a clicked URL link address, if not, acquiring the clicked URL link address in the website from an operating system of the mobile terminal in a callback mode, then creating a webpage view, displaying page data corresponding to the clicked URL link address in the created webpage view, caching the displayed webpage view, and after receiving a reloading request of the user for the page data corresponding to the clicked URL link address, invoking the cached webpage view to load, wherein the reloading request comprises a page forward request or a page backward request. By the method and the device, the advancing and retreating efficiency of the webpage can be improved.
Description
Technical Field
The present document relates to the field of computer technologies, and in particular, to a method and apparatus for displaying a page.
Background
On a mobile terminal, such as a mobile phone terminal, a user typically browses web site content through a browser. When a user clicks a URL (uniform resource locator system, uniform resource locator) link in a website, for some websites, the browser may obtain the URL link address clicked by the user from the mobile terminal operating system through a callback function supported by the mobile terminal operating system, and then create a web page view to show the page requested by the user. After the browser creates the webpage view to display the webpage requested by the user, the displayed webpage view can be cached, so that the reloading of the webpage is facilitated. For some websites, due to the limitation of the programming language of the websites, the browser cannot acquire the URL link address clicked by the user from the mobile terminal operating system through a callback function supported by the mobile terminal operating system, and further the browser cannot create a webpage view to display the page requested by the user.
For websites where the browser cannot acquire the URL link address through callback, the mobile terminal operating system can destroy page data on the currently displayed webpage view and then display the page requested by the user on the currently displayed webpage view. However, since the mobile terminal does not create and cache a new web page view, reloading of the page data is inconvenient.
Based on this, it is necessary to provide a technical solution to solve the problem that for some websites, the browser cannot acquire the URL link address clicked by the user through the callback function supported by the mobile terminal operating system, so that the browser cannot create and cache a new webpage view to display the page, which is inconvenient for reloading the page data.
Disclosure of Invention
An object of one embodiment of the present disclosure is to provide a method and an apparatus for displaying a page, which solve the problem that for some websites, a browser cannot obtain a URL link address clicked by a user through a callback function supported by a mobile terminal operating system, so that the browser cannot create and cache a new web page view to display the page, which is inconvenient for reloading page data.
To solve the above technical problems, an embodiment of the present specification is implemented as follows:
in a first aspect, an embodiment of the present disclosure provides a page displaying method, which is applied to a browser in a mobile terminal, including:
receiving a website access request of a user, and responding to the website access request to judge whether the website is positioned in a preset website white list;
if the URL link is located, monitoring a URL link clicking event of a uniform resource positioning system in the website, and acquiring a clicked URL link address, and if the URL link is not located, acquiring the clicked URL link address in the website from an operating system of the mobile terminal in a callback mode;
Acquiring the operation parameters of the browser, creating a webpage view according to the operation parameters of the browser, and displaying page data corresponding to the clicked URL link address in the created webpage view;
caching the displayed webpage view, and after receiving a reloading request of a user for page data corresponding to the clicked URL link address, calling the cached webpage view to load in response to the reloading request; wherein the reload request comprises a page forward request or a page backward request; the page advancing request is used for requesting to advance to a page corresponding to the clicked URL link address; and the page back request is used for requesting to back to the page corresponding to the clicked URL link address.
In a second aspect, another embodiment of the present disclosure provides a page display device, which is applied to a browser in a mobile terminal, including:
the website judging unit is used for receiving a website access request of a user, responding to the website access request and judging whether the website is positioned in a preset website white list or not;
the link acquisition unit is used for monitoring URL link clicking events of the uniform resource positioning system in the website if the URL link clicking events are located, acquiring clicked URL link addresses, and acquiring the clicked URL link addresses in the website from an operating system of the mobile terminal in a callback mode if the URL link clicking events are not located;
The page display unit is used for acquiring the operation parameters of the browser, creating a webpage view according to the operation parameters of the browser, and displaying page data corresponding to the clicked URL link address in the created webpage view;
the first reloading unit is used for caching the displayed webpage view, and after receiving a reloading request of a user for the webpage data corresponding to the clicked URL link address, the first reloading unit responds to the reloading request to call the cached webpage view for loading; wherein the reload request comprises a page forward request or a page backward request; the page advancing request is used for requesting to advance to a page corresponding to the clicked URL link address; and the page back request is used for requesting to back to the page corresponding to the clicked URL link address.
In a third aspect, a further embodiment of the present specification provides a page display device, comprising: a memory, a processor, and computer-executable instructions stored on the memory and executable on the processor, which when executed by the processor, implement the steps of the page presentation method as described in the first aspect above.
In a fourth aspect, a further embodiment of the present specification provides a computer-readable storage medium for storing computer-executable instructions which, when executed by a processor, implement the steps of the page presentation method as described in the first aspect above.
In an embodiment of the present disclosure, for a website in a website whitelist, a clicked URL link address in the website may be obtained by monitoring a URL link click event in the website, and for a website outside the website whitelist, a clicked URL link address in the website may be obtained from an operating system of a mobile terminal by a callback manner, so as to solve the problem that for some websites, a browser cannot obtain a URL link address clicked by a user through a callback function supported by a mobile terminal operating system. After the URL link address clicked by the user is obtained, the browser can create a webpage view, page data corresponding to the clicked URL link address is displayed in the created webpage view, and the displayed webpage view is cached, so that after a reloading request of the user for the page data corresponding to the clicked URL link address is received, the cached webpage view is called for loading in response to the reloading request, the reloading of the page data is conveniently realized, and the problems that a browser cannot create and cache a new webpage view to display a page and the reloading of the page data is inconvenient are solved. Wherein the reload request comprises a page forward request or a page backward request. Therefore, according to the embodiment, the clicked URL link address can be acquired for various websites, page data are displayed through the created webpage view, and the displayed webpage view is cached, so that reloading of the page is realized, and the advancing and retreating efficiency of the page is improved.
Drawings
In order to more clearly illustrate the technical solution in one or more embodiments of the present description, the following description will briefly introduce the drawings that are needed in the embodiments or the description of the prior art, it is obvious that the drawings in the following description are only some embodiments described in the present description, and other drawings may be obtained according to these drawings without inventive effort to a person of ordinary skill in the art.
Fig. 1 is a flow chart of a page display method according to an embodiment of the present disclosure;
fig. 2 is a flow chart of a page display method according to another embodiment of the present disclosure;
fig. 3 is a schematic block diagram of a page display device according to an embodiment of the present disclosure;
fig. 4 is a schematic structural diagram of a page display device according to an embodiment of the present disclosure.
Detailed Description
In order to enable a person skilled in the art to better understand the technical solutions in one or more embodiments of the present specification, the technical solutions in one or more embodiments of the present specification will be clearly and completely described below with reference to the drawings in one or more embodiments of the present specification, and it is obvious that the described embodiments are only some embodiments of the present specification, not all embodiments. All other embodiments, which can be made by one or more embodiments of the present disclosure without inventive faculty, are intended to be within the scope of the present disclosure.
An object of one embodiment of the present disclosure is to provide a method and an apparatus for displaying a page, which solve the problem that for some websites, a browser cannot obtain a URL link address clicked by a user through a callback function supported by a mobile terminal operating system, so that the browser cannot create and cache a new web page view to display the page, which is inconvenient for reloading page data.
First, the web page views mentioned below in this specification are referred to as webviews.
Fig. 1 is a flowchart of a page display method according to an embodiment of the present disclosure, where the method is applied to a browser in a mobile terminal and executed by the browser. The mobile terminal comprises, but is not limited to, mobile electronic equipment which is realized based on an android system or an apple system or other mobile terminal operating systems, such as a mobile phone, a computer and a tablet personal computer. As shown in fig. 1, the page display method includes the following steps:
step S102, receiving a website access request of a user, and responding to the website access request to judge whether the website is positioned in a preset website white list;
step S104, if the URL link is located, monitoring a URL link clicking event in the website, acquiring a clicked URL link address, and if the URL link is not located, acquiring the clicked URL link address in the website from an operating system of the mobile terminal in a callback mode;
Step S106, acquiring operation parameters of the browser, creating a webpage view according to the operation parameters of the browser, and displaying page data corresponding to the clicked URL link address in the created webpage view;
step S108, caching the displayed webpage view, and after receiving a reloading request of a user for page data corresponding to the clicked URL link address, invoking the cached webpage view to load in response to the reloading request.
Wherein the reload request comprises a page forward request or a page backward request. The page advance request is used for requesting to advance to the page corresponding to the clicked URL link address. The page back request is used for requesting to back to the page corresponding to the clicked URL link address.
In this embodiment, for websites in the website whitelist, the clicked URL link address in the website may be obtained by monitoring the URL link click event in the website, and for websites other than the website whitelist, the clicked URL link address in the website may be obtained from the operating system of the mobile terminal by callback, so as to solve the problem that for some websites, the browser cannot obtain the URL link address clicked by the user through the callback function supported by the mobile terminal operating system. After the URL link address clicked by the user is obtained, the browser can create a webpage view, page data corresponding to the clicked URL link address is displayed in the created webpage view, and the displayed webpage view is cached, so that after a reloading request of the user for the page data corresponding to the clicked URL link address is received, the cached webpage view is called for loading in response to the reloading request, the reloading of the page data is conveniently realized, and the problems that a browser cannot create and cache a new webpage view to display a page and the reloading of the page data is inconvenient are solved. Wherein the reload request comprises a page forward request or a page backward request. Therefore, according to the embodiment, the clicked URL link address can be acquired for various websites, page data are displayed through the created webpage view, and the displayed webpage view is cached, so that reloading of the page is realized, and the advancing and retreating efficiency of the page is improved.
In step S102, the browser receives a website access request from the user. For example, when a user inputs a website address in an address bar of a browser and performs a jump operation, the browser receives a website access request for the website from the user in response to the jump operation. Or when the user clicks the homepage link of a website in a certain navigation webpage, the browser responds to the clicking operation and receives a website access request of the user for the website.
In the step S102, after receiving the website access request from the user, the browser determines whether the website is located in a preset website white list in response to the website access request. In an embodiment of the present disclosure, a website whitelist is preset, in which a plurality of website domain names are recorded, and the website with the recorded domain names belongs to the whitelist website. The website white list can be located in an installation package of the browser, and can be directly loaded in the mobile terminal along with the installation process of the browser, or can be located at a background server corresponding to the browser.
In the step S102, the browser determines whether the website is in a preset website white list, which may be: and acquiring the domain name of the website, and judging whether the domain name of the website is positioned in a preset website white list. It can be understood that if the domain name of the website is in the preset website whitelist, the website is in the preset website whitelist and belongs to the whitelist website, and if the domain name of the website is not in the preset website whitelist, the website is not in the preset website whitelist and does not belong to the whitelist website.
Typically, the website whitelist may be determined empirically. For example, based on experience, it is determined that the browser cannot obtain the websites of the clicked URL link address from the operating system of the mobile terminal in a callback manner, the websites are determined as whitelist websites, and domain names of the websites are recorded in a website whitelist.
In this embodiment, whether the website is located in the preset website white list is judged by judging the domain name, which has the advantage of fast and accurate judgment.
If the website accessed by the user is located in the preset website white list, in step S104, the browser monitors the URL link click event in the website and obtains the clicked URL link address. Monitoring URL link clicking events in websites and obtaining clicked URL link addresses, wherein the URL link clicking events comprise the following steps:
(a1) Monitoring a selected starting event aiming at the URL link in the website, and acquiring a selected URL link address;
(a2) Monitoring a selected ending event corresponding to the selected starting event in the website, and judging the moving distance of the selected URL link address according to the selected starting event and the selected ending event;
(a3) If the moving distance is within the preset distance range, determining that the selected starting event and the selected ending event are combined to be URL link clicking events, and determining the acquired URL link address as the clicked URL link address.
In one embodiment, the selected start event comprises a touchDown event and the selected end event comprises a touchUp event. In this embodiment, in the action (a 1), the browser may monitor the touch event of the user in the website through the pre-written JS script, if the touch down event is monitored, acquire an element corresponding to the touch down event, and if the element is a URL link, acquire the URL link address of the touched touch down. If the element is not a URL link, monitoring continues.
In the action (a 2), the browser monitors a touchUp event which occurs first after the touchDown event through the JS script, and takes the touchUp event as a touchUp event corresponding to the touchDown event. The browser judges the moving distance of the URL link address of the touchDown between the touchDown event and the touchUp event.
In the action (a 3), if the moving distance of the URL link address of touchDown between the touchDown event and the touchUp event is within the preset distance range, the browser determines that the touchDown event and the touchUp event are combined into the URL link clicking event, and determines the acquired URL link address as the clicked URL link address. If the moving distance of the URL link address of the touchDown between the touchDown event and the touchUp event is not within the preset distance range, the browser determines that the touchDown event and the touchUp event are combined into the URL link moving event, and does not determine the acquired URL link address as the clicked URL link address.
If the website accessed by the user is not located in the preset website white list, in the step S104, the browser obtains the clicked URL link address in the website from the operating system of the mobile terminal in a callback manner, which specifically includes: the browser calls back the URL link address clicked in the website through a sholded overrideUrlLoading function of the webview component provided by the operating system of the mobile terminal.
It can be seen that, through step S102 and step S104, the browser can acquire the URL link address clicked in the website for various websites. Moreover, the clicked URL link address is obtained by monitoring the TOUCH event through the JS script, the monitoring process is simple and quick, the URL link address clicked by the user can be obtained rapidly, and the problem that for some websites, the browser cannot obtain the URL link address clicked by the user through a callback function supported by the mobile terminal operating system is solved.
Next, in step S106, the browser obtains the operation parameters of the browser, creates a web page view according to the operation parameters of the browser, and displays the page data corresponding to the clicked URL link address in the created web page view.
In one embodiment, the operating parameters of the browser include the amount of memory occupied by the browser and the number of cached web page views in the browser. Accordingly, in step S106, a web page view is created according to the operation parameters of the browser, specifically:
(b1) Judging whether the size of the memory occupied by the browser is smaller than the preset memory size or not, and judging whether the number of cached webpage views in the browser is smaller than the preset view number or not;
(b2) If the size of the occupied memory is smaller than the preset memory size and the number of the cached webpage views is smaller than the preset view number, creating the webpage views through a webpage view creation function provided by an operating system of the mobile terminal, otherwise, selecting the webpage view with the earliest history creation in the cached webpage views, destroying the webpage view with the earliest history creation, and creating the webpage views through the webpage view creation function provided by the operating system of the mobile terminal after the destruction is completed.
In the action (b 1), the browser judges whether the size of the memory occupied by the browser is smaller than the preset memory size, and judges whether the number of cached webpage views in the browser is smaller than the preset view number.
In the act (b 2), if the size of the occupied memory is smaller than the preset memory size and the number of cached web page views is smaller than the preset view number, the browser does not need to destroy the cached web page views, and creates a new web page view directly through a web page view creation function provided by an operating system of the mobile terminal. Otherwise, the browser selects the webpage view with the earliest history in the cached webpage views, destroys the webpage view with the earliest history so as to reduce the memory occupied by the browser, and creates a new webpage view through the webpage view creation function provided by the operating system of the mobile terminal after the destruction is completed.
All references to web views in this specification refer to webviews. The operating system of the mobile terminal may be an android system provided with webview creation functionality.
In this embodiment, when the memory occupied by the browser is too large, or the number of cached web page views of the browser is too large, the browser may create a new web page view by destroying the web page view created earliest in the history, so as to ensure that the page requested latest by the user can be loaded through the new web page view each time, and ensure that the page requested latest by the user is convenient to reload.
After creating the new web page view, in step S106, the browser displays the page data corresponding to the clicked URL link address in the created web page view. The browser firstly acquires page data corresponding to the clicked URL link address from the corresponding server, and then displays the page data in the created webpage view.
In one embodiment, if the browser determines that the size of the occupied memory is greater than or equal to the preset memory size, or determines that the number of cached web page views in the browser is greater than or equal to the preset view number, the browser may also destroy page data displayed in the currently displayed web page view, and display page data corresponding to the clicked URL link address in the currently displayed web page view. The browser can also cache the URL corresponding to the destroyed page data, so that when the user requests reloading the page, such as forward or backward, the page data is requested to be displayed to the corresponding server through the cached URL, and when the page data is displayed, the browser can create a new webpage view through the flow in fig. 1 for displaying.
In step S108, after displaying the page data corresponding to the clicked URL link address, the browser also caches the displayed web page view. And further, after receiving a reloading request of a user for page data corresponding to the clicked URL link address, calling the cached webpage view to load in response to the reloading request.
Wherein the reload request comprises a page forward request or a page backward request. The page advance request is used for requesting to advance to the page corresponding to the clicked URL link address. The page back request is used for requesting to back to the page corresponding to the clicked URL link address.
For convenience of description, a page corresponding to the clicked URL link address is referred to herein as a target page. After the user clicks to request the target page, the browser creates a new webpage view through the process in fig. 1, and the target page is displayed on the new webpage view. It can be appreciated that the user can also re-click on the URL link in the target page, so that the browser continues to recreate a new web page view showing the page requested by the user through the flow in fig. 1. After the user clicks the URL link to request the page for multiple times, the user can return to the target page in a page forward or page backward mode. When the user returns to the target page in a page advancing mode, the browser can receive a page advancing request of the user, and call a webpage view corresponding to the cached target page to load in response to the page advancing request. Similarly, when the user returns to the target page in a page back mode, the browser can receive a page back request of the user, and call a webpage view corresponding to the cached target page to load in response to the page back request.
For example, after the browser displays the target page, the user clicks a URL link in the target page, and the browser creates a new web page view to display the page data corresponding to the link. And the user executes page back operation, and the browser responds to a page back request of the user based on the operation, and calls a webpage view corresponding to the cached target page to load.
For another example, after the browser displays the target page, the user performs a page back operation, returns to the previous page of the target page, then performs a page forward operation, and based on the operation, the browser responds to a page forward request of the user, and calls a webpage view corresponding to the cached target page to load.
Therefore, according to the embodiment, the clicked URL link address can be acquired for various websites, page data are displayed through the created webpage view, the displayed webpage view is cached, and when a page reloading request of a user is received, the cached webpage view is fetched for loading, so that page reloading is realized, and the advancing and backing efficiency of the page is improved.
According to the foregoing description, when creating a new web page view and loading page data in the process in fig. 1, if the size of the memory occupied by the browser is greater than or equal to the preset memory size, or the number of cached web page views in the browser is greater than or equal to the preset view number, the web page view created earliest in the history needs to be selected from the cached web page views, the web page view created earliest in the history is destroyed, and after the destruction is completed, the web page view is created through the web page view creation function provided by the operating system of the mobile terminal.
Further, the method in this embodiment may further include the steps of:
(c1) Before destroying the webpage view created earliest in the history, caching URL link addresses corresponding to the page data displayed in the webpage view created earliest in the history;
(c2) Receiving a reloading request of a user for page data displayed in a webpage view created earliest in the history, and responding to the reloading request, acquiring page data corresponding to a cached URL link address from a server corresponding to the cached URL link address for loading;
wherein the reload request comprises a page forward request or a page backward request. The page advance request is used to request advance to the page shown in the view of the web page that was created earliest in the history. The page back request is used to request to back to the page shown in the view of the web page created earliest in the history.
Considering that the user may need to reload the page data shown in the webpage view created earliest in the history, for example, the user advances to the page shown in the webpage view created earliest in the history by means of page advancing, or the user retreats to the page shown in the webpage view created earliest in the history by means of page retreating, in this embodiment, the URL link address corresponding to the page data shown in the webpage view created earliest in the history is cached before destroying the webpage view created earliest in the history. And further, when a reloading request of a user for page data displayed in the webpage view created earliest in the history is received, responding to the reloading request, and acquiring the page data corresponding to the cached URL link address from the server corresponding to the cached URL link address for loading so as to meet the reloading requirement of the page.
Wherein the reload request of the user comprises a page forward request or a page backward request. The page advance request is used to request advance to the page shown in the view of the web page that was created earliest in the history. The page back request is used to request to back to the page shown in the view of the web page created earliest in the history. For example, when the user proceeds to the page displayed in the webpage view created earliest in the history through the page advancing operation in the process of browsing the website, the browser receives the page advancing request of the user, and takes the page advancing request as the reloading request. In another example, when the user backs to the page displayed in the webpage view created earliest in the history through page back operation in the process of browsing the website, the browser receives a page back request of the user, and the page back request is used as a reloading request.
Therefore, in this embodiment, before the webpage view created by the earliest history needs to be destroyed, the URL corresponding to the view is also cached, so that the reloading of the webpage is facilitated, and the page forward and backward requirements of the user are met.
In this embodiment, in step S106, after displaying the page data corresponding to the clicked URL link address in the created web page view, the browser further sends a URL link cancellation response event to the operating system of the mobile terminal. The URL link cancellation response event is used to notify the operating system of the mobile terminal that the clicked URL link address is not responded, so that page data corresponding to the clicked URL link address is not displayed in the currently displayed web page view.
Taking an example that an operating system of the mobile terminal is an android system, when a user clicks a URL link in a website, the android system can acquire the URL link clicked by the user based on the function of the android system, and defaults to destroy page data in a currently displayed webpage view, and display the page data corresponding to the clicked URL link in the currently displayed webpage view. Based on this, in this embodiment, after the browser displays the page data corresponding to the clicked URL link address in the created web page view, a URL link cancellation response event is sent to the android system, where the event may be a cancel event, so that the operation system of the mobile terminal is notified by the cancel event that the clicked URL link address is not responded, so that the page data corresponding to the clicked URL link address is not displayed in the currently displayed web page view.
It can be seen that, in this embodiment, the browser may send a URL link cancellation response event to the operating system of the mobile terminal to avoid the operating system of the mobile terminal responding to the clicked URL link, so as to avoid displaying the page data corresponding to the clicked URL link address in the currently displayed web page view.
Fig. 2 is a flowchart of a page display method according to another embodiment of the present disclosure, where the method is applied to a browser in a mobile terminal and executed by the browser. The mobile terminal comprises, but is not limited to, mobile electronic equipment which is realized based on an android system or an apple system or other mobile terminal operating systems, such as a mobile phone, a computer and a tablet personal computer. As shown in fig. 2, the page display method includes the following steps:
Step S202, a website access request of a user is received.
Step S204, judging whether the domain name of the website is in a preset website white list.
If yes, go to step S206, otherwise, go to step S208.
In step S206, the URL link click event in the website is monitored by monitoring the TOUCH event, and the clicked URL link address is obtained.
Step S208, the clicked URL link address in the website is obtained from the sholded overrideUrlLoading callback of the webview.
Step S210, creating a new webpage view, and displaying the page data corresponding to the clicked URL link address in the created new webpage view.
Step S212, a cancel event is sent to the operating system of the mobile terminal to inform the operating system of the mobile terminal that the clicked URL link address is not responded.
Step S214, caching the displayed webpage view.
In step S216, if a page forward request is received from the user and used for requesting to forward to a page corresponding to the clicked URL link address, or a page backward request is received from the user and used for requesting to backward to a page corresponding to the clicked URL link address, the cached web page view is called and loaded.
In the flow shown in fig. 2, step S212 and step S214 may be performed simultaneously, or S212 may be performed first, then S214 may be performed, or S214 may be performed first, then S212 may be performed, and fig. 2 illustrates one of these cases as an example.
In summary, through the above method flows in fig. 1 and fig. 2, for websites in the website whitelist, the clicked URL link address in the website can be obtained by monitoring the URL link click event in the website, and for websites outside the website whitelist, the clicked URL link address in the website can be obtained from the operating system of the mobile terminal by callback, so that the problem that for some websites, the browser cannot obtain the URL link address clicked by the user through the callback function supported by the mobile terminal operating system is solved. After the URL link address clicked by the user is obtained, the browser can create a webpage view, page data corresponding to the clicked URL link address is displayed in the created webpage view, and the displayed webpage view is cached, so that after a reloading request of the user for the page data corresponding to the clicked URL link address is received, the cached webpage view is called for loading in response to the reloading request, the reloading of the page data is conveniently realized, and the problems that a browser cannot create and cache a new webpage view to display a page and the reloading of the page data is inconvenient are solved. Wherein the reload request comprises a page forward request or a page backward request. Therefore, through the method flows in fig. 1 and fig. 2, the clicked URL link address can be obtained for various websites, page data are displayed through the created web page view, and the displayed web page view is cached, so that reloading of the page is realized, and the advancing and retreating efficiency of the page is improved.
According to the description, after the page data is displayed in the newly built webpage view, the webpage view can be cached, so that the page can be conveniently reloaded when the user moves forward and backward. Several common page forward and backward scenarios are specifically described below.
Scene 1: the method comprises the steps that a user opens a webpage for the first time in a website, or the user always opens the webpage, if the user does not perform forward or backward operations, for example, three webpages are opened, the webview corresponding to the opened webview is webview1, webview2 and webview3 respectively, if the user opens a new webpage again, a new webview is created and named as webview4, the browser firstly adds the webview4 into a webview cache list, and if the number of the current webview exceeds the number of the predefined webview caches, for example, the number of the defined webview caches does not exceed 3, the webview1 is deleted after the webview4 is added into the webview cache list, so that the latest opened webpage can be ensured to enjoy the forward and backward webview caches. And, put url that the webview1 corresponds to in the url list of backing, can obtain url and open the webpage while backing to this url conveniently.
Scene 2: the user performs the forward and backward operations. In case 1, the user does not open a new page during the forward and backward processes. For example, when the user browses webview1, webview2 and webview3 in turn, and clicks back to webview2 once and then clicks forward in the process of browsing webview3, the browser displays webview3. In case 2, the user opens a new page during the forward and backward processes. For example, the user browses webview1, webview2 and webview3 in turn, clicks backward once to webview2 in the process of browsing webview3, and then clicks backward, so that the browser displays webview1. When the user clicks the URL4 in the process of browsing the webview1 and the browser displays the webview4, the browser firstly deletes and destroys the webview2 and the webview3, and the webview cache list is changed from the webview1, the webview2 and the webview3 to the webview1 and the webview4.
Scene 3: the user clicks backward, and if webview exists in the cache list, the webview corresponding to the index is displayed. If the first webview currently in the cache list (i.e., the earliest created webview), then a check is made as to whether the back url list is empty, and if not, creating a new webview opens the cached urls in the back url list. For example, url1, url2, url3 and url4 are opened, the webview cache list is webview2, webview3 and webview4, the backward url list is url1, the backward url list is clicked twice to the webview2, if the backward url is clicked again, a new webview is created to open url1, the webview1 is inserted into the head of the cache list, url1 is removed from the backward url list, the webview4 is destroyed, the forward url list is added with url4, the cache list of the webview is webview1, the webview2 and the webview3 are empty, and the forward url list is url4.
Scene 4: the user clicks forward, if the cache list has webview, the webview corresponding to the index is displayed, the last webview currently located in the cache list (i.e. the last created webview) is checked to see if the forward url list is empty, if not, a new webview is created to open the cached urls in the forward url list. For example, when url1, url2, url3 and url4 are opened, the webview cache list is webview2, webview3 and webview4 and is successively returned to url1, the cache list is webview1, webview2 and webview3, the forward url list is url4, if the forward list is clicked, the webview2 is directly displayed, the index points to the webview2 and is clicked once again to forward to webview3, if the forward list is clicked again, a new webview is created to open url4, the new webview is inserted to the end of the cache list, the forward url list is cleared up url4, the backward list is added to url1, the cache of the webview is webview2, the webview3 and the backward url4 when the backward list is added to url1, and the backward url1 is empty.
The specific flow of the page display method in each embodiment of the present disclosure is described in detail above, and a page display device is described below. Fig. 3 is a schematic block diagram of a page display device according to an embodiment of the present disclosure, where the device is applied to a browser in a mobile terminal, as shown in fig. 3, and the device includes:
a website judging unit 31, configured to receive a website access request of a user, and respond to the website access request to judge whether the website is located in a preset website white list;
the link obtaining unit 32 is configured to monitor a URL link click event of the URL in the website if the URL is located, and obtain a clicked URL link address, and if the URL is not located, obtain the clicked URL link address in the website from the operating system of the mobile terminal by a callback manner;
the page display unit 33 is configured to obtain an operation parameter of the browser, create a web page view according to the operation parameter of the browser, and display page data corresponding to the clicked URL link address in the created web page view;
the first reloading unit 34 is configured to cache the displayed web page view, and after receiving a reloading request of a user for the page data corresponding to the clicked URL link address, invoke the cached web page view to load in response to the reloading request; wherein the reload request comprises a page forward request or a page backward request; the page advancing request is used for requesting to advance to a page corresponding to the clicked URL link address; and the page back request is used for requesting to back to the page corresponding to the clicked URL link address.
Alternatively, the website determining unit 31 is specifically configured to:
and acquiring the domain name of the website, and judging whether the domain name of the website is positioned in a preset website white list.
Alternatively, the link acquiring unit 32 is specifically configured to:
monitoring a selected starting event aiming at the URL link in the website, and acquiring a selected URL link address;
monitoring a selected ending event corresponding to the selected starting event in the website, and judging the moving distance of the selected URL link address according to the selected starting event and the selected ending event;
and if the moving distance is within the preset distance range, determining that the selected starting event and the selected ending event are combined to be URL link clicking events, and determining the acquired URL link address as the clicked URL link address.
Optionally, the operation parameters of the browser include the size of the memory occupied by the browser and the number of cached web page views in the browser; the page display unit 33 is specifically configured to:
judging whether the size of the memory occupied by the browser is smaller than the preset memory size or not, and judging whether the number of cached webpage views in the browser is smaller than the preset view number or not;
If the size of the occupied memory is smaller than the preset memory size and the number of the cached webpage views is smaller than the preset view number, creating the webpage views through a webpage view creation function provided by an operating system of the mobile terminal, otherwise, selecting the webpage view with the earliest history creation in the cached webpage views, destroying the webpage view with the earliest history creation, and creating the webpage views through the webpage view creation function provided by the operating system of the mobile terminal after the destroying is completed.
Optionally, the device further comprises a second reloading unit, in particular for:
before destroying the webpage view created earliest in the history, caching URL link addresses corresponding to the page data displayed in the webpage view created earliest in the history;
receiving a reloading request of a user for page data displayed in a webpage view created earliest in the history, and responding to the reloading request, acquiring page data corresponding to a cached URL link address from a server corresponding to the cached URL link address for loading;
the reload request comprises a page forward request or a page backward request; the page advancing request is used for requesting to advance to a page displayed in a webpage view created earliest in the history; the page back request is used for requesting to back to the page shown in the webpage view created earliest in the history.
Optionally, the device further includes an event sending unit, specifically configured to:
in the created webpage view, after page data corresponding to the clicked URL link address is displayed, a URL link cancellation response event is sent to an operating system of the mobile terminal; the URL link cancellation response event is used for notifying an operating system of the mobile terminal not to respond to the clicked URL link address so as not to display page data corresponding to the clicked URL link address in the currently displayed webpage view.
In an embodiment of the present disclosure, for a website in a website whitelist, a clicked URL link address in the website may be obtained by monitoring a URL link click event in the website, and for a website outside the website whitelist, a clicked URL link address in the website may be obtained from an operating system of a mobile terminal by a callback manner, so as to solve the problem that for some websites, a browser cannot obtain a URL link address clicked by a user through a callback function supported by a mobile terminal operating system. After the URL link address clicked by the user is obtained, the browser can create a webpage view, page data corresponding to the clicked URL link address is displayed in the created webpage view, and the displayed webpage view is cached, so that after a reloading request of the user for the page data corresponding to the clicked URL link address is received, the cached webpage view is called for loading in response to the reloading request, the reloading of the page data is conveniently realized, and the problems that a browser cannot create and cache a new webpage view to display a page and the reloading of the page data is inconvenient are solved. Wherein the reload request comprises a page forward request or a page backward request. Therefore, according to the embodiment, the clicked URL link address can be acquired for various websites, page data are displayed through the created webpage view, and the displayed webpage view is cached, so that reloading of the page is realized, and the advancing and retreating efficiency of the page is improved.
The page display device provided in an embodiment of the present disclosure can implement each process in the foregoing embodiment of the page display method, and achieve the same functions and effects, which are not repeated here.
Further, an embodiment of the present disclosure further provides a page display device, and fig. 4 is a schematic structural diagram of the page display device provided in an embodiment of the present disclosure, as shown in fig. 4, where the device includes: memory 401, processor 402, bus 403, and communication interface 404. The memory 401, processor 402, and communication interface 404 communicate over a bus 403, and the communication interface 404 may include input output interfaces including, but not limited to, a keyboard, mouse, display, microphone, loudspeaker, and the like. In one embodiment, the page presentation device may be a mobile terminal running a browser.
In fig. 4, the memory 401 stores computer executable instructions executable on the processor 402, which when executed by the processor 402 implement the following procedures:
receiving a website access request of a user, and responding to the website access request to judge whether the website is positioned in a preset website white list;
If the URL link is located, monitoring a URL link clicking event of a uniform resource positioning system in the website, and acquiring a clicked URL link address, and if the URL link is not located, acquiring the clicked URL link address in the website from an operating system of the mobile terminal in a callback mode;
acquiring the operation parameters of the browser, creating a webpage view according to the operation parameters of the browser, and displaying page data corresponding to the clicked URL link address in the created webpage view;
caching the displayed webpage view, and after receiving a reloading request of a user for page data corresponding to the clicked URL link address, calling the cached webpage view to load in response to the reloading request; wherein the reload request comprises a page forward request or a page backward request; the page advancing request is used for requesting to advance to a page corresponding to the clicked URL link address; and the page back request is used for requesting to back to the page corresponding to the clicked URL link address.
Optionally, when the computer executable instructions are executed by the processor, determining whether the website is in a preset website whitelist includes:
And acquiring the domain name of the website, and judging whether the domain name of the website is positioned in a preset website white list.
Optionally, when the computer executable instructions are executed by the processor, monitoring URL link click events of the URL in the website and obtaining the clicked URL link address, including:
monitoring a selected starting event aiming at the URL link in the website, and acquiring a selected URL link address;
monitoring a selected ending event corresponding to the selected starting event in the website, and judging the moving distance of the selected URL link address according to the selected starting event and the selected ending event;
and if the moving distance is within the preset distance range, determining that the selected starting event and the selected ending event are combined to be URL link clicking events, and determining the acquired URL link address as the clicked URL link address.
Optionally, when the computer executable instructions are executed by the processor, the operating parameters of the browser include a memory size occupied by the browser and a number of cached web page views in the browser; creating a webpage view according to the operation parameters of the browser, including:
Judging whether the size of the memory occupied by the browser is smaller than the preset memory size or not, and judging whether the number of cached webpage views in the browser is smaller than the preset view number or not;
if the size of the occupied memory is smaller than the preset memory size and the number of the cached webpage views is smaller than the preset view number, creating the webpage views through a webpage view creation function provided by an operating system of the mobile terminal, otherwise, selecting the webpage view with the earliest history creation in the cached webpage views, destroying the webpage view with the earliest history creation, and creating the webpage views through the webpage view creation function provided by the operating system of the mobile terminal after the destroying is completed.
Optionally, when the computer executable instructions are executed by the processor, the following procedure may also be implemented:
before destroying the webpage view created earliest in the history, caching URL link addresses corresponding to the page data displayed in the webpage view created earliest in the history;
receiving a reloading request of a user for page data displayed in a webpage view created earliest in the history, and responding to the reloading request, acquiring page data corresponding to a cached URL link address from a server corresponding to the cached URL link address for loading;
The reload request comprises a page forward request or a page backward request; the page advancing request is used for requesting to advance to a page displayed in a webpage view created earliest in the history; the page back request is used for requesting to back to the page shown in the webpage view created earliest in the history.
Optionally, when the computer executable instructions are executed by the processor, the following procedure may also be implemented:
in the created webpage view, after page data corresponding to the clicked URL link address is displayed, a URL link cancellation response event is sent to an operating system of the mobile terminal; the URL link cancellation response event is used for notifying an operating system of the mobile terminal not to respond to the clicked URL link address so as not to display page data corresponding to the clicked URL link address in the currently displayed webpage view.
The page display device provided in an embodiment of the present disclosure can implement each process in the foregoing embodiment of the page display method, and achieve the same functions and effects, which are not repeated here.
Further, another embodiment of the present specification also provides a computer-readable storage medium for storing computer-executable instructions that when executed by a processor implement the following:
Receiving a website access request of a user, and responding to the website access request to judge whether the website is positioned in a preset website white list;
if the URL link is located, monitoring a URL link clicking event of a uniform resource positioning system in the website, and acquiring a clicked URL link address, and if the URL link is not located, acquiring the clicked URL link address in the website from an operating system of the mobile terminal in a callback mode;
acquiring the operation parameters of the browser, creating a webpage view according to the operation parameters of the browser, and displaying page data corresponding to the clicked URL link address in the created webpage view;
caching the displayed webpage view, and after receiving a reloading request of a user for page data corresponding to the clicked URL link address, calling the cached webpage view to load in response to the reloading request; wherein the reload request comprises a page forward request or a page backward request; the page advancing request is used for requesting to advance to a page corresponding to the clicked URL link address; and the page back request is used for requesting to back to the page corresponding to the clicked URL link address.
Optionally, when the computer executable instructions are executed by the processor, determining whether the website is in a preset website whitelist includes:
and acquiring the domain name of the website, and judging whether the domain name of the website is positioned in a preset website white list.
Optionally, when the computer executable instructions are executed by the processor, monitoring URL link click events of the URL in the web site and obtaining the clicked URL link address, including:
monitoring a selected starting event aiming at the URL link in the website, and acquiring a selected URL link address;
monitoring a selected ending event corresponding to the selected starting event in the website, and judging the moving distance of the selected URL link address according to the selected starting event and the selected ending event;
and if the moving distance is within the preset distance range, determining that the selected starting event and the selected ending event are combined to be URL link clicking events, and determining the acquired URL link address as the clicked URL link address.
Optionally, when the computer executable instructions are executed by the processor, the operating parameters of the browser include the size of memory occupied by the browser and the number of cached web page views in the browser; creating a webpage view according to the operation parameters of the browser, including:
Judging whether the size of the memory occupied by the browser is smaller than the preset memory size or not, and judging whether the number of cached webpage views in the browser is smaller than the preset view number or not;
if the size of the occupied memory is smaller than the preset memory size and the number of the cached webpage views is smaller than the preset view number, creating the webpage views through a webpage view creation function provided by an operating system of the mobile terminal, otherwise, selecting the webpage view with the earliest history creation in the cached webpage views, destroying the webpage view with the earliest history creation, and creating the webpage views through the webpage view creation function provided by the operating system of the mobile terminal after the destroying is completed.
Optionally, when the computer executable instructions are executed by the processor, the following procedure may also be implemented:
before destroying the webpage view created earliest in the history, caching URL link addresses corresponding to the page data displayed in the webpage view created earliest in the history;
receiving a reloading request of a user for page data displayed in a webpage view created earliest in the history, and responding to the reloading request, acquiring page data corresponding to a cached URL link address from a server corresponding to the cached URL link address for loading;
The reload request comprises a page forward request or a page backward request; the page advancing request is used for requesting to advance to a page displayed in a webpage view created earliest in the history; the page back request is used for requesting to back to the page shown in the webpage view created earliest in the history.
Optionally, when the computer executable instructions are executed by the processor, the following procedure may also be implemented:
in the created webpage view, after page data corresponding to the clicked URL link address is displayed, a URL link cancellation response event is sent to an operating system of the mobile terminal; the URL link cancellation response event is used for notifying an operating system of the mobile terminal not to respond to the clicked URL link address so as not to display page data corresponding to the clicked URL link address in the currently displayed webpage view.
The computer readable storage medium includes Read-Only Memory (ROM), random access Memory (Random Access Memory RAM), magnetic disk or optical disk, etc.
The computer readable storage medium according to an embodiment of the present disclosure can implement the respective processes in the foregoing embodiments of the page display method, and achieve the same functions and effects, and are not repeated here.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, as relevant to see a section of the description of method embodiments.
The foregoing is merely exemplary of the present disclosure and is not intended to limit the present disclosure. Various modifications and variations of the embodiments described herein will be apparent to those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. that fall within the spirit and principles of the present document are intended to be included within the scope of the claims of the present document.
Claims (12)
1. The page display method is characterized by being applied to a browser in a mobile terminal and comprising the following steps of:
receiving a website access request of a user, and responding to the website access request to judge whether the website is positioned in a preset website white list;
if the URL link is located, monitoring a URL link clicking event of a uniform resource positioning system in the website, and acquiring a clicked URL link address, and if the URL link is not located, acquiring the clicked URL link address in the website from an operating system of the mobile terminal in a callback mode;
Acquiring the operation parameters of the browser, creating a webpage view according to the operation parameters of the browser, and displaying page data corresponding to the clicked URL link address in the created webpage view;
caching the displayed webpage view, and after receiving a reloading request of a user for page data corresponding to the clicked URL link address, calling the cached webpage view to load in response to the reloading request; wherein the reload request comprises a page forward request or a page backward request; the page advancing request is used for requesting to advance to a page corresponding to the clicked URL link address; and the page back request is used for requesting to back to the page corresponding to the clicked URL link address.
2. The method of claim 1, wherein determining whether the website is in a preset website whitelist comprises:
and acquiring the domain name of the website, and judging whether the domain name of the website is positioned in a preset website white list.
3. The method of claim 1, wherein monitoring URL link click events of a URL in the web site and obtaining the clicked URL link address comprises:
Monitoring a selected starting event aiming at the URL link in the website, and acquiring a selected URL link address;
monitoring a selected ending event corresponding to the selected starting event in the website, and judging the moving distance of the selected URL link address according to the selected starting event and the selected ending event;
and if the moving distance is within the preset distance range, determining that the selected starting event and the selected ending event are combined to be URL link clicking events, and determining the acquired URL link address as the clicked URL link address.
4. The method of claim 1, wherein the operating parameters of the browser include the amount of memory occupied by the browser and the number of cached web page views in the browser; creating a webpage view according to the operation parameters of the browser, including:
judging whether the size of the memory occupied by the browser is smaller than the preset memory size or not, and judging whether the number of cached webpage views in the browser is smaller than the preset view number or not;
if the size of the occupied memory is smaller than the preset memory size and the number of the cached webpage views is smaller than the preset view number, creating the webpage views through a webpage view creation function provided by an operating system of the mobile terminal, otherwise, selecting the webpage view with the earliest history creation in the cached webpage views, destroying the webpage view with the earliest history creation, and creating the webpage views through the webpage view creation function provided by the operating system of the mobile terminal after the destroying is completed.
5. The method according to claim 4, wherein the method further comprises:
before destroying the webpage view created earliest in the history, caching URL link addresses corresponding to the page data displayed in the webpage view created earliest in the history;
receiving a reloading request of a user for page data displayed in a webpage view created earliest in the history, and responding to the reloading request, acquiring page data corresponding to a cached URL link address from a server corresponding to the cached URL link address for loading;
the reload request comprises a page forward request or a page backward request; the page advancing request is used for requesting to advance to a page displayed in a webpage view created earliest in the history; the page back request is used for requesting to back to the page shown in the webpage view created earliest in the history.
6. The method according to any one of claims 1-5, further comprising:
in the created webpage view, after page data corresponding to the clicked URL link address is displayed, a URL link cancellation response event is sent to an operating system of the mobile terminal; the URL link cancellation response event is used for notifying an operating system of the mobile terminal not to respond to the clicked URL link address so as not to display page data corresponding to the clicked URL link address in the currently displayed webpage view.
7. A page display device, which is applied to a browser in a mobile terminal, comprising:
the website judging unit is used for receiving a website access request of a user, responding to the website access request and judging whether the website is positioned in a preset website white list or not;
the link acquisition unit is used for monitoring URL link clicking events of the uniform resource positioning system in the website if the URL link clicking events are located, acquiring clicked URL link addresses, and acquiring the clicked URL link addresses in the website from an operating system of the mobile terminal in a callback mode if the URL link clicking events are not located;
the page display unit is used for acquiring the operation parameters of the browser, creating a webpage view according to the operation parameters of the browser, and displaying page data corresponding to the clicked URL link address in the created webpage view;
the first reloading unit is used for caching the displayed webpage view, and after receiving a reloading request of a user for the webpage data corresponding to the clicked URL link address, the first reloading unit responds to the reloading request to call the cached webpage view for loading; wherein the reload request comprises a page forward request or a page backward request; the page advancing request is used for requesting to advance to a page corresponding to the clicked URL link address; and the page back request is used for requesting to back to the page corresponding to the clicked URL link address.
8. The apparatus according to claim 7, wherein the website determining unit is specifically configured to:
and acquiring the domain name of the website, and judging whether the domain name of the website is positioned in a preset website white list.
9. The apparatus according to claim 7, wherein the link acquisition unit is specifically configured to:
monitoring a selected starting event aiming at the URL link in the website, and acquiring a selected URL link address;
monitoring a selected ending event corresponding to the selected starting event in the website, and judging the moving distance of the selected URL link address according to the selected starting event and the selected ending event;
and if the moving distance is within the preset distance range, determining that the selected starting event and the selected ending event are combined to be URL link clicking events, and determining the acquired URL link address as the clicked URL link address.
10. The apparatus of claim 7, wherein the operating parameters of the browser include an amount of memory occupied by the browser and a number of cached web page views in the browser; the page display unit is specifically configured to:
Judging whether the size of the memory occupied by the browser is smaller than the preset memory size or not, and judging whether the number of cached webpage views in the browser is smaller than the preset view number or not;
if the size of the occupied memory is smaller than the preset memory size and the number of the cached webpage views is smaller than the preset view number, creating the webpage views through a webpage view creation function provided by an operating system of the mobile terminal, otherwise, selecting the webpage view with the earliest history creation in the cached webpage views, destroying the webpage view with the earliest history creation, and creating the webpage views through the webpage view creation function provided by the operating system of the mobile terminal after the destroying is completed.
11. The apparatus according to claim 10, characterized in that it further comprises a second reloading unit, in particular for:
before destroying the webpage view created earliest in the history, caching URL link addresses corresponding to the page data displayed in the webpage view created earliest in the history;
receiving a reloading request of a user for page data displayed in a webpage view created earliest in the history, and responding to the reloading request, acquiring page data corresponding to a cached URL link address from a server corresponding to the cached URL link address for loading;
The reload request comprises a page forward request or a page backward request; the page advancing request is used for requesting to advance to a page displayed in a webpage view created earliest in the history; the page back request is used for requesting to back to the page shown in the webpage view created earliest in the history.
12. The apparatus according to any of the claims 7-11, characterized in that the apparatus further comprises an event sending unit, in particular for:
in the created webpage view, after page data corresponding to the clicked URL link address is displayed, a URL link cancellation response event is sent to an operating system of the mobile terminal; the URL link cancellation response event is used for notifying an operating system of the mobile terminal not to respond to the clicked URL link address so as not to display page data corresponding to the clicked URL link address in the currently displayed webpage view.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110056118.6A CN112733064B (en) | 2021-01-15 | 2021-01-15 | Page display method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110056118.6A CN112733064B (en) | 2021-01-15 | 2021-01-15 | Page display method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112733064A CN112733064A (en) | 2021-04-30 |
| CN112733064B true CN112733064B (en) | 2023-06-27 |
Family
ID=75591668
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110056118.6A Active CN112733064B (en) | 2021-01-15 | 2021-01-15 | Page display method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112733064B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101996077A (en) * | 2010-09-08 | 2011-03-30 | 海皮士（北京）网络技术有限公司 | Method and system for embedding browser in three-dimensional client end |
| KR20130007186A (en) * | 2011-06-30 | 2013-01-18 | 주식회사 케이티 | Web massaging system and method for providing information related visiting-service |
| CN104182229A (en) * | 2014-08-21 | 2014-12-03 | 乐视网信息技术（北京）股份有限公司 | Callback display method and device and callback method and device |
| CN104915461A (en) * | 2015-07-10 | 2015-09-16 | 广州神马移动信息科技有限公司 | Page presentation method and device |
| CN108197126A (en) * | 2016-12-08 | 2018-06-22 | 阿里巴巴集团控股有限公司 | A kind of processing method and system of data displaying, client and server |
| CN109062626A (en) * | 2018-07-09 | 2018-12-21 | 北京奇艺世纪科技有限公司 | Exchange method, device and the equipment of Web page component and Native component |
| CN109274978A (en) * | 2018-08-24 | 2019-01-25 | 武汉斗鱼网络科技有限公司 | A kind of cooperation bootstrap technique, device, terminal and the storage medium of direct broadcasting room |
| CN111488576A (en) * | 2020-04-23 | 2020-08-04 | 成都安易迅科技有限公司 | Method and system for protecting tampering of home page, electronic equipment and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20070108315A (en) * | 2005-12-07 | 2007-11-09 | 한국전자통신연구원 | Appartus and method for privacy information sharing service using signed callback url message |
-
2021
- 2021-01-15 CN CN202110056118.6A patent/CN112733064B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101996077A (en) * | 2010-09-08 | 2011-03-30 | 海皮士（北京）网络技术有限公司 | Method and system for embedding browser in three-dimensional client end |
| KR20130007186A (en) * | 2011-06-30 | 2013-01-18 | 주식회사 케이티 | Web massaging system and method for providing information related visiting-service |
| CN104182229A (en) * | 2014-08-21 | 2014-12-03 | 乐视网信息技术（北京）股份有限公司 | Callback display method and device and callback method and device |
| CN104915461A (en) * | 2015-07-10 | 2015-09-16 | 广州神马移动信息科技有限公司 | Page presentation method and device |
| CN108197126A (en) * | 2016-12-08 | 2018-06-22 | 阿里巴巴集团控股有限公司 | A kind of processing method and system of data displaying, client and server |
| CN109062626A (en) * | 2018-07-09 | 2018-12-21 | 北京奇艺世纪科技有限公司 | Exchange method, device and the equipment of Web page component and Native component |
| CN109274978A (en) * | 2018-08-24 | 2019-01-25 | 武汉斗鱼网络科技有限公司 | A kind of cooperation bootstrap technique, device, terminal and the storage medium of direct broadcasting room |
| CN111488576A (en) * | 2020-04-23 | 2020-08-04 | 成都安易迅科技有限公司 | Method and system for protecting tampering of home page, electronic equipment and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| 基于iOS的搜狗阅读客户端的设计与实现;仲维涛;《中国优秀硕士学位论文全文数据库信息科技辑》(第7期);I138-99 * |
| 支持移动Web组件的高精度确定性重放技术;闫方戈;《中国优秀硕士学位论文全文数据库信息科技辑》(第1期);I138-769 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112733064A (en) | 2021-04-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110162720B (en) | Webpage loading method and device, computer equipment and storage medium | |
| US9756108B2 (en) | Preloading resources of a web page | |
| US7698256B1 (en) | History support for stateless Javascript Web client | |
| US20140143644A1 (en) | Web browser page transition acceleration | |
| CN107040584B (en) | Method and device for downloading picture by client | |
| US20140006487A1 (en) | Methods for making ajax web applications bookmarkable and crawable and devices thereof | |
| CN107181779B (en) | Method, device and system for processing access request | |
| CN104572777B (en) | Webpage loading method and device based on UIWebView component | |
| US20190109920A1 (en) | Browser resource pre-pulling method, terminal and storage medium | |
| CN104361071A (en) | Page preloading method and device | |
| CN112073405A (en) | Webpage data loading method and device, computer equipment and storage medium | |
| CN107679214B (en) | Link positioning method, device, terminal and computer readable storage medium | |
| CN108920703B (en) | HTTP cache optimization method and device | |
| CN108200132B (en) | Resource acquisition method, device, equipment and computer readable storage medium | |
| CN111191158A (en) | Webpage resource caching method and device, computer equipment and storage medium | |
| CN111198998A (en) | Network page loading method, device and system based on Ajax request | |
| CN110795650A (en) | Webpage opening method and device and computer readable storage medium | |
| CN112612982A (en) | Webpage preloading method and device and computer equipment | |
| CN112685669A (en) | Page rendering method and system | |
| WO2018046716A1 (en) | Web access enhancement | |
| CN112926002A (en) | Service request processing method and device | |
| CN111273964B (en) | Data loading method and device | |
| CN112733064B (en) | Page display method and device | |
| US10095791B2 (en) | Information search method and apparatus | |
| CN107341234B (en) | Page display method and device and computer readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |