Page control method, device, equipment and storage medium

Abstract

The embodiments of the present invention provide a page control method, apparatus, device and storage medium, which relate to the field of computer technology. The method is directed to a page structure including a container and a drawer, and includes: obtaining a routing list showing the mapping relationship between all relevant page URLs and their corresponding page component addresses; in response to a user's operation on a jump component in a container page, obtaining the page URL corresponding to the jump component, and matching the page component address corresponding to the page URL from the routing list; and obtaining the page component indicated by the matched page component address, and rendering the corresponding embedded page in the drawer through the page component. The present invention obtains the corresponding page component through the page URL to render the embedded page in the drawer, thereby avoiding repeated loading of the same resources in the container page and the embedded page, and improving the user experience.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a page control method, device, equipment and storage medium. Background Art

[0002] Currently, for various web browsers on computers, mobile phones, etc., it will be found that the data displayed on their list pages is very limited, and users need to frequently click "View Details Page" or modify the "Edit Page" content to view the complete content.

[0003] In this regard, the existing technology uses iframes to display detail pages or edit pages within list pages. Specifically, iframe is a Hypertext Markup Language (HTML) tag, and through iframe, it is possible to display another web page (hereinafter referred to as an embedded page) within the original container page.

[0004] However, due to iframe security requirements, an iframe-based embedded page is actually an independent browser window relative to the container page. Rules for window size, page elements, and other aspects have been pre-defined, and page rendering is directly based on these rules, independent of the container page. Due to this characteristic of iframes, when used for embedded page display, there are at least the following problems:

[0005] 1) The container page and the embedded page each load resources based on their own preset rules, so the same resources in them will be loaded repeatedly, thereby extending the time it takes to complete resource loading.

[0006] 2) The embedded page is displayed in the container page but is not controlled by the container page. As a result, the forward and backward movements of the container page itself require calculations of the embedded page (for example, the iframe embedded page must be moved backward before the container page can be moved backward). As a result, the forward and backward functions of the container page do not meet expectations.

[0007] 3) According to the rules, the content embedded in the page cannot exceed the iframe container, so pop-up prompts cannot be displayed in full screen, affecting the user experience.

[0008] Based on this, it is necessary to study new display solutions for embedded pages. Summary of the Invention

[0009] The purpose of the embodiments of the present invention is to provide a page control method, apparatus, device and storage medium, which are used to at least partially solve the above technical problems.

[0010] In order to achieve the above-mentioned purpose, an embodiment of the present invention provides a page control method for a page structure including a container and a drawer, and the page control method includes: obtaining a routing list showing the mapping relationship between all relevant page uniform resource locators (URLs) and their corresponding page component addresses; in response to a user's operation on a jump component in a container page, obtaining the page URL corresponding to the jump component, and matching the page component address corresponding to the page URL from the routing list; and obtaining the page component indicated by the matched page component address, and rendering the corresponding embedded page in the drawer through the page component.

[0011] Preferably, the routing list is configured to be: pre-stored in a code format; or pre-stored in a database.

[0012] Preferably, before obtaining the page URL corresponding to the jump component, the page control method also includes: obtaining an indication parameter in the jump component, wherein the indication parameter is pre-configured in the jump component and is used to indicate the display method of the embedded page after the jump, wherein the display method includes displaying it as a new page or displaying it in the drawer; and when the indication parameter indicates displaying it in the drawer, performing the acquisition of the page URL corresponding to the jump component.

[0013] Preferably, after rendering the corresponding embedded page in the drawer through the page component, the page control method further includes: on the container side, controlling the container page to inject an identifier into the embedded page, the identifier being used to indicate that the container page and the embedded page can communicate.

[0014] Preferably, the container page and the embedded page communicate with each other through any one of the following: defining a function in the container page so that the embedded page communicates with the container page through function calls; and configuring an event in the container page so that the embedded page communicates with the container page by triggering an event.

[0015] Preferably, the page control method also includes: at the drawer end, in response to the embedded page detecting the identifier, controlling the embedded page to notify the container page of the user's operation information for the embedded page; and at the container end, in response to the operation information, controlling the embedded page to perform an action corresponding to the operation information.

[0016] Preferably, when the embedded page does not detect the identifier, the page control method further comprises: controlling the embedded page to open as a new page.

[0017] Preferably, controlling the embedded page to perform an action corresponding to the operation information includes: controlling the container page to write path information of the action of the embedded page adapted to the operation information at different times in a preset history record list; and in response to the current operation information, querying the history record list to provide the embedded page with path information about the action corresponding to the operation information.

[0018] Preferably, the page control method further comprises: when acquiring a page URL of another jump component in the container page in anticipation of rendering an embedded page in a new drawer, clearing the history record list.

[0019] On the other hand, the present invention also provides a page control device for a page structure including a container and a drawer, and the page control device includes: a routing list acquisition module, used to obtain a routing list showing the mapping relationship between all relevant page uniform resource locators (URLs) and their corresponding page component addresses; an address matching module, used to respond to the user's operation on the jump component in the container page, obtain the page URL corresponding to the jump component, and match the page component address corresponding to the page URL from the routing list; and a page rendering module, used to obtain the page component indicated by the matched page component address, and render the corresponding embedded page in the drawer through the page component.

[0020] Preferably, the page control device also includes: an identifier injection module, which is used to control the container page to inject an identifier into the embedded page at the container end, and the identifier is used to indicate that the container page and the embedded page can communicate; a notification module, which is used to control the embedded page to notify the container page of the user's operation information for the embedded page in response to the embedded page detecting the identifier at the drawer end; and a management module, which is used to control the embedded page to perform an action corresponding to the operation information in response to the operation information at the container end.

[0021] On the other hand, the present invention further provides a machine-readable storage medium having stored thereon instructions for enabling a machine to execute any of the above-mentioned page control methods of the present application.

[0022] On the other hand, the present invention also provides a page control device, comprising: one or more processors; a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement any of the above-mentioned page control methods.

[0023] Through the above technical solution, the solution of the present invention maintains the mapping relationship between the full page URL and the page component address to obtain the corresponding page component through the page URL to render the embedded page in the drawer, so that the resource loading of the embedded page is no longer based on preset rules like iframe, avoiding the repeated loading of the same resources in the container page and the embedded page, shortening the resource loading completion time, and improving the user experience.

[0024] Other features and advantages of the embodiments of the present invention will be described in detail in the subsequent detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The accompanying drawings are used to provide a further understanding of the embodiments of the present invention and constitute a part of the specification. Together with the following detailed description, they are used to explain the embodiments of the present invention, but do not constitute a limitation of the embodiments of the present invention. In the accompanying drawings:

[0026] Figure 1 is a flow chart of a page control method according to an embodiment of the present invention;

[0027] Figure 2 This is an example diagram of an embedded page implemented by the page control method according to an embodiment of the present invention;

[0028] Figure 3 1 is a flow chart of a page control method according to a preferred embodiment of the present invention;

[0029] Figure 4 is a structural diagram of a page control device according to another embodiment of the present invention; and

[0030] Figure 5 It is a structural diagram of a page control device according to another embodiment of the present invention.

[0031] Description of Reference Numerals

[0032] 10. Container; 20. Drawer; 30. Forward label; 40. Back label; 50. Refresh label;

[0033] 401. Route list acquisition module; 402. Address matching module; 403. Page rendering module; 404. Identity injection module; 405. Notification module; 406. Management module. DETAILED DESCRIPTION

[0034] The following describes the specific implementation of the embodiment of the present invention in detail with reference to the accompanying drawings. It should be understood that the specific implementation described herein is only used to illustrate and explain the embodiment of the present invention and is not used to limit the embodiment of the present invention.

[0035] Figure 1FIG is a flow chart of a page control method according to an embodiment of the present invention, wherein the method is directed to a page structure including a container and a drawer. Figure 1 As shown, the page control method may include the following steps S110 to S130:

[0036] Step S110 : obtaining a routing list showing mapping relationships between all relevant page Uniform Resource Locators (URLs) and their corresponding page component addresses.

[0037] The page component address is used to indicate the address of the page component for rendering the embedded page in the drawer, so as to implement the calling of the page component.

[0038] The routing list requires the maintenance of a full set of routing data, including all relevant page URLs and the page component addresses corresponding to each page URL. For example, a set of mapping relationships shown in the routing list can be described as follows:

[0039] [{

[0040] path: ' / help / detail',

[0041] component: ' / help / detail.vue'

[0042] }]

[0043] Among them, path refers to the page URL; component is the corresponding page component address, which indicates the JS / CSS / HTML content required to render this page.

[0044] In a preferred embodiment, the routing list is configured to be pre-stored in code or in a database. Accordingly, step S110 can retrieve the mapping relationship between the page URL and the page component address shown in the routing list by calling the code or querying the database. It should be noted that the routing list is not limited to these two storage methods and can also be stored in other ways.

[0045] Step S120 , in response to the user's operation on the jump component in the container page, obtain the page URL corresponding to the jump component, and match the page component address corresponding to the page URL from the routing list.

[0046] For example, a user clicks on a jump component. Alternatively, the jump component can be configured as a link. However, in a preferred embodiment, a link directly opens a new page, while a separate jump component indicates that an embedded page will be displayed in a drawer. In this embodiment of the present invention, the new page refers to a page that is independent of the container page and is not displayed in a drawer.

[0047] Based on the above considerations of opening a new page or opening a drawer, in a preferred embodiment, the page control method further includes: obtaining an indication parameter in the jump component, wherein the indication parameter is pre-configured in the jump component and is used to indicate the display method of the embedded page after the jump, wherein the display method includes displaying it as a new page or displaying it in the drawer; and when the indication parameter indicates displaying it in the drawer, performing acquisition of the page URL corresponding to the jump component.

[0048] That is, by embedding an indication parameter in the jump component, it is determined whether there is a need to open a new page. For example, the jump component is configured with an indication parameter, which can help determine whether the jump component opens a new page or opens a drawer. If the drawer is opened, the default method of opening a new page is blocked and the drawer is called up. Otherwise, the new page is opened. Based on this, for some embedded pages that are not suitable for drawer display (for example, for security reasons, the embedded page is required to be completely independent of the container page) or some embedded pages that require to be opened on a new page and cannot be displayed in the drawer, they can still be jumped to the new page for display as a link.

[0049] Step S130: Acquire the page component indicated by the matched page component address, and render the corresponding embedded page in the drawer through the page component.

[0050] Among them, rendering the corresponding page through the page component is easy to implement for those skilled in the art, and is not the main focus of the embodiments of the present invention, so it will not be described here in detail.

[0051] For step S130, Figure 2 This is an example diagram of displaying embedded pages implemented by the page control method according to an embodiment of the present invention, wherein page A and page B are respectively a container page displayed in the container 10 and an embedded page displayed in the drawer 20 .

[0052] Combine Figure 2From the results shown, it can be seen that the page control method of the embodiment of the present invention maintains a mapping relationship between the full page URL and the page component address, and can use the page URL to obtain the corresponding page component to render the embedded page in the drawer. As a result, the resource loading of the embedded page is no longer based on preset rules like iframe, avoiding the repeated loading of the same resources in the container page and the embedded page, and shortening the time it takes to complete resource loading. In addition, in the drawer display, the content of the embedded page can exceed the drawer, and pop-up prompts can be displayed full-screen, improving the user experience.

[0053] However, continue to refer to Figure 2 The drawer is also equipped with a page forward label 30, a page back label 40 and a page refresh label 50 (other function labels can also be configured). In order to ensure the efficient use of these function labels, the preferred embodiment of the present invention proposes a method of Figure 1 Based on the steps above, we further establish the interaction scheme between the container page and the embedded page. Specifically, Figure 3 This is a flow chart of a page control method according to a preferred embodiment of the present invention. Figure 1 Based on steps S110-S130, the following steps are further included:

[0054] Step S140: On the container side, control the container page to inject a logo into the embedded page.

[0055] The identifier is used to indicate that the container page and the embedded page can communicate with each other.

[0056] For example, in step S140, for an embedded page, whether the page has the above-mentioned mark is used to determine whether the current embedded page is in a drawer. If there is no such mark, a new page (such as a new browser page) is opened normally. If there is such mark, the container page is notified through a predetermined method.

[0057] Preferably, the communication between the container page and the embedded page can be achieved in an agreed manner, and the agreed manner is, for example, any one of the following: defining a function in the container page so that the embedded page communicates with the container page through a function call; and configuring an event in the container page so that the embedded page communicates with the container page by triggering an event.

[0058] For example, a "convention" can be implemented as a global function, such as window.openInnerPage, or a global event, such as the 'openInnerPage' event on window. If it's a global function, the container page defines the function and the embedded page calls it. If it's a global event, the container page listens for the event and the embedded page triggers it.

[0059] Through the identification and agreement in step S140, the container page and the embedded page in the drawer can communicate with each other, so that the container page can manage the functions corresponding to the function tags on the embedded page.

[0060] Based on this, in a more preferred embodiment, the page control method further includes the following steps S150 and S160:

[0061] Step S150: At the drawer end, in response to the embedded page detecting the identifier, controlling the embedded page to notify the container page of the user's operation information on the embedded page.

[0062] For example, refer to Figure 2 , the user clicks the forward tag 30 of the embedded page in the drawer, and the embedded page notifies the container page of the operation information corresponding to the click operation, so as to apply to the container page for executing the page forward operation.

[0063] It should be noted that if the embedded page does not detect the identifier, the page control method may further include: controlling the embedded page to open as a new page. That is, if the embodiment of the present invention finds that the embedded page and the container page have not successfully established a communication relationship, the embedded page is opened as a new page.

[0064] Step S160: On the container side, in response to the operation information, control the embedded page to perform an action corresponding to the operation information.

[0065] Continuing with the above example of the forward tag 30 , after receiving the operation information sent by the embedded page, the container page controls the embedded page to perform a page forward operation to reach the next page in the drawer.

[0066] For step S160, in a preferred embodiment, controlling the embedded page to perform an action corresponding to the operation information includes: controlling the container page to write path information of the action of the embedded page adapted to the operation information at different times in a preset history record list; and in response to the current operation information, querying the history record list to provide the embedded page with path information about the action corresponding to the operation information.

[0067] For example, the container page will save a history list. When the embedded page tells the container page to jump to another page in the drawer through an agreed method, the container page will write the path of the current embedded page into this history list. Based on this, when the back tab 40 of the embedded page is currently clicked, the path information of the previous page of the current page can be queried using the history list to realize the back function of the back tab 40.

[0068] However, if the history list stores too much path information, it will inevitably affect the page jump speed and bring a poor user experience. In this regard, in a more preferred embodiment, the page control method further includes: when obtaining the page URL of another jump component in the container page in anticipation of rendering the embedded page in a new drawer, clearing the history list.

[0069] For example, if the drawer currently displays embedded page B1, corresponding to jump component B1, the container page currently stores a history list containing the content of embedded page B1. When the user clicks jump component B2 again to display embedded page B2 in the drawer, the container page, in response to obtaining the page URL corresponding to embedded page B2, clears the history list, allowing it to be reused to record the path information for embedded page B2. In other words, the history list is cleared when the container page triggers a new drawer, thus avoiding the problem of the embedded page responding slowly when moving forward or backward due to an excessive amount of content in the history list.

[0070] In summary, in a preferred embodiment of the present invention, the container page can communicate with the embedded page and manage the jump (or navigation) between the embedded pages. During this management process, when the container page moves forward or backward, it does not need to calculate the embedded page, thereby making the "forward, back" and other functions of the container page more in line with expectations.

[0071] Figure 4 FIG. 1 is a structural diagram of a page control device according to another embodiment of the present invention. The page control device and the page control method according to the above embodiment are based on the same inventive concept. Figure 4 As shown, the page control device may include: a routing list acquisition module 401, used to obtain a routing list showing the mapping relationship between all relevant page URLs and their corresponding page component addresses; an address matching module 402, used to respond to the user's operation on the jump component in the container page, obtain the page URL corresponding to the jump component, and match the page component address corresponding to the page URL from the routing list; and a page rendering module 403, used to obtain the page component indicated by the matched page component address, and render the corresponding embedded page in the drawer through the page component.

[0072] In a preferred embodiment, the page control device also includes: an identifier injection module 404, which is used to control the container page to inject an identifier into the embedded page at the container end, and the identifier is used to indicate that the container page and the embedded page can communicate in an agreed manner; a notification module 405, which is used to control the embedded page to notify the container page of the user's operation information for the embedded page in response to the embedded page detecting the identifier at the drawer end; and a management module 406, which is used to control the embedded page to perform an action corresponding to the operation information in response to the operation information at the container end.

[0073] It should be noted that for more implementation details and effects of the page control device of the embodiment of the present invention, reference may be made to the page control method of the above embodiment, which will not be described in detail here.

[0074] Figure 5 is a schematic diagram of the structure of a page control device according to another embodiment of the present invention. The page control device may include: one or more processors; and a memory for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the page control method described above. It should be noted that the page control device is, for example, a computer.

[0075] Another embodiment of the present invention further provides a machine-readable storage medium, on which instructions are stored, and the instructions are used to enable a machine to execute the page control method described above.

[0076] The page control method in the computer device and the machine-readable storage medium can be understood by referring to the above embodiments, which will not be described in detail here. The following mainly introduces the computer device and the machine-readable storage medium in combination with application scenarios.

[0077] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, apparatuses (devices or systems), or computer program products. Thus, embodiments of the present invention may take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware. Furthermore, embodiments of the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROMs, optical storage, etc.) containing computer-usable program code.

[0078] The present invention is described with reference to flowcharts and / or block diagrams of methods, apparatus (devices or systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowcharts and / or block diagrams, as well as combinations of processes and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowcharts and / or block diagrams. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0079] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0080] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0081] In a typical configuration, a computer device includes one or more processors (CPU), storage, input / output interfaces, network interfaces, and memory.

[0082] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0083] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can be implemented using any method or technology to store information. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change RAM (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media such as modulated data signals and carrier waves.

[0084] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0085] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Thus, embodiments of the present invention may take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects. Furthermore, embodiments of the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROMs, optical storage, etc.) containing computer-usable program code.

[0086] The above describes in detail the optional implementation methods of the embodiments of the present invention in conjunction with the accompanying drawings. However, the embodiments of the present invention are not limited to the specific details in the above implementation methods. Within the technical concept of the embodiments of the present invention, various simple modifications can be made to the technical solutions of the embodiments of the present invention, such as changing the order of execution of the steps. These simple modifications all fall within the scope of protection of the embodiments of the present invention.

[0087] It should also be noted that the various specific technical features described in the above specific embodiments can be combined in any appropriate manner without contradiction. To avoid unnecessary repetition, the embodiments of the present invention will not further describe various possible combinations.

[0088] In addition, various implementations of the embodiments of the present invention may be arbitrarily combined, and as long as they do not violate the concept of the embodiments of the present invention, they should also be regarded as the contents disclosed in the embodiments of the present invention.

Claims

1. A page control method, characterized in that: For a page structure including a container and a drawer, the page control method includes: Obtain a routing list showing mapping relationships between all relevant page uniform resource locators (URLs) and their corresponding page component addresses; In response to a user operation on a jump component in a container page, obtaining a page URL corresponding to the jump component, and matching a page component address corresponding to the page URL from the routing list; and Obtain the page component indicated by the matched page component address, and render the corresponding embedded page in the drawer through the page component; Before obtaining the page URL corresponding to the jump component, the page control method further includes: Obtaining an indication parameter in the jump component, wherein the indication parameter is pre-configured in the jump component and is used to indicate a display method of the embedded page after the jump, wherein the display method includes displaying it as a new page or displaying it in the drawer; and When the indication parameter indicates that the component is displayed in the drawer, obtaining the URL of the page corresponding to the jump component is executed; After rendering the corresponding embedded page in the drawer through the page component, the page control method further includes: On the container side, controlling the container page to inject an identifier into the embedded page, where the identifier is used to indicate that the container page and the embedded page can communicate; The page control method further includes: At the drawer side, in response to the embedded page detecting the identifier, controlling the embedded page to notify the container page of user operation information on the embedded page; and On the container side, in response to the operation information, the embedded page is controlled to perform an action corresponding to the operation information.

2. The page control method according to claim 1, wherein: The route list is configured as follows: Pre-stored in code; or Pre-stored in the database.

3. The page control method according to claim 1, wherein: The container page and the embedded page communicate with each other through any one of the following: defining a function in the container page so that the embedded page communicates with the container page through function calls; and Events are configured in the container page so that the embedded page communicates with the container page by triggering events.

4. The page control method according to claim 1, wherein: When the embedded page does not detect the identifier, the page control method further includes: Control the embedded page to open as a new page.

5. The page control method according to claim 1, wherein: The controlling the embedded page to execute an action corresponding to the operation information includes: Controlling the container page to write path information of actions of the embedded page adapted to the operation information at different times into a preset history record list; and In response to the current operation information, the history record list is queried to provide the embedded page with path information about the action corresponding to the operation information.

6. The page control method according to claim 5, characterized in that: The page control method further includes: When the page URL of another jump component in the container page is obtained in anticipation of rendering an embedded page in a new drawer, the history list is cleared.

7. A page control device, characterized in that: For a page structure including a container and a drawer, the page control device includes: A routing list acquisition module is used to acquire a routing list showing the mapping relationship between all relevant page uniform resource locators (URLs) and their corresponding page component addresses; An address matching module is configured to, in response to a user's operation on a jump component in a container page, obtain a page URL corresponding to the jump component and match a page component address corresponding to the page URL from the routing list; and A page rendering module is used to obtain the page component indicated by the matched page component address, and render the corresponding embedded page in the drawer through the page component; The page control device further includes obtaining an indication parameter in the jump component before obtaining the page URL corresponding to the jump component, wherein the indication parameter is pre-configured in the jump component and is used to indicate a display method of the embedded page after the jump, wherein the display method includes displaying it as a new page or displaying it in the drawer; and when the indication parameter indicates displaying it in the drawer, executing the acquisition of the page URL corresponding to the jump component; The page control device also includes: An identifier injection module, configured to control the container page to inject an identifier into the embedded page at the container end, the identifier being used to indicate that the container page and the embedded page are capable of communicating; a notification module configured to, at the drawer end, control the embedded page to notify the container page of user operation information on the embedded page in response to the embedded page detecting the identifier; and The management module is used to control the embedded page to perform an action corresponding to the operation information in response to the operation information at the container end.

8. A machine-readable storage medium having instructions stored thereon, wherein the instructions are used to enable a machine to execute the page control method according to any one of claims 1 to 6.

9. A page control device, characterized in that: include: one or more processors; a memory for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the page control method according to any one of claims 1 to 6.

Images