Page processing method and device, equipment and storage medium

Abstract

The invention provides a page processing method and device, equipment and a storage medium, and the method comprises the steps: responding to a page rendering result for a to-be-rendered object, calling a white screen anomaly detection module to detect the page rendering result, and obtaining a white screen anomaly detection result, and if the white screen anomaly detection result indicates that the white screen anomaly occurs in the page rendering result, calling a front-end attribution detection module to detect an attribution event of the white screen anomaly, and after the attribution event of the white screen anomaly is detected, processing the white screen anomaly based on the attribution event, and updating the page rendering result of the to-be-rendered object. According to the embodiment of the invention, under the condition that the white screen exception occurs in the page rendering result in the cross-end scene, the front-end attribution detection module is called to perform attribution detection on the white screen exception, and the white screen exception is processed according to the detected attribution event, so that the page rendering result with the white screen exception is updated; the probability of displaying the white screen page to the user in the cross-end scene is reduced, and the user experience is improved.

Description

Technical Field

[0001] This disclosure relates to the field of data processing, and more particularly to a page processing method, apparatus, device, and storage medium. Background Technology

[0002] A white screen error refers to a situation where a webpage displays a blank page for a specified period of time, without any content. White screen errors can be caused by various reasons, such as rendering function errors, empty route pages, slow page loading leading to a lack of content for the designated time. Monitoring for white screen errors can help identify and promptly fix bugs in your application.

[0003] Cross-platform applications refer to applications that span both the front-end and client sides, meaning they are applications implemented through interaction and collaboration between front-end and client-side code. Currently, if a white screen error occurs in a cross-platform application, an error report is generated after detection so that the error can be handled subsequently. However, for the current page display, the page showing the error will still be displayed to the user, thus affecting the user's browsing experience.

[0004] Therefore, how to solve the white screen error problem and improve the user's page browsing experience is a technical problem that urgently needs to be solved. Summary of the Invention

[0005] To address the aforementioned technical problems, this disclosure provides a page processing method, apparatus, device, and storage medium.

[0006] In a first aspect, this disclosure provides a page processing method, the method comprising:

[0007] In response to the page rendering result of the object to be rendered, the white screen anomaly detection module is invoked to detect the page rendering result and obtain the white screen anomaly detection result; wherein, the page rendering result of the object to be rendered is rendered by the front-end rendering module;

[0008] If the white screen anomaly detection result indicates that a white screen anomaly has occurred in the page rendering result, the front-end attribution detection module is called to detect the attribution event of the white screen anomaly. After detecting the attribution event of the white screen anomaly, the white screen anomaly is processed based on the attribution event, and the page rendering result of the object to be rendered is updated.

[0009] In one optional implementation, the method further includes:

[0010] If the front-end attribution detection module does not detect the attribution event for the white screen anomaly, a re-rendering instruction is sent to the client loading module, instructing the client loading module to trigger a re-rendering for the object to be rendered.

[0011] In one optional implementation, before calling the white screen anomaly detection module to detect the page rendering result in response to the page rendering result of the object to be rendered, and before obtaining the white screen anomaly detection result, the method further includes:

[0012] In response to a rendering request for the object to be rendered, the resource data and context information of the object to be rendered are obtained, the resource data is injected into the front-end rendering module, and the front-end rendering module is called to render the object to be rendered to obtain the page rendering result;

[0013] In addition, the resource data and context information of the object to be rendered are stored;

[0014] Accordingly, after sending a re-rendering instruction to the client loading module, instructing the client loading module to trigger a re-rendering for the object to be rendered, the process further includes:

[0015] The client loading module is invoked to trigger a re-rendering of the object to be rendered based on the stored resource data and context information of the object to be rendered.

[0016] In one optional implementation, after detecting the attribution event of the white screen anomaly, processing the white screen anomaly based on the attribution event and updating the page rendering result of the object to be rendered includes:

[0017] If the detected white screen anomaly is attributed to a rendering data anomaly, a rendering data request is sent to the object to be rendered to obtain the latest rendering data of the object to be rendered.

[0018] Based on the latest rendering data, a re-render is triggered for the object to be rendered, a re-render result is obtained, and the page rendering result of the object to be rendered is updated using the re-render result.

[0019] In one optional implementation, the object to be rendered includes a page and / or a resource card, and the object to be rendered is generated based on front-end code.

[0020] In one optional implementation, if the white screen anomaly detection result indicates that a white screen anomaly has occurred in the page rendering result, then the front-end attribution detection module is invoked to detect the attribution event of the white screen anomaly, including:

[0021] If the white screen anomaly detection result indicates that the page rendering result has a white screen anomaly, then determine whether the white screen anomaly detection for the object to be rendered has reached a preset number of consecutive times;

[0022] If it is determined that the number of consecutive preset number of white screen anomaly detections for the object to be rendered has not been reached, the front-end attribution detection module is invoked to detect the attribution event of the white screen anomaly.

[0023] In one optional implementation, the method further includes:

[0024] If it is determined that the white screen anomaly detection for the object to be rendered has reached a preset number of consecutive times, a preset prompt page is displayed for the object to be rendered; wherein, the preset prompt page is used to indicate that a rendering anomaly has occurred for the object to be rendered.

[0025] Secondly, this disclosure provides a page processing apparatus, the apparatus comprising:

[0026] The calling module is used to call the white screen anomaly detection module to detect the page rendering result for the object to be rendered in response to the page rendering result, and obtain the white screen anomaly detection result; wherein, the page rendering result of the object to be rendered is rendered by the front-end rendering module;

[0027] The update module is used to call the front-end attribution detection module to detect the attribution event of the white screen anomaly when the white screen anomaly detection result indicates that a white screen anomaly has occurred in the page rendering result. After detecting the attribution event of the white screen anomaly, the module processes the white screen anomaly based on the attribution event and updates the page rendering result of the object to be rendered.

[0028] Thirdly, this disclosure provides a computer-readable storage medium storing instructions that, when executed on a terminal device, cause the terminal device to implement the above-described method.

[0029] Fourthly, this disclosure provides a page processing device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the above-described method.

[0030] Fifthly, this disclosure provides a computer program product comprising a computer program / instruction that, when executed by a processor, implements the method described above.

[0031] The technical solution provided in this disclosure has at least the following advantages compared with the prior art:

[0032] This disclosure provides a page processing method. First, in response to the page rendering result of the object to be rendered, a white screen anomaly detection module is invoked to detect the page rendering result and obtain a white screen anomaly detection result. The page rendering result of the object to be rendered is obtained by the front-end rendering module. Then, if the white screen anomaly detection result indicates that a white screen anomaly has occurred in the page rendering result, the front-end attribution detection module is invoked to detect the attribution event of the white screen anomaly. After detecting the attribution event of the white screen anomaly, the white screen anomaly is processed based on the attribution event, and the page rendering result of the object to be rendered is updated.

[0033] This embodiment of the present disclosure can detect white screen errors in cross-platform scenarios by calling the front-end attribution detection module, and process the white screen errors according to the detected attribution events, so as to update the page rendering results of the white screen error, reduce the probability of displaying a white screen page to users in cross-platform scenarios, and thus improve the user experience. Attached Figure Description

[0034] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0035] To more clearly illustrate the technical solutions in the embodiments of this disclosure or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0036] Figure 1 A flowchart illustrating a page processing method provided in this embodiment of the disclosure;

[0037] Figure 2 A data interaction diagram of a page processing method provided in this embodiment of the disclosure;

[0038] Figure 3 This is a schematic diagram of the structure of a page processing apparatus provided in an embodiment of the present disclosure;

[0039] Figure 4 This is a schematic diagram of the structure of a page processing device provided in an embodiment of the present disclosure. Detailed Implementation

[0040] To better understand the above-mentioned objectives, features, and advantages of this disclosure, the solutions disclosed herein will be further described below. It should be noted that, unless otherwise specified, the embodiments and features described herein can be combined with each other.

[0041] Numerous specific details are set forth in the following description in order to provide a full understanding of this disclosure, but this disclosure may also be implemented in other ways different from those described herein; obviously, the embodiments in the specification are only some, and not all, of the embodiments of this disclosure.

[0042] White screen detection refers to the process of detecting the display status of an application or webpage to determine whether a white screen anomaly occurs. This is used to discover and resolve white screen problems that may lead to a poor user experience, ensuring that the application or webpage can display content normally and improving the user experience.

[0043] In cross-platform applications, when a rendering request for an object to be rendered is received, if the loading time of the object to be rendered is too long or the object to be rendered fails to load correctly for some reason, a white screen will appear, affecting the user experience.

[0044] Therefore, how to solve the white screen anomaly and improve the user experience is a technical problem that urgently needs to be solved.

[0045] To address this, this disclosure provides a page processing method. First, in response to the page rendering result of the object to be rendered, a white screen anomaly detection module is invoked to detect the page rendering result and obtain a white screen anomaly detection result. The page rendering result of the object to be rendered is obtained by the front-end rendering module. Then, if the white screen anomaly detection result indicates that a white screen anomaly has occurred in the page rendering result, the front-end attribution detection module is invoked to detect the attribution event of the white screen anomaly. After detecting the attribution event of the white screen anomaly, the white screen anomaly is processed based on the attribution event, and the page rendering result of the object to be rendered is updated.

[0046] This embodiment of the present disclosure can detect white screen errors in cross-platform scenarios by calling the front-end attribution detection module, and process the white screen errors according to the detected attribution events, so as to update the page rendering results of the white screen error, reduce the probability of displaying a white screen page to users in cross-platform scenarios, and thus improve the user experience.

[0047] Based on this, the present disclosure provides a page processing method, referring to... Figure 1 The flowchart below illustrates a page processing method provided in this embodiment of the present disclosure. The method specifically includes:

[0048] S101: In response to the page rendering result of the object to be rendered, the white screen anomaly detection module is called to detect the page rendering result and obtain the white screen anomaly detection result.

[0049] The page rendering result of the object to be rendered is obtained by the front-end rendering module.

[0050] The page processing method provided in this disclosure is applied to cross-platform applications, which are applications implemented based on client-side and front-end technologies. Typically, the display of content such as pages and resource cards in cross-platform applications is implemented based on front-end technologies, while other logical content is implemented based on client-side technologies. Cross-platform applications need to implement communication between the front-end and client-side components.

[0051] In this embodiment of the disclosure, the object to be rendered can refer to the object that needs to be rendered and displayed, such as a page or resource card. The object to be rendered can be generated based on front-end code, such as a page or resource card generated based on JavaScript code. Resource cards are used to display various resource data; specifically, resource cards can display resource data such as images, text, and videos.

[0052] In one optional implementation, when the client loading module receives a rendering request for the object to be rendered, it obtains the resource data and context information of the object to be rendered, injects the obtained resource data into the front-end rendering module, calls the front-end rendering module to render the object to be rendered, and after the rendering processing of the front-end rendering module, the page rendering result is obtained and presented to the user.

[0053] When the front-end rendering module completes the rendering of the object to be rendered and obtains the page rendering result, it displays the object to be rendered and calls the white screen anomaly detection module to detect the page rendering result and obtain the white screen anomaly detection result of the page rendering result.

[0054] The page rendering result of the object to be rendered can refer to the display view of the object to be rendered.

[0055] The white screen anomaly detection module in this embodiment is used to detect white screens on the received page rendering results. This white screen anomaly detection module can be deployed on the client side and is usually implemented based on client-side code. The white screen anomaly detection module can be a tool for detecting and diagnosing white screen occurrences on a page. Specifically, this embodiment does not limit the implementation method of the white screen anomaly detection module.

[0056] The white screen anomaly detection module may include testing the visibility and responsiveness of elements in the page rendering result of the object to be rendered. There are many ways for the white screen anomaly detection module to perform white screen anomaly detection on the page rendering result, and this disclosure does not impose any limitations. In one optional implementation, pixel information on the page rendering result is analyzed using image processing technology. If the proportion of white pixels exceeds a certain threshold, it is determined that the page rendering result of the object to be rendered has a white screen anomaly, and a white screen anomaly detection result indicating that the page rendering result has a white screen anomaly is output. Otherwise, a white screen anomaly detection result indicating that the page rendering result has not a white screen anomaly is output.

[0057] In other words, the white screen anomaly detection results of the page rendering results can indicate whether a white screen anomaly has occurred in the page rendering result of the object to be rendered.

[0058] S102: If the white screen anomaly detection result indicates that the page rendering result has a white screen anomaly, then the front-end attribution detection module is called to detect the attribution event of the white screen anomaly, and after detecting the attribution event of the white screen anomaly, the white screen anomaly is processed based on the attribution event, and the page rendering result of the object to be rendered is updated.

[0059] In this embodiment of the disclosure, when the white screen anomaly detection module determines that the white screen anomaly detection result of the page rendering result indicates that the page rendering result has a white screen anomaly, the white screen anomaly detection module sends the white screen anomaly detection result to the front-end attribution detection module, which then performs white screen anomaly detection, specifically detecting the attribution event of the white screen anomaly occurring in the object to be rendered.

[0060] The front-end attribution detection module, generated from front-end code, is specifically used to analyze the page rendering results of the object to be rendered to determine whether the cause of the white screen anomaly lies in the front end; that is, to analyze whether a front-end issue is causing the white screen anomaly. Furthermore, after determining that a front-end issue is causing the white screen anomaly, the front-end attribution detection module can also determine the specific reasons why the front end is causing the white screen anomaly.

[0061] The front-end attribution detection module can detect and analyze the rendering data and rendering logic code of the object to be rendered to determine whether the resource data used for rendering the object is missing, whether the rendering logic code is incorrect, etc., and thus determine the attribution event for the white screen exception of the object to be rendered. After the front-end attribution detection module detects and analyzes the rendering data and rendering logic code of the object to be rendered on the front end, if the attribution event for the white screen exception of the object to be rendered is determined, the white screen exception is handled on the front end based on the attribution event. After the handling is completed, the page rendering result of the object to be rendered is updated to overcome the page white screen exception.

[0062] Among them, the attribution event is the event that causes the white screen error of the object to be rendered, as determined by the front-end attribution detection module. The attribution event can include the loss of resource data of the object to be rendered, syntax errors or logic errors in the processing logic code, etc. Based on the attribution event of the white screen error of the object to be rendered, the front-end handles the white screen error and updates the page rendering result of the object to be rendered. Specifically, it can take corresponding solutions for the attribution event, re-render the page of the object to be rendered, and then display the page based on the re-rendered page rendering result to overcome the white screen error.

[0063] In one application scenario, if the front-end attribution detection module detects that the cause of the white screen anomaly is a rendering data anomaly, it sends a rendering data request to the object to be rendered to obtain the latest rendering data for that object. Specifically, sending a rendering data request to the source of the rendering data for the object to be rendered can be done by sending the request to that source.

[0064] Based on the latest rendering data of the object to be rendered, the object is re-rendered to obtain the re-rendering result. Then, the page rendering result of the object to be rendered is updated using the re-rendering result, and the page is displayed based on the page rendering result.

[0065] In practical applications, if the white screen anomaly detection result indicates that no white screen anomaly has occurred in the page rendering result, there is no need to re-render the object to be rendered. Instead, the object to be rendered is displayed based on the page rendering result, and page interaction operations of the object to be rendered are handled.

[0066] The page processing method provided in this embodiment firstly calls a white screen anomaly detection module to detect the page rendering result in response to the page rendering result of the object to be rendered, and obtains a white screen anomaly detection result. The page rendering result of the object to be rendered is rendered by the front-end rendering module. Then, if the white screen anomaly detection result indicates that a white screen anomaly has occurred in the page rendering result, the front-end attribution detection module is called to detect the attribution event of the white screen anomaly. After detecting the attribution event of the white screen anomaly, the white screen anomaly is processed based on the attribution event, and the page rendering result of the object to be rendered is updated.

[0067] This embodiment of the present disclosure can detect white screen errors in cross-platform scenarios by calling the front-end attribution detection module, and process the white screen errors according to the detected attribution events, so as to update the page rendering results of the white screen error, reduce the probability of displaying a white screen page to users in cross-platform scenarios, and thus improve the user experience.

[0068] In one optional implementation, after detecting the page rendering result for the object to be rendered, the white screen anomaly detection module is called to detect the page rendering result and obtain the white screen anomaly detection result. If the white screen anomaly detection result indicates that the page rendering result has a white screen anomaly, the white screen anomaly detection module sends the white screen anomaly detection result to the front-end attribution detection module and calls the front-end attribution detection module to detect the attribution event of the white screen anomaly.

[0069] If the front-end attribution detection module does not detect an attribution event for the white screen exception, a re-rendering instruction is sent to the client loading module, instructing the client loading module to trigger a re-render for the object to be rendered.

[0070] If the front-end attribution detection module fails to detect the attribution event for the white screen exception, it means that the module did not detect the event causing the exception in the front-end. In other words, the white screen exception is not caused by the front-end. This implies that the attribution event causing the white screen exception most likely occurred on the client-side. Therefore, after the front-end attribution detection module fails to detect the event, the front-end sends a re-rendering instruction to the client-side loading module, instructing it to handle the white screen exception. Specifically, it instructs the client-side loading module to re-render the object to be rendered to overcome the white screen exception.

[0071] The front-end sends a re-rendering command to the client-side loading module to trigger a re-rendering of objects that are experiencing a white screen error. Upon receiving the re-rendering command from the front-end for the object to be rendered, the client-side loading module initiates the re-rendering process for that object.

[0072] In practical applications, in order for the client loading module to trigger a re-rendering process for the object to be rendered, this embodiment of the present disclosure also requires storing the resource data and context information of the object to be rendered after loading the resource data of the object to be rendered, so that the client loading module can trigger a re-rendering process for the object to be rendered based on the stored resource data and context information of the object to be rendered.

[0073] Among them, the resource data of the object to be rendered is the data required by the object to be rendered during the rendering process.

[0074] The context information of the object to be rendered can include information related to the object. Specifically, the context information can include parameter information when rendering the object, such as page load time and card load time.

[0075] In practical applications, when a rendering request for an object to be rendered is received, the resource data and context information of the object to be rendered are obtained, the resource data is injected into the front-end rendering module, the front-end rendering module is called to render the object to be rendered, the page rendering result is obtained, and then the resource data and context information of the object to be rendered are stored.

[0076] When the client-side loading module receives a re-rendering instruction from the front end, it triggers a re-rendering for the object to be rendered based on the stored resource data and context information of the object. Specifically, after obtaining the stored resource data and context information of the object to be rendered, the client-side loading module sends the resource data and context information of the object to be rendered to the front-end rendering module. The front-end rendering module then re-renders the object based on the resource data and context information, and updates the page rendering result that caused the white screen error based on the re-rendered page rendering result, thereby overcoming the white screen error.

[0077] In practical applications, when the white screen anomaly detection result indicates that the page rendering result of the object to be rendered has encountered a white screen anomaly, this embodiment of the disclosure can also support configuring the number of times the white screen anomaly is handled, in order to further improve the user experience. Specifically, a configuration item for the number of times the white screen anomaly is handled can be added to the white screen anomaly detection module, and the number of times the white screen anomaly is handled can be configured based on requirements.

[0078] In one optional implementation, when a page rendering result for the object to be rendered is detected, a white screen anomaly detection module is invoked to detect the page rendering result and obtain a white screen anomaly detection result. If the white screen anomaly detection result indicates that a white screen anomaly has occurred in the page rendering result, it is determined whether the white screen anomaly detection for the object to be rendered has reached a preset number of consecutive detections. If the white screen anomaly detection module determines that the white screen anomaly detection for the object to be rendered has not reached the preset number of consecutive detections, the white screen anomaly detection module sends the white screen anomaly detection result to the front-end attribution detection module and invokes the front-end attribution detection module to detect the attribution event of the white screen anomaly.

[0079] The preset number of consecutive attempts is configured in advance based on requirements. This preset number of consecutive attempts controls the number of times a white screen error is processed. That is, if a white screen error occurs, the white screen error processing can be executed repeatedly within the preset number of consecutive attempts until the preset number of consecutive attempts is reached and the white screen error processing steps are stopped.

[0080] In another optional implementation, if the white screen anomaly detection result indicates that the page rendering result has a white screen anomaly, and if it is determined that the white screen anomaly detection for the object to be rendered has reached a preset number of consecutive times, then a preset prompt page is displayed for the object to be rendered on the white screen view of the object to be rendered.

[0081] The preset prompt page is used to indicate a rendering error for the object to be rendered.

[0082] To facilitate understanding of the above embodiments, this disclosure also provides a data interaction diagram of a page processing method, see reference. Figure 2Among them, the white screen anomaly detection module and the client loading module are implemented based on client-side technology, while the front-end rendering module and the front-end attribution detection module are implemented based on front-end technology.

[0083] S201: Receive the rendering request for page A.

[0084] S202: When the client loading module receives a rendering request for page A, the client loading module obtains and stores the resource data and context information of page A.

[0085] S203: The client-side loading module injects the resource data of page A into the front-end rendering module.

[0086] S204: Based on the resource data of page A, the front-end rendering module renders page A to obtain the page rendering result.

[0087] S205: The front-end rendering module sends the page rendering result to the client.

[0088] S206: When the client receives the page rendering result for page A, it calls the white screen anomaly detection module to detect the page rendering result and obtain the white screen anomaly detection result.

[0089] S207: Based on the white screen detection results, determine whether a white screen abnormality has occurred in the page rendering result.

[0090] S208: If the white screen anomaly detection result indicates that no white screen anomaly has occurred in the page rendering result, then the object to be rendered is displayed based on the page rendering result. At this point, the data interaction of the page processing method ends.

[0091] Otherwise, execute S209: If the white screen anomaly detection result indicates that the page rendering result has a white screen anomaly, then send the white screen anomaly detection result to the front-end attribution detection module.

[0092] S210: Call the front-end attribution detection module to detect the attribution event of the white screen exception.

[0093] S211: Determine whether an attribution event for a white screen error on page A has been detected.

[0094] S212: If an attribution event for a white screen error is detected on page A, the white screen error is handled based on the attribution event, and the page rendering result of page A is updated to overcome the white screen error. At this point, the data interaction of the page processing method ends.

[0095] Otherwise, execute S213: If the front-end attribution detection module does not detect an attribution event for page A's white screen exception, it sends a re-rendering instruction to the client loading module, instructing the client loading module to trigger a re-render for page A.

[0096] S214: The client-side loading module receives a re-rendering instruction and triggers a re-render for page A to overcome the white screen error. Specifically, after obtaining the stored resource data and context information of the object to be rendered, the client-side loading module sends the resource data and context information of the object to be rendered to the front-end rendering module. The front-end rendering module then re-renders the page based on the resource data and context information of the object to be rendered, and updates the rendering result of the page that experienced the white screen error based on the re-rendered page rendering result, thereby overcoming the white screen error. At this point, the data interaction of the page processing methods ends.

[0097] This embodiment of the present disclosure can detect white screen errors in cross-platform scenarios by calling the front-end attribution detection module, and process the white screen errors according to the detected attribution events, so as to update the page rendering results of the white screen error, reduce the probability of displaying a white screen page to users in cross-platform scenarios, and thus improve the user experience.

[0098] Based on the above method embodiments, this disclosure also provides a page processing apparatus, with reference to... Figure 3 This is a schematic diagram of a page processing apparatus provided in an embodiment of the present disclosure. The apparatus includes:

[0099] Module 301 is invoked in response to the page rendering result of the object to be rendered, and the white screen anomaly detection module is invoked to detect the page rendering result and obtain the white screen anomaly detection result; wherein, the page rendering result of the object to be rendered is rendered by the front-end rendering module;

[0100] The update module 302 is used to call the front-end attribution detection module to detect the attribution event of the white screen abnormality when the white screen abnormality detection result indicates that the page rendering result has a white screen abnormality, and after detecting the attribution event of the white screen abnormality, process the white screen abnormality based on the attribution event and update the page rendering result of the object to be rendered.

[0101] In one optional embodiment, the apparatus further includes:

[0102] The sending module is used to send a re-rendering instruction to the client loading module when the front-end attribution detection module does not detect the attribution event of the white screen abnormality, instructing the client loading module to trigger a re-rendering for the object to be rendered.

[0103] In one optional embodiment, the apparatus further includes:

[0104] The first acquisition module is used to respond to the rendering request for the object to be rendered, acquire the resource data and context information of the object to be rendered, inject the resource data into the front-end rendering module, call the front-end rendering module to render the object to be rendered, and obtain the page rendering result.

[0105] A storage module is used to store the resource data and context information of the object to be rendered;

[0106] Accordingly, the device also includes:

[0107] The first rendering module is used to call the client loading module to trigger a re-rendering of the object to be rendered based on the stored resource data and context information of the object to be rendered.

[0108] In one optional implementation, the update module includes:

[0109] The second acquisition module is used to send a rendering data request to the object to be rendered and obtain the latest rendering data of the object to be rendered when the attribution event of the white screen abnormality is detected as a rendering data abnormality event.

[0110] The second rendering module is used to trigger a re-rendering of the object to be rendered based on the latest rendering data, obtain the re-rendering result, and use the re-rendering result to update the page rendering result of the object to be rendered.

[0111] In one optional implementation, the object to be rendered includes a page and / or a resource card, and the object to be rendered is generated based on front-end code.

[0112] In one optional implementation, the first calling module includes:

[0113] The determination module is used to determine whether the white screen anomaly detection for the object to be rendered has reached a preset number of consecutive counts when the white screen anomaly detection result indicates that the page rendering result has a white screen anomaly.

[0114] The submodule is called to determine if the white screen anomaly detection for the object to be rendered has not reached a preset number of consecutive times, and then the front-end attribution detection module is called to detect the attribution event of the white screen anomaly.

[0115] In one optional embodiment, the apparatus further includes:

[0116] The display module is used to determine that when the white screen anomaly detection for the object to be rendered has reached a preset number of consecutive times, a preset prompt page is displayed for the object to be rendered; wherein, the preset prompt page is used to indicate that a rendering anomaly has occurred for the object to be rendered.

[0117] In the page processing method provided in this embodiment, firstly, in response to the page rendering result of the object to be rendered, a white screen anomaly detection module is called to detect the page rendering result and obtain a white screen anomaly detection result. The page rendering result of the object to be rendered is rendered by the front-end rendering module. Then, if the white screen anomaly detection result indicates that a white screen anomaly has occurred in the page rendering result, the front-end attribution detection module is called to detect the attribution event of the white screen anomaly. After detecting the attribution event of the white screen anomaly, the white screen anomaly is processed based on the attribution event, and the page rendering result of the object to be rendered is updated.

[0118] This embodiment of the present disclosure can detect white screen errors in cross-platform scenarios by calling the front-end attribution detection module, and process the white screen errors according to the detected attribution events, so as to update the page rendering results of the white screen error, reduce the probability of displaying a white screen page to users in cross-platform scenarios, and thus improve the user experience.

[0119] In addition to the methods and apparatus described above, this disclosure also provides a computer-readable storage medium storing instructions that, when executed on a terminal device, cause the terminal device to implement the page processing method described in this disclosure.

[0120] This disclosure also provides a computer program product, which includes a computer program / instructions that, when executed by a processor, implement the page processing method described in this disclosure.

[0121] In addition, this disclosure also provides a page processing device, see [link to relevant documentation]. Figure 4 As shown, it may include:

[0122] The page processing device includes a processor 401, a memory 402, an input device 403, and an output device 404. The number of processors 401 in the page processing device can be one or more. Figure 4 Taking a processor as an example. In some embodiments of this disclosure, the processor 401, memory 402, input device 403, and output device 404 can be connected via a bus or other means, wherein, Figure 4 Taking the example of a connection between China and Israel via a bus.

[0123] The memory 402 can be used to store software programs and modules. The processor 401 executes various functional applications and data processing of the page processing device by running the software programs and modules stored in the memory 402. The memory 402 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function, etc. In addition, the memory 402 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. The input device 403 can be used to receive input digital or character information, and to generate signal inputs related to user settings and function control of the page processing device.

[0124] Specifically in this embodiment, the processor 401 loads the executable files corresponding to the processes of one or more applications into the memory 402 according to the following instructions, and the processor 401 runs the applications stored in the memory 402, thereby realizing the various functions of the page processing device described above.

[0125] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0126] The above description is merely a specific embodiment of this disclosure, enabling those skilled in the art to understand or implement it. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this disclosure. Therefore, this disclosure is not to be limited to the embodiments described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A page processing method, characterized in that, The method includes: In response to the page rendering result of the object to be rendered, the white screen anomaly detection module is invoked to detect the page rendering result and obtain the white screen anomaly detection result; wherein, the page rendering result of the object to be rendered is rendered by the front-end rendering module; If the white screen anomaly detection result indicates that a white screen anomaly has occurred in the page rendering result, the front-end attribution detection module is called to detect the attribution event of the white screen anomaly. After detecting the attribution event of the white screen anomaly, the white screen anomaly is processed based on the attribution event, and the page rendering result of the object to be rendered is updated.

2. The method according to claim 1, characterized in that, The method further includes: If the front-end attribution detection module does not detect the attribution event for the white screen anomaly, a re-rendering instruction is sent to the client loading module, instructing the client loading module to trigger a re-rendering for the object to be rendered.

3. The method according to claim 2, characterized in that, Before the step of responding to the page rendering result for the object to be rendered and calling the white screen anomaly detection module to detect the page rendering result, and obtaining the white screen anomaly detection result, the method further includes: In response to a rendering request for the object to be rendered, the resource data and context information of the object to be rendered are obtained, the resource data is injected into the front-end rendering module, and the front-end rendering module is called to render the object to be rendered to obtain the page rendering result; In addition, the resource data and context information of the object to be rendered are stored; Accordingly, after sending a re-rendering instruction to the client loading module, instructing the client loading module to trigger a re-rendering for the object to be rendered, the process further includes: The client loading module is invoked to trigger a re-rendering of the object to be rendered based on the stored resource data and context information of the object to be rendered.

4. The method according to claim 1, characterized in that, After detecting the attribution event for the white screen anomaly, the process of handling the white screen anomaly based on the attribution event and updating the page rendering result of the object to be rendered includes: If the detected white screen anomaly is attributed to a rendering data anomaly, a rendering data request is sent to the object to be rendered to obtain the latest rendering data of the object to be rendered. Based on the latest rendering data, a re-render is triggered for the object to be rendered, a re-render result is obtained, and the page rendering result of the object to be rendered is updated using the re-render result.

5. The method according to claim 1, characterized in that, The object to be rendered includes pages and / or resource cards, and the object to be rendered is generated based on front-end code.

6. The method according to claim 1, characterized in that, If the white screen anomaly detection result indicates that a white screen anomaly has occurred in the page rendering result, then the front-end attribution detection module is invoked to detect the attribution event of the white screen anomaly, including: If the white screen anomaly detection result indicates that the page rendering result has a white screen anomaly, then determine whether the white screen anomaly detection for the object to be rendered has reached a preset number of consecutive times; If it is determined that the number of consecutive preset number of white screen anomaly detections for the object to be rendered has not been reached, the front-end attribution detection module is invoked to detect the attribution event of the white screen anomaly.

7. The method according to claim 6, characterized in that, The method further includes: If it is determined that the white screen anomaly detection for the object to be rendered has reached a preset number of consecutive times, a preset prompt page is displayed for the object to be rendered; wherein, the preset prompt page is used to indicate that a rendering anomaly has occurred for the object to be rendered.

8. A page processing apparatus, characterized in that, The device includes: The calling module is used to call the white screen anomaly detection module to detect the page rendering result for the object to be rendered in response to the page rendering result, and obtain the white screen anomaly detection result; wherein, the page rendering result of the object to be rendered is rendered by the front-end rendering module; The update module is used to call the front-end attribution detection module to detect the attribution event of the white screen anomaly when the white screen anomaly detection result indicates that a white screen anomaly has occurred in the page rendering result. After detecting the attribution event of the white screen anomaly, the module processes the white screen anomaly based on the attribution event and updates the page rendering result of the object to be rendered.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed on a terminal device, cause the terminal device to perform the method as described in any one of claims 1-7.

10. A page processing device, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the method as claimed in any one of claims 1-7.

11. A computer program product, characterized in that, The computer program product includes a computer program / instruction that, when executed by a processor, implements the method as described in any one of claims 1-7.

Images