CN105930266A - Webpage debugging method and device - Google Patents

Abstract

The present disclosure relates to a webpage debugging method and device, wherein the webpage debugging method includes: if receiving abnormal information about webpage access, suspending the loading of the webpage; sending a debugging request to a local pre-established service, so as to use the service to Operate the request content carried in the above debugging request; receive the debugging response returned by the service, and load and execute the new code carried in the debugging response to find the cause of the exception. In the embodiment of the present disclosure, it is possible to dynamically choose to suspend the loading of webpages as needed, and obtain a debugging response by interacting with pre-established services, and then find the cause of abnormal webpage access by loading and executing the new code carried in the debugging response, effectively reducing the It is difficult to debug and saves debugging time.

Description

Web page debugging method and device

technical field

The present disclosure relates to the technical field of mobile Internet, and in particular to a web page debugging method and device.

Background technique

Some problems are often encountered during mobile development, such as page rendering problems, page loading blockage or crashes, etc. For such problems, remote debugging is often used to solve them. Remote debugging can usually solve problems with obvious errors, but for some page rendering, page loading and other issues that may involve compatibility between webview and third-party libraries, this method cannot meet the needs.

For compatibility issues between webview and third-party libraries, you can cut the code and try again and again to find the code that may cause rendering problems. However, this debugging method is difficult and time-consuming to debug.

Contents of the invention

In order to overcome the problems existing in related technologies, the present disclosure provides a web page debugging method and device.

According to a first aspect of an embodiment of the present disclosure, a method for debugging a web page is provided, including:

If information about abnormal web page access is received, the loading of the web page is suspended;

Send a debugging request to a local pre-established service, so as to operate the request content carried in the debugging request through the service;

Receive the debugging response returned by the service, and load and execute the new code carried in the debugging response to find the cause of the exception.

In one embodiment, the method also includes:

Receive updated configuration information for the network view, where the updated configuration information is used to enable the network view to dynamically choose to pause loading the webpage or continue loading the webpage during the loading process of the webpage.

In an embodiment, the service is configured to receive the debugging request, operate on the request content carried in the debugging request, and return the debugging response.

In an embodiment, the request content includes at least one of the code block flag, the number of currently executed code lines, the dot position, the dot content, and the operation content, and the operation content includes at least one of the dot operation and the cutting operation item.

In one embodiment, the method also includes:

After the loading executes the new code carried in the debugging response, if no abnormal cause is found, the operation of pausing the loading of the webpage is repeatedly performed until the abnormal reason is found.

According to the second aspect of the embodiments of the present disclosure, a webpage debugging device is provided, including:

The loading suspension module is configured to suspend the loading of the webpage if information about abnormal webpage access is received;

The sending module is configured to send a debugging request to a local pre-established service, so as to operate the request content carried in the debugging request through the service;

The receiving, loading and executing module is configured to receive the debugging response returned by the service, and load and execute the new code carried in the debugging response to find the cause of the exception.

In one embodiment, the device also includes:

The configuration information receiving module is configured to receive updated configuration information for the network view, and the updated configuration information is used to enable the network view to dynamically choose to suspend loading the webpage or continue loading the webpage during the webpage loading process.

In an embodiment, the service is configured to receive the debugging request, operate on the request content carried in the debugging request, and return the debugging response.

In an embodiment, the request content includes at least one of the code block flag, the number of currently executed code lines, the dot position, the dot content, and the operation content, and the operation content includes at least one of the dot operation and the cutting operation item.

In one embodiment, the device also includes:

The processing module is configured to call the pause loading module to execute the operation of pausing loading the webpage after the receiving, loading and executing module loads and executes the new code carried in the debugging response, if no abnormal cause is found, until the cause of the abnormality is found.

According to a third aspect of the embodiments of the present disclosure, a web page debugging device is provided, including:

processor;

memory for storing processor-executable instructions;

where the processor is configured as:

If information about abnormal web page access is received, the loading of the web page is suspended;

Send a debugging request to a local pre-established service, so as to operate the request content carried in the debugging request through the service;

Receive the debugging response returned by the service, and load and execute the new code carried in the debugging response to find the cause of the exception.

The technical solutions provided by the embodiments of the present disclosure may include the following beneficial effects: by suspending the loading of web pages, sending a debugging request to a local pre-established service, and loading and executing the new code carried in the debugging response according to the debugging response returned by the service, so as to find The purpose of the abnormal reason for webpage access, it can be seen that this method can dynamically choose to pause loading webpages according to needs, and obtain a debugging response by interacting with pre-established services, and then find the webpage by loading and executing the new code carried in the debugging response Access to the cause of the exception effectively reduces the difficulty of debugging and saves debugging time.

By receiving the updated configuration information for the web view, the web view can dynamically choose to pause and continue loading the web page during the web page loading process, so as to find the web page by continuously pausing the web page loading and loading and executing the new code carried in the debugging response The reason for the access exception provides the conditions.

By describing the function of the service, the network view end can interact with the service and provide conditions for finding the cause of the exception.

An introduction to the request content carried in the debugging request can more clearly demonstrate the technical solution of the web page debugging method provided by the embodiments of the present disclosure.

By executing the process of pausing loading web pages, interacting with services, and continuing to load and execute new codes multiple times, the cause of the exception can be found, the implementation method is simple, and the debugging efficiency is high.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description serve to explain the principles of the invention.

Fig. 1 is a flow chart of a method for debugging a web page according to an exemplary embodiment.

Fig. 2 is a flow chart of another web page debugging method according to an exemplary embodiment.

Fig. 3 is a schematic diagram of a web page debugging process according to an exemplary embodiment.

Fig. 4 is a block diagram of an apparatus for debugging a web page according to an exemplary embodiment.

Fig. 5 is a block diagram of another apparatus for debugging a web page according to an exemplary embodiment.

Fig. 6 is a block diagram of another apparatus for debugging a web page according to an exemplary embodiment.

Fig. 7 is a block diagram showing a device suitable for webpage debugging according to an exemplary embodiment.

detailed description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numerals in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the present invention. Rather, they are merely examples of apparatuses and methods consistent with aspects of the invention as recited in the appended claims.

Fig. 1 is a flow chart of a webpage debugging method shown according to an exemplary embodiment. As shown in Fig. 1, the webpage debugging method can be applied to the webview end, and the webpage debugging method includes the following steps S101-S103:

In step S101, if the information that the webpage access is abnormal is received, the loading of the webpage is suspended.

In this embodiment, the web page access exception may include, but not limited to, a problem in web page rendering, page loading blockage or crash, and the like. When receiving the information that the web page access is abnormal, the loading of the web page is suspended.

In step S102, a debugging request is sent to a local pre-established service, so that the service can operate on the request content carried in the debugging request.

In this embodiment, the debugging request can be a hypertext transfer protocol (http) request, and the request content can include but not limited to at least one of the code block mark, the number of lines of code currently executed, the location of the dot, the content of the dot and the operation content , the operation content may include, but not limited to, at least one of a dotting operation and a cropping operation.

Wherein, the pre-established service may be a software body providing some functions, and the service may be used to receive the debugging request, operate on the request content carried in the debugging request, and return a debugging response.

In step S103, the debugging response returned by the service is received, and the new code carried in the debugging response is loaded and executed to find the cause of the abnormality.

In this embodiment, after receiving the debugging response returned by the service, the new code carried in the debugging response can be loaded and executed, for example, the new code after adding dotted content or the new code after cutting is executed, so as to find the cause of the exception.

In this embodiment, the purpose of pausing the loading of the webpage and sending the debugging request to the service is to confirm the specific processing method of the debugging request. If dots are required, request dots and execute the new code returned by the service plus the dotted content; if tailoring is required, request tailoring and execute the new codes after the tailoring returned by the service; specific processing methods may include but are not limited to dots and cutting .

In the embodiment of the webpage debugging method described above, by pausing the loading of the webpage, sending a debugging request to the local pre-established service, and loading and executing the new code carried in the debugging response according to the debugging response returned by the service, in order to achieve the purpose of finding the reason for the abnormal webpage access, by It can be seen that this method can dynamically choose to pause loading webpages as needed, and obtain a debugging response by interacting with pre-established services, and then find the cause of webpage access exceptions by loading and executing the new code carried in the debugging response, effectively reducing debugging time. Difficulty, saving debugging time.

Fig. 2 is a flowchart of a web page debugging method according to an exemplary embodiment. As shown in Fig. 2, the method includes the following steps S201-S205:

In step S201, the updated configuration information for the network view is received, the updated configuration information is used to enable the network view to dynamically choose to pause loading the webpage or continue loading the webpage during the loading process of the webpage.

In this embodiment, the webview terminal receives the updated configuration information for the webview terminal from the debugger, and the updated configuration information is used to enable the webview terminal to dynamically choose to pause loading the webpage or continue loading the webpage during the webpage loading process.

In step S202, if the page rendering abnormality information is received, the loading of the webpage is suspended.

In step S203, a debugging request is sent to a local pre-established service, so that the service can operate on the request content carried in the debugging request.

In step S204, the debugging response returned by the service is received, and the new code carried in the debugging response is loaded and executed.

In step S205, it is judged whether the cause of abnormality is found, and if the cause of abnormality is found, the operation ends; if the cause of abnormality is not found, then turn to the execution of pausing the loading of the webpage in step S202.

In this embodiment, if the abnormal reason is not found, then continue to suspend the loading of the webpage, repeat steps S202-S205, until the abnormal reason is found, the process of this search can be referred to Figure 3, as can be seen from Figure 3, in the first pause After loading the webpage, you can send a debugging request to the service, receive the debugging response returned by the service, and execute the new code carried in the debugging response. If the abnormal cause is still not found at this time, you can continue to pause loading the webpage, that is, the second pause Load the webpage and repeat the above process until the cause of the abnormality is found.

In the above embodiment of the web page debugging method, by receiving updated configuration information for the web view, the web view can dynamically choose to suspend loading the web page and continue loading the web page during the web page loading process, so as to continuously pause and load the web page and execute the debugging response for the subsequent The new code carried provides the conditions to find the reason for the abnormal web page access.

Corresponding to the aforementioned embodiments of the web page debugging method, the present disclosure also provides embodiments of a web page debugging device.

FIG. 4 is a block diagram of a webpage debugging device according to an exemplary embodiment. As shown in FIG. 4 , the webpage debugging device includes: a pause loading module 41 , a sending module 42 and a receiving loading execution module 43 .

The pausing loading module 41 is configured to suspend loading the webpage if receiving information that the webpage access is abnormal.

In this embodiment, the web page access exception may include, but not limited to, a problem in web page rendering, page loading blockage or crash, and the like. When receiving the information that the web page access is abnormal, the loading of the web page is suspended.

The sending module 42 is configured to send a debugging request to a local pre-established service, so as to operate on the request content carried in the debugging request through the service.

In this embodiment, the debugging request can be a hypertext transfer protocol (http) request, and the request content can include but not limited to at least one of the code block mark, the number of lines of code currently executed, the location of the dot, the content of the dot and the operation content , the operation content may include, but not limited to, at least one of a dotting operation and a cropping operation.

Wherein, the pre-established service may be a software body providing some functions, and the service may be used to receive the debugging request, operate on the request content carried in the debugging request, and return a debugging response.

The receiving, loading and executing module 43 is configured to receive the debugging response returned by the service, and load and execute the new code carried in the debugging response to find the cause of the abnormality.

In this embodiment, after receiving the debugging response returned by the service, the new code carried in the debugging response can be loaded and executed, for example, the new code after adding dotted content or the new code after cutting is executed, so as to find the cause of the exception.

In this embodiment, the purpose of pausing the loading of the webpage and sending the debugging request to the service is to confirm the specific processing method of the debugging request. If dots are required, request dots and execute the new code returned by the service plus the dotted content; if tailoring is required, request tailoring and execute the new codes after the tailoring returned by the service; specific processing methods may include but are not limited to dots and cutting .

The device shown in FIG. 4 is used to implement the above-mentioned method flow shown in FIG. 1 , and the relevant content involved is described in the same way, and will not be repeated here.

In the embodiment of the above-mentioned webpage debugging device, by suspending the loading of webpages, sending a debugging request to a local pre-established service, and loading and executing the new code carried in the debugging response according to the debugging response returned by the service, to achieve the purpose of finding the reason for the abnormal webpage access, by It can be seen that this method can dynamically choose to pause loading webpages as needed, and obtain a debugging response by interacting with pre-established services, and then find the cause of webpage access exceptions by loading and executing the new code carried in the debugging response, effectively reducing debugging time. Difficulty, saving debugging time.

FIG. 5 is a block diagram of another web page debugging device according to an exemplary embodiment. As shown in FIG. 5 , on the basis of the embodiment shown in FIG. 4 , the device may further include: a configuration information receiving module 40 .

The configuration information receiving module 40 is configured to receive updated configuration information for the network view, the updated configuration information is used to enable the network view to dynamically choose to suspend loading the webpage or continue loading the webpage during the loading process of the webpage.

In this embodiment, the webview terminal receives the updated configuration information for the webview terminal from the debugger, and the updated configuration information is used to enable the webview terminal to dynamically choose to pause loading the webpage or continue loading the webpage during the webpage loading process.

The device shown in FIG. 5 is used to implement the above-mentioned method flow shown in FIG. 2 , and the relevant content involved is described in the same way and will not be repeated here.

In the embodiment of the web page debugging device described above, by receiving updated configuration information for the web view, the web view can dynamically choose to suspend loading web pages and continue loading web pages during the web page loading process, so as to continuously pause loading web pages and load execution in the subsequent debugging response. The new code carried provides the conditions to find the reason for the abnormal web page access.

Fig. 6 is a block diagram of another web page debugging device shown according to an exemplary embodiment. As shown in Fig. 6, on the basis of the embodiment shown in Fig. 4 or Fig. 5 above, the device may further include: a processing module 44 .

The processing module 44 is configured to call the pause loading module 41 to execute the operation of pausing the loading of the webpage after the receiving, loading and executing module 43 loads and executes the new code carried in the debugging response, if no abnormal cause is found, until the cause of the abnormality is found.

In this embodiment, if the abnormal reason is not found, then the suspension loading module 41 can be called to continue to suspend the loading of the webpage until the abnormal reason is found. The process of this search can be referred to FIG. 3 . As can be seen from FIG. After loading the webpage, you can send a debugging request to the service, receive the debugging response returned by the service, and execute the new code carried in the debugging response. If the abnormal cause is still not found at this time, you can continue to pause loading the webpage, that is, the second pause Load the webpage and repeat the above process until the cause of the abnormality is found.

The device shown in FIG. 6 is used to implement the above-mentioned method flow shown in FIG. 2 , and related content is described in the same way, and will not be repeated here.

In the embodiment of the above-mentioned web page debugging device, by performing the process of pausing loading web pages, interacting with services, and continuing to load and execute new codes multiple times, the cause of the abnormality can be found, the implementation method is simple, and the debugging efficiency is high.

Regarding the apparatus in the above embodiments, the specific manner in which each module and sub-module performs operations has been described in detail in the embodiments related to the method, and will not be described in detail here.

Fig. 7 is a block diagram showing a device suitable for web page debugging according to an exemplary embodiment. For example, the apparatus 700 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, an aircraft, and the like.

7, device 700 may include one or more of the following components: processing component 702, memory 704, power supply component 706, multimedia component 708, audio component 710, input/output (I/O) interface 712, sensor component 714, and communication component 716 .

The processing component 702 generally controls the overall operations of the device 700, such as those associated with display, telephone calls, data communications, camera operations, and recording operations. The processing element 702 may include one or more processors 720 to execute instructions to complete all or part of the steps of the above method. Additionally, processing component 702 may include one or more modules that facilitate interaction between processing component 702 and other components. For example, processing component 702 may include a multimedia module to facilitate interaction between multimedia component 708 and processing component 702 .

Memory 704 is configured to store various types of data to support operations at device 700 . Examples of such data include instructions for any application or method operating on device 700, contact data, phonebook data, messages, pictures, videos, and the like. The memory 704 can be realized by any type of volatile or non-volatile storage device or their combination, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Magnetic or Optical Disk.

Power component 706 provides power to various components of device 700 . Power components 706 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for device 700 .

The multimedia component 708 includes a screen that provides an output interface between the device 700 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may not only sense a boundary of a touch or swipe action, but also detect duration and pressure associated with the touch or swipe action. In some embodiments, the multimedia component 708 includes a front camera and/or a rear camera. When the device 700 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera can receive external multimedia data. Each front camera and rear camera can be a fixed optical lens system or have focal length and optical zoom capability.

The audio component 710 is configured to output and/or input audio signals. For example, the audio component 710 includes a microphone (MIC) configured to receive external audio signals when the device 700 is in operation modes, such as call mode, recording mode and voice recognition mode. Received audio signals may be further stored in memory 704 or sent via communication component 716 . In some embodiments, the audio component 710 also includes a speaker for outputting audio signals.

The I/O interface 712 provides an interface between the processing component 702 and a peripheral interface module, which may be a keyboard, a click wheel, a button, and the like. These buttons may include, but are not limited to: a home button, volume buttons, start button, and lock button.

Sensor assembly 714 includes one or more sensors for providing various aspects of status assessment for device 700 . For example, the sensor component 714 can detect the open/closed state of the device 700, the relative positioning of components, such as the display and keypad of the device 700, and the sensor component 714 can also detect a change in the position of the device 700 or a component of the device 700 , the presence or absence of user contact with the device 700 , the device 700 orientation or acceleration/deceleration and the temperature change of the device 700 . Sensor assembly 714 may include a proximity sensor configured to detect the presence of nearby objects in the absence of any physical contact. Sensor assembly 714 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor component 714 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor or a temperature sensor.

The communication component 716 is configured to facilitate wired or wireless communication between the apparatus 700 and other devices. The device 700 can access wireless networks based on communication standards, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 716 receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 716 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, Infrared Data Association (IrDA) technology, Ultra Wide Band (UWB) technology, Bluetooth (BT) technology and other technologies.

In an exemplary embodiment, apparatus 700 may be programmed by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable A gate array (FPGA), controller, microcontroller, microprocessor or other electronic component implementation for performing the methods described above.

In an exemplary embodiment, there is also provided a non-transitory computer-readable storage medium including instructions, such as the memory 704 including instructions, which can be executed by the processor 720 of the device 700 to implement the above method. For example, the non-transitory computer readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.

Other embodiments of the disclosure will be readily apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any modification, use or adaptation of the present disclosure, and these modifications, uses or adaptations follow the general principles of the present disclosure and include common knowledge or conventional technical means in the technical field not disclosed in the present disclosure . The specification and examples are to be considered exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It should be understood that the present disclosure is not limited to the precise constructions which have been described above and shown in the drawings, and various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims (11)

1. A web page debugging method, characterized in that the method comprises: If information about abnormal web page access is received, the loading of the web page is suspended; Send a debugging request to a local pre-established service, so as to operate the request content carried in the debugging request through the service; Receive the debugging response returned by the service, and load and execute the new code carried in the debugging response to find the cause of the exception. 2. The webpage debugging method according to claim 1, wherein the method further comprises: Receive updated configuration information for the network view, where the updated configuration information is used to enable the network view to dynamically choose to pause loading the webpage or continue loading the webpage during the loading process of the webpage. 3. The webpage debugging method according to claim 1, wherein the service is used to receive the debugging request, operate on the request content carried in the debugging request, and return the debugging response. 4. The web page debugging method according to claim 3, wherein the request content includes at least one of a code block mark, the number of code lines currently executed, a dotted position, a dotted content, and an operation content, and the operation The content includes at least one of a dotting operation and a cropping operation. 5. The web page debugging method according to any one of claims 1-4, wherein the method further comprises: After the loading executes the new code carried in the debugging response, if no abnormal cause is found, the operation of pausing the loading of the webpage is repeatedly performed until the abnormal reason is found. 6. A web page debugging device, characterized in that the device comprises: The loading suspension module is configured to suspend the loading of the webpage if information about abnormal webpage access is received; The sending module is configured to send a debugging request to a local pre-established service, so as to operate the request content carried in the debugging request through the service; The receiving, loading and executing module is configured to receive the debugging response returned by the service, and load and execute the new code carried in the debugging response to find the cause of the exception. 7. The webpage debugging device according to claim 6, wherein the device further comprises: The configuration information receiving module is configured to receive updated configuration information for the network view, and the updated configuration information is used to enable the network view to dynamically choose to suspend loading the webpage or continue loading the webpage during the webpage loading process. 8. The web page debugging device according to claim 6, wherein the service is configured to receive the debugging request, operate on the request content carried in the debugging request, and return the debugging response. 9. The web page debugging device according to claim 8, wherein the request content includes at least one of a code block mark, the number of code lines currently executed, a dotted position, a dotted content, and an operation content, and the operation The content includes at least one of a dotting operation and a cropping operation. 10. The webpage debugging device according to any one of claims 6-9, wherein the device further comprises: The processing module is configured to call the pause loading module to execute the operation of pausing loading the webpage after the receiving, loading and executing module loads and executes the new code carried in the debugging response, if no abnormal cause is found, until the cause of the abnormality is found. 11. A web page debugging device, characterized in that it comprises: processor; memory for storing processor-executable instructions; Wherein, the processor is configured as: If information about abnormal web page access is received, the loading of the web page is suspended; Send a debugging request to a local pre-established service, so as to operate the request content carried in the debugging request through the service; Receive the debugging response returned by the service, and load and execute the new code carried in the debugging response to find the cause of the exception.