Browser debugging method and device, storage medium and electronic equipment
By creating a modification interface within the browser kernel to display and modify browser settings, the problem of existing tools being unable to perform global debugging and restarts is solved, achieving an efficient and secure browser debugging process.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- BEIJING HONGTENG INTELLIGENT TECH CO LTD
- Filing Date
- 2024-11-11
- Publication Date
- 2026-05-12
AI Technical Summary
Existing browser debugging tools cannot display all browser settings information, which limits debugging. Furthermore, changing the configuration may require a restart, affecting debugging efficiency.
By creating a modification interface within the browser kernel, all browser settings information can be displayed, and modifications can be made based on user commands, applying the modified settings without restarting the browser.
It enables comprehensive viewing and modification of browser state data, improving debugging efficiency and ensuring the normal workflow and security of debugging work.
Smart Images
Figure CN122019342A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of computer technology, and more specifically, to a browser debugging method, apparatus, storage medium, and electronic device in the field of computer technology. Background Technology
[0002] A browser is an application used to access and display internet content. During the browser development, testing, and maintenance phases, staff need to modify relevant browser information to debug the browser to its ideal state. However, existing browser debugging tools can only display some local configuration parameters for staff to adjust, and cannot show all relevant parameters. This limits staff when debugging browser configurations, preventing them from making adjustments based on the global settings. Furthermore, changes to local configuration parameters using existing debugging tools may cause the browser to restart, interrupting the debugging work and wasting time. Therefore, a more convenient and efficient browser debugging method is needed. Summary of the Invention
[0003] This application provides a browser debugging method, apparatus, storage medium, and electronic device. The method can facilitate users to view and modify browser status-related data by displaying all browser settings information, and can run the browser directly with the modified settings information without restarting, thereby ensuring the normal process of browser debugging for users and improving the efficiency of browser debugging.
[0004] In a first aspect, embodiments of this application provide a browser debugging method, the method comprising:
[0005] The browser's modification interface is opened based on the user's access command, and the browser settings information of the browser is displayed on the modification interface.
[0006] Obtain the data modification instructions input by the user on the modification interface;
[0007] The browser settings are modified based on the data modification instructions, and the browser is controlled to run according to the modified browser settings.
[0008] The above technical solution allows users to view and modify browser status data by displaying all browser settings information, and the browser can run directly with the modified settings without restarting, thus ensuring the normal process of browser debugging and improving the efficiency of browser debugging.
[0009] In conjunction with the first aspect, in some possible implementations, the browser settings information includes the browser's local configuration parameters, user preference settings parameters, and memory data.
[0010] The above technical solution can comprehensively display the relevant settings parameters of the browser to users, so that users can debug the browser.
[0011] In conjunction with the first aspect, in some possible implementations, the step of opening a modification interface in the browser kernel based on the user's access command, and displaying the browser's settings information on the modification interface, includes:
[0012] If a user's access instruction to modify the interface is received, then an access permission verification process is performed on the user.
[0013] If the user passes the access permission verification, the modification interface is opened, and the browser settings information of the browser is displayed on the modification interface.
[0014] The above technical solution can prevent browser settings from being leaked to unauthorized personnel through access permission verification, thus ensuring the privacy and security of browser settings.
[0015] In conjunction with the first aspect, in some possible implementations, the access permission verification process for the user includes:
[0016] Display an access verification window in the browser and obtain the access permission verification information entered by the user in the access verification window;
[0017] If the access permission verification information exists in the access whitelist, then the user is determined to have passed the access permission verification process.
[0018] The above technical solution can verify a user's access permissions through an access verification window, thereby preventing unauthorized access and further improving the security of browser settings and the accuracy of access control.
[0019] In conjunction with the first aspect, in some possible implementations, the modification of the browser settings information based on the data modification instruction includes:
[0020] Determine the target setting parameters for the data modification instruction, and obtain the modification value in the data modification instruction;
[0021] Change the value of the target setting parameter to the modified value.
[0022] The above technical solution can accurately identify the target settings parameters that need to be modified and modify them, thereby improving the efficiency and accuracy of modifying browser settings.
[0023] In conjunction with the first aspect, in some possible implementations, before opening the browser's modification interface based on the user's access instruction, the following steps are also included:
[0024] Create and modify the interface within the browser engine.
[0025] The above technical solutions enable tight integration between the modified interface and browser kernel functions, thereby reducing the risk of data exposure and improving data acquisition efficiency.
[0026] In conjunction with the first aspect, in some possible implementations, the method further includes:
[0027] Generate target modification information based on the data modification instructions;
[0028] The target modification information is saved to the browser's history modification record.
[0029] The above technical solution makes it easier for users to review and retrospectively review changes made to browser settings.
[0030] Secondly, embodiments of this application provide a browser debugging device, the device comprising:
[0031] The interface display unit is used to open the browser's modification interface based on the user's access command, and to display the browser's browser settings information on the modification interface.
[0032] The instruction acquisition unit is used to acquire the data modification instruction input by the user for the modification interface;
[0033] The modification processing unit is used to modify the browser settings information based on the data modification instruction, and control the browser to run according to the modified browser settings information.
[0034] Thirdly, embodiments of this application provide a computer storage medium storing a plurality of instructions adapted for loading by a processor and executing the above-described method steps.
[0035] Fourthly, embodiments of this application provide an electronic device that may include: a processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and to execute the above-described method steps.
[0036] In one or more embodiments of this application, a browser modification interface is opened based on a user's access command. The browser settings information is displayed on this interface. Data modification commands input by the user are obtained, and the browser settings information is modified based on these commands. The browser is then controlled to run according to the modified browser settings. Displaying all browser settings facilitates user viewing and modification of browser status-related data, and the browser can run directly with the modified settings without restarting, thus ensuring a normal workflow for browser debugging and improving debugging efficiency. Attached Figure Description
[0037] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0038] Figure 1 This is a system architecture diagram of a browser debugging device provided in an embodiment of this application;
[0039] Figure 2 This is a flowchart illustrating a browser debugging method provided in an embodiment of this application;
[0040] Figure 3 This is a flowchart illustrating a browser debugging method provided in an embodiment of this application;
[0041] Figure 4 This is an example schematic diagram of an access verification window provided in an embodiment of this application;
[0042] Figure 5 This is a schematic diagram of the structure of a browser debugging device provided in an embodiment of this application;
[0043] Figure 6 This is a schematic diagram of the structure of a browser debugging device provided in an embodiment of this application;
[0044] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation
[0045] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0046] A browser is an application used to access and display internet content. It loads web pages, images, or videos from internet servers onto a user's terminal device. For example, a user can install a browser on their terminal device, and the browser can request web page content through the entered URL and present it to the user, thus achieving the function of displaying a webpage. To ensure the normal and efficient operation of the browser on the terminal device, users can perform maintenance tasks such as performance optimization, compatibility testing, and troubleshooting. Users can be either the owner of the terminal device with the browser installed or browser-related personnel. Understandably, browser debugging is often required during maintenance. Browser debugging involves modifying relevant parameters and configurations of the browser until it functions correctly or a fault is resolved. Existing debugging tools only allow users to modify some browser configuration parameters, and some changes to these parameters may cause the browser to restart, interrupting the user's browser debugging work and affecting debugging efficiency.
[0047] The browser debugging method provided in this application can be implemented using a computer program and can run on a browser debugging device based on the von Neumann architecture. This computer program can be integrated into an application or run as a standalone utility application. The browser debugging device can be a terminal device with a browser installed, or it can be a module or application within the browser or terminal device used to implement the browser debugging method. The browser debugging device can create a modification interface in the browser, which users can access and modify to view and modify browser settings. These browser settings are parameters related to the browser, including local configuration parameters, user preference settings, and memory data. Local configuration parameters can be browser configuration files or settings files used to control browser behavior and functions, and can be stored in the browser's local storage. User preference settings are personalized settings for browser behavior and interface, and can be obtained based on themes, bookmarks, browsing history, etc., set by the user for the browser. Memory data can be real-time data used by the browser at runtime. For example, it can include various information that the browser is processing, such as the content of currently open tabs, temporary cache, network request data, etc. Memory data can be stored in the random access memory (RAM) of the terminal device.
[0048] Please see also Figure 1 This application provides a system architecture diagram for a browser debugging device. The browser debugging device can create a modification interface within the browser's kernel. The browser kernel is the core of the browser, used to parse webpage code and present it to the user, such as HTML, CSS, and JavaScript. It also handles all page rendering, layout, and interaction. The modification interface created within the browser kernel is not a regular webpage but an internal interface tightly integrated with the browser's core functions. This allows the browser debugging device to obtain browser settings information and display it on the modification interface. Furthermore, it can obtain user-inputted modification commands based on the modification interface, thereby changing the browser settings and enabling users to debug the browser. The modification interface is a WebUI interface, which is a user interface built using Web technologies, running within the browser and used for user interaction and information display.
[0049] The browser debugging method provided in this application will be described in detail below with reference to specific embodiments.
[0050] Please see Figure 2 This is a flowchart illustrating a browser debugging method provided in an embodiment of this application. Figure 2 As shown, the method described in this application embodiment may include the following steps S101-S103.
[0051] S101 opens the browser's modification interface based on the user's access command, and displays the browser's settings information on the modification interface.
[0052] Specifically, when a user wants to debug their browser, they can send an access command to the browser. When the browser debugging device detects the access command, it can open the browser's modification interface based on the user's access command. The access command can take the form of a click, voice, or inputting the Uniform Resource Locator (URL) of the modification interface. For example, the browser debugging device can display a hyperlink or button on the browser to jump to the modification interface, and the user can send an access command to the browser by clicking the hyperlink or button. After opening the browser's modification interface, the browser debugging device can obtain the current browser settings information and display this browser settings information on the modification interface, so that the user can have a comprehensive understanding of the browser's current operating status through the browser settings information, which is convenient for browser debugging.
[0053] S102, Obtain the data modification command entered by the user on the modification interface.
[0054] Specifically, the browser debugging device can not only display browser settings information to the user through the modification interface, but also allow the user to modify the browser settings through the modification interface. The user can input data modification commands into the modification interface, and the browser debugging device can obtain the data modification commands input by the user. For example, when a user wants to change a certain setting parameter in the browser settings information, they can input data modification commands for that setting parameter into the modification interface and specify the desired modification value in the data modification commands.
[0055] S103 modifies browser settings based on data modification instructions and controls browser operation according to the modified browser settings.
[0056] Specifically, the browser debugging device can modify browser settings based on data modification commands. For example, it can modify the setting parameters targeted by the data modification command to the value desired by the user, and control the browser's operation based on the modified browser settings. It is understandable that modifying browser settings may affect the browser's running status, such as changing the default homepage, changing or extending plugins, deleting or saving applications, etc. This allows users to view the browser's running status after modification without restarting the browser, thereby gradually optimizing or adjusting the browser while adjusting the browser settings.
[0057] In this embodiment, a browser modification interface is opened based on a user's access command. The browser settings information is displayed on this interface. The user's data modification command input to the modification interface is obtained, and the browser settings information is modified based on this command. The browser is then controlled to run according to the modified browser settings. Displaying all browser settings facilitates user viewing and modification of browser status data, and the browser runs directly with the modified settings without requiring a restart, thus ensuring a normal workflow for browser debugging and improving debugging efficiency.
[0058] Please see Figure 3 This is a flowchart illustrating a browser debugging method provided in an embodiment of this application. Figure 3 As shown, the method described in this application embodiment may include the following steps S201-S208.
[0059] S201, Create and modify the interface within the browser kernel.
[0060] Specifically, browser debugging tools can create a modification interface within the browser kernel, allowing users to directly interact with the browser's core functions and settings. This means that creating the modification interface within the browser kernel allows for tight integration, better utilizing the functions and data provided by the browser kernel. This facilitates subsequent acquisition and modification of browser settings. Directly obtaining browser settings from the browser kernel also reduces the risk of data exposure and improves data acquisition efficiency. In situations requiring frequent and repeated acquisition and modification of browser settings, such as during browser debugging, increased data processing speed enhances the efficiency of browser debugging.
[0061] Optionally, when creating the modification interface, a URL corresponding to the modification interface can be generated so that users can access the modification interface via the URL.
[0062] S202, if a user's access instruction to modify the interface is received, then the user's access permission is verified.
[0063] Specifically, when a user wants to debug a browser, they can send an access command to the browser. This command can take the form of a click, voice command, or inputting the URL of the modified interface. For example, a browser debugging device can display a hyperlink or button on the browser to redirect to the modified interface, and the user can send the access command by clicking the hyperlink or button. If the browser debugging device displays browser settings information immediately upon detecting an access command, it could lead to the leakage of browser settings. It's understandable that browser settings are closely related to the browser's security and operational status; arbitrarily changing them could cause the browser to malfunction or introduce dangerous vulnerabilities. Therefore, if the browser receives a user's access command for modifying the interface, it can perform an access permission verification. This verification can be done using the initial settings of the browser debugging device or by authorized personnel to determine whether the user has the necessary access permissions. If the user passes the access permission verification, they have the required permissions; if they fail, they do not.
[0064] Optionally, if a user's access command for modifying the interface is received, the browser debugging device can display an access verification window in the browser. The access verification window may contain an input box, allowing the user to enter access permission verification information. After obtaining the access permission verification information entered by the user, the browser debugging device can compare the access permission verification information with the access whitelist. The access whitelist stores all access permission verification information that supports access to the modified interface. If the access permission verification information entered by the user exists in the access whitelist, it can be determined that the user has access permission and the user passes the access permission verification process.
[0065] Optionally, the access permission verification information can be a string of characters representing access permissions, or it can be an access account and the corresponding access password. If the access permission verification information is a pair of access accounts and access passwords, the access whitelist can store all access accounts and their corresponding access passwords, as well as the mapping relationship between access accounts and access passwords. Only when the access account, access password, and the mapping relationship entered by the user all exist in the access whitelist can it be determined that the user has passed the access permission verification process. Please refer to [link / reference]. Figure 4 This document provides an example of an access verification window in an embodiment of this application. If the browser installed on the terminal device is Chrome, the browser debugging device can create and modify the interface based on the browser core and obtain the URL "chrome: / / prefs-internals / " corresponding to the modified interface. The user can then send an access command by entering the URL into the browser. Figure 4As shown, users can enter the URL "chrome: / / prefs-internals / " in the browser's search box to send an access command for modifying the interface to the browser. When the browser debugging device detects the access command for modifying the interface, it can pop up an access verification window and prompt the user to enter access permission information. If the access permission information is an access account and access password, the browser debugging device can determine whether the user has access permission based on the access account and access password entered by the user.
[0066] S203 If the user passes the access permission verification, the modification interface will be opened, displaying the browser's settings information.
[0067] Specifically, if the user has access permissions (i.e., the user passes the access permission verification process), the browser debugging device can open the modification interface in the browser, obtain browser settings information based on the relevant functions of the browser core, and display the browser settings information on the modification interface. The browser settings information may include local configuration parameters, user preference settings parameters, and memory data, etc.
[0068] S204, Obtain the data modification command entered by the user on the modification interface.
[0069] Specifically, the browser debugging device can not only display browser settings information to the user in the modification interface, but also allow the user to modify the browser settings information through the modification interface. The user can input data modification commands in the modification interface, and the browser debugging device can obtain the data modification commands input by the user in the modification interface.
[0070] S205, determine the target setting parameters for the data modification instruction, and obtain the modified value in the data modification instruction.
[0071] Specifically, when a user wants to modify a target setting parameter in the browser settings, they can enter a modification command for the target setting parameter into the modification interface. The modification command can include the user's desired modification value. Therefore, after receiving the data modification command, the browser debugging device can determine the target setting parameter targeted by the data modification command and obtain the modification value in the data modification command.
[0072] Optionally, modifying browser settings may affect the browser's operating status. Therefore, upon receiving a user's data modification instruction, the browser debugging device can display a confirmation window in the browser. This confirmation window serves as a secondary confirmation of the user's intention to modify the browser settings. For example, the confirmation window may display a prompt asking "Do you want to modify this parameter?", along with "Yes" and "No" option buttons. If the user clicks the "Yes" button, it indicates that the user confirms the modification of the browser settings and continues with the relevant steps. Conversely, if the user clicks the "No" button, it indicates that the user does not want to modify the browser settings and therefore does not need to perform the relevant steps, thus avoiding browser settings changes due to user error and preventing browser malfunctions.
[0073] Optionally, since browser settings are displayed directly on the modification interface, when a user wants to modify a target setting parameter, they can delete the original value displayed on the modification interface and enter the desired value. This sends a data modification command; the deleted setting parameter becomes the target setting parameter, and the entered value becomes the modified value. Understandably, if the user confirms in the modification confirmation window that they will not make any changes, for example, by clicking the "No" button, the browser modification device can restore the value displayed on the modification interface to its original value.
[0074] Optionally, since browser settings may include local configuration parameters, user preference settings, and memory data, some of these settings are of high importance and require careful modification. For example, memory data settings may affect the browser's operating logic. For instance, if a webpage's certificate expires, preventing the browser from generating access, users might modify the memory data to allow the browser to temporarily bypass the certificate expiration verification step and directly access the webpage if they need to debug the browser. Understandably, such a change could lead to the browser accessing malicious or insecure webpages, potentially resulting in attacks on the terminal device. Therefore, these types of data require more caution when modifying.
[0075] Therefore, the browser debugging device can set all or some of the settings in the browser settings information to restricted modification parameters. Only users with modification permissions can modify these restricted modification parameters. These restricted modification parameters can be the initial settings of the browser debugging device or set by relevant personnel. For example, all memory data can be set to restricted modification parameters. After determining the target setting parameter of the data modification command and obtaining the modification value in the data modification command, the browser debugging device can determine whether the target setting parameter is a restricted modification parameter. If the target setting parameter is not a restricted modification parameter, it can directly execute the steps to change the value of the target setting parameter to the modified value. Conversely, if the target setting parameter is a restricted modification parameter, the browser debugging device can perform modification permission verification for the user. This verification process determines whether the user has permission to modify the interface. If the user passes the permission verification, it means the user has modification permission; if the user fails the permission verification, it means the user does not have modification permission.
[0076] The modification permission verification process can be configured either as an initial setting of the browser debugging device or by relevant personnel. For example, the browser debugging device can display a modification verification window in the browser, with an input box allowing the user to enter modification permission verification information. After obtaining the user's input modification permission verification information, the browser debugging device can compare it with a whitelist. The whitelist stores modification permission verification information for all devices that support modifying restricted modification settings. If the user's input modification permission verification information exists in the whitelist, it can be determined that the user has modification permissions and the user has passed the modification permission verification process.
[0077] Optionally, the user's modification permission verification information can be different from the access permission verification information; that is, the modification permission verification information and the access permission verification information are two independent verification methods. Alternatively, the modification permission verification information can be related to the access permission verification information, and the user's modification permission verification information can be the same as the access permission verification information. When the browser's debugging device determines that the target setting parameter is a restricted modification setting parameter, it can obtain the access permission verification information previously entered by the user and determine whether the access permission verification information exists in the modification whitelist. If the access permission verification information exists in the modification whitelist, it means that the user's modification permission verification information is the same as the access permission verification information, and the user is directly determined to have passed the modification permission verification process. If the access permission verification information does not exist in the modification whitelist, then the user's modification permission verification process can be performed.
[0078] S206, change the value of the target setting parameter to the modified value.
[0079] Specifically, the browser debugging device can modify browser settings based on data modification commands, changing the value of the target setting parameter targeted by the data modification command to the value desired by the user.
[0080] Optionally, if the user passes the permission verification process, the browser debugging device will change the target setting parameter to the modified value.
[0081] S207 controls browser operation based on the modified browser settings.
[0082] Specifically, the browser debugging device controls the browser's operation directly based on the modified browser settings without requiring a browser restart. This allows users to view the modified browser's running status without restarting, thus enabling them to gradually optimize or adjust the browser while adjusting its settings.
[0083] S208, Generate target modification information based on data modification instructions and save the target modification information to the browser's history modification record.
[0084] Specifically, the browser debugging device can generate target modification information based on data modification instructions. This target modification information can include the user, the generation time of the data modification instruction, the modified target setting parameter, and the original and modified values of the target setting parameter. This target modification information is then saved to the browser's history modification record. The history modification record can store target modification information corresponding to all data modification instructions, thereby tracking all setting parameter modification operations. Furthermore, the browser debugging device can provide users with the ability to view the history modification record, allowing users to review and retrospectively review browser setting information modifications.
[0085] In this embodiment, a modification interface is created within the browser kernel to reduce the risk of data exposure and improve data acquisition efficiency. If a user's access instruction for the modification interface is received, access permission verification is performed. If the user passes the access permission verification, the modification interface is opened, displaying the browser's settings information, thus improving the security of the browser settings. The system acquires the user's input modification instruction for the modification interface, determines the target setting parameter, and obtains the modification value from the instruction. A secondary confirmation can be provided to the user before modification to prevent accidental operation. Modification parameters can be restricted, and user modification permissions can be verified to prevent important settings from being incorrectly changed, leading to browser vulnerabilities or malfunctions. The target setting parameter value is changed to the modified value, and the browser operation is controlled based on the modified browser settings. Displaying all browser settings facilitates users' viewing and modification of browser status data, and the browser can run directly with the modified settings without restarting, ensuring a normal workflow for browser debugging and improving debugging efficiency. Target modification information is generated based on the data modification instruction and saved to the browser's historical modification record for user review and retrospective analysis of browser settings modifications.
[0086] The following will be combined with the appendix Figure 5 -Appendix Figure 6 This application provides a detailed description of the browser debugging device provided in its embodiments. It should be noted that the appendix... Figure 5 -Appendix Figure 6 The browser debugging device in the document is used to execute this application. Figures 1-4 The methods shown in the embodiments are for illustrative purposes only, illustrating the parts relevant to the embodiments of this application. For specific technical details not disclosed, please refer to this application. Figures 1-4 The example shown.
[0087] Please see Figure 5 This illustration shows a schematic diagram of a browser debugging device provided in an exemplary embodiment of this application. The browser debugging device can be implemented as all or part of a device through software, hardware, or a combination of both. The device 1 includes an interface display unit 11, an instruction acquisition unit 12, and a modification processing unit 13.
[0088] The interface display unit 11 is used to open the browser's modification interface based on the user's access command, and to display the browser's browser settings information on the modification interface.
[0089] Instruction acquisition unit 12 is used to acquire the data modification instruction input by the user for the modification interface;
[0090] The modification processing unit 13 is used to modify the browser settings information based on the data modification instruction, and control the browser to run according to the modified browser settings information.
[0091] In this embodiment, the browser's modification interface is opened based on the user's access command. The browser's settings information is displayed on this interface. The user's data modification command input to the modification interface is obtained, and the browser settings information is modified based on this command. The browser is then controlled to run according to the modified settings. Displaying all browser settings facilitates the user's viewing and modification of browser status data, and the browser runs directly with the modified settings without requiring a restart. This ensures a smooth workflow for browser debugging and improves debugging efficiency.
[0092] Please see Figure 6 This illustration shows a schematic diagram of a browser debugging device provided in an exemplary embodiment of this application. The browser debugging device can be implemented as all or part of a device through software, hardware, or a combination of both. Device 1 includes an interface creation unit 14, an interface display unit 11, an instruction acquisition unit 12, a modification processing unit 13, and a modification record generation unit 15.
[0093] Interface creation unit 14 is used to create and modify the interface in the browser kernel.
[0094] The interface display unit 11 is used to open the browser's modification interface based on the user's access command, and to display the browser's browser settings information on the modification interface.
[0095] Optionally, the browser settings information includes the browser's local configuration parameters, user preference settings parameters, and memory data.
[0096] Optionally, the interface display unit 11 is specifically used to perform access permission verification processing on the user if it receives an access instruction from the user to modify the interface.
[0097] If the user passes the access permission verification, the modification interface is opened, and the browser settings information of the browser is displayed on the modification interface.
[0098] Optionally, the interface display unit 11 is specifically used to display an access verification window in the browser and obtain the access permission verification information input by the user in response to the access verification window;
[0099] If the access permission verification information exists in the access whitelist, then the user is determined to have passed the access permission verification process.
[0100] Instruction acquisition unit 12 is used to acquire the data modification instruction input by the user for the modification interface;
[0101] The modification processing unit 13 is used to modify the browser settings information based on the data modification instruction, and control the browser to run according to the modified browser settings information.
[0102] Optionally, the modification processing unit 13 is specifically used to determine the target setting parameters targeted by the data modification instruction and to obtain the modification value in the data modification instruction;
[0103] Change the value of the target setting parameter to the modified value.
[0104] Modify the record generation unit 15, which is used to generate target modification information based on the data modification instruction;
[0105] The target modification information is saved to the browser's history modification record.
[0106] In this embodiment, a modification interface is created within the browser kernel to reduce the risk of data exposure and improve data acquisition efficiency. If a user's access command for the modification interface is received, access permission verification is performed. If the user passes the access permission verification, the modification interface is opened, displaying the browser's settings information, thus improving the security of the browser settings. The system acquires the user's data modification command for the modification interface, determines the target setting parameter, and obtains the modification value from the command. A secondary confirmation can be provided to the user before modification to prevent accidental operation. Restrictions on modification parameters can be set, and user modification permissions can be verified to prevent important settings from being incorrectly changed, leading to browser vulnerabilities or malfunctions. The target setting parameter value is changed to the modified value, and the browser operation is controlled based on the modified browser settings. Displaying all browser settings facilitates users' viewing and modification of browser status data, and the browser can run directly with the modified settings without restarting, ensuring a normal workflow for browser debugging and improving debugging efficiency. Target modification information is generated based on the data modification command and saved to the browser's historical modification record for user review and retrospective analysis of browser settings modifications.
[0107] It should be noted that the browser debugging device provided in the above embodiments is only illustrated by the division of the above functional modules when executing the browser debugging method. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the browser debugging device and the browser debugging method embodiments provided in the above embodiments belong to the same concept, and the implementation process is detailed in the method embodiments, which will not be repeated here.
[0108] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.
[0109] This application also provides a computer storage medium that can store multiple instructions, which are adapted to be loaded and executed by a processor as described above. Figures 1-4 The browser debugging method described in the illustrated embodiment can be found in the following documentation for a detailed execution process: Figures 1-4 The specific details of the illustrated embodiments will not be elaborated here.
[0110] This application also provides a computer program product storing at least one instruction, which is loaded and executed by the processor as described above. Figures 1-4 The browser debugging method described in the illustrated embodiment can be found in the following documentation for a detailed execution process: Figures 1-4 The specific details of the illustrated embodiments will not be elaborated here.
[0111] Please refer to Figure 7 This diagram illustrates a structural block diagram of an electronic device provided in an exemplary embodiment of this application. The electronic device in this application may include one or more components such as a processor 110, a memory 120, an input device 130, an output device 140, and a bus 150. The processor 110, memory 120, input device 130, and output device 140 may be connected via the bus 150.
[0112] Processor 110 may include one or more processing cores. Processor 110 connects to various parts of the electronic device using various interfaces and lines, and executes various functions of terminal 100 and processes data by running or executing instructions, programs, code sets, or instruction sets stored in memory 120, and by calling data stored in memory 120. Optionally, processor 110 may be implemented using at least one hardware form of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), or Programmable Logic Array (PLA). Processor 110 may integrate one or more of the following: Central Processing Unit (CPU), Graphics Processing Unit (GPU), and modem. The CPU primarily handles the operating system, user page, and applications; the GPU is responsible for rendering and drawing the displayed content; and the modem handles wireless communication. It is understood that the modem may also not be integrated into processor 110 and may be implemented separately using a communication chip.
[0113] The memory 120 may include random access memory (RAM) or read-only memory (ROM). Optionally, the memory 120 may include non-transitory computer-readable storage medium. The memory 120 may be used to store instructions, programs, code, code sets, or instruction sets. The memory 120 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for implementing at least one function (such as touch function, sound playback function, image playback function, etc.), instructions for implementing the various method embodiments described above, etc. The operating system may be the Android system, including systems deeply developed based on the Android system, the iOS system developed by Apple Inc., including systems deeply developed based on the iOS system, or other systems.
[0114] The memory 120 can be divided into operating system space and user space. The operating system runs in the operating system space, while native and third-party applications run in user space. To ensure that different third-party applications can achieve good running performance, the operating system allocates corresponding system resources for each application. However, different application scenarios within the same third-party application have different requirements for system resources. For example, in local resource loading scenarios, third-party applications have high requirements for disk read speed; in animation rendering scenarios, third-party applications have high requirements for GPU performance. Since the operating system and third-party applications are independent of each other, the operating system often cannot promptly perceive the current application scenario of a third-party application, resulting in the operating system's inability to adapt system resources accordingly.
[0115] In order for the operating system to distinguish the specific application scenarios of third-party applications, it is necessary to establish data communication between the third-party applications and the operating system. This would allow the operating system to obtain the current scenario information of the third-party applications at any time, and then perform targeted system resource adaptation based on the current scenario.
[0116] The input device 130 is used to receive input instructions or data, and includes, but is not limited to, a keyboard, mouse, camera, microphone, or touch device. The output device 140 is used to output instructions or data, and includes, but is not limited to, a display device and a speaker. In one example, the input device 130 and the output device 140 can be combined, and the input device 130 and the output device 140 can be a touch display screen.
[0117] The touch display screen can be designed as a full-screen, curved screen, or irregularly shaped screen. It can also be designed as a combination of a full-screen and a curved screen, or a combination of an irregularly shaped screen and a curved screen; however, this application does not limit the specific design in this regard.
[0118] In addition, those skilled in the art will understand that the structure of the electronic device shown in the above figures does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown, or combine certain components, or have different component arrangements. For example, the electronic device may also include radio frequency circuits, input units, sensors, audio circuits, Wireless Fidelity (WiFi) modules, power supplies, Bluetooth modules, etc., which will not be described in detail here.
[0119] exist Figure 7 In the illustrated electronic device, processor 110 can be used to call a browser debugging application stored in memory 120 and specifically perform the following operations:
[0120] The browser's modification interface is opened based on the user's access command, and the browser settings information of the browser is displayed on the modification interface.
[0121] Obtain the data modification instructions input by the user on the modification interface;
[0122] The browser settings are modified based on the data modification instructions, and the browser is controlled to run according to the modified browser settings.
[0123] In one embodiment, the browser settings information includes the browser's local configuration parameters, user preference settings parameters, and memory data.
[0124] In one embodiment, when the processor 110 executes a user-based access command to open a modification interface in the browser kernel and displays the browser settings information on the modification interface, it specifically performs the following operations:
[0125] If a user's access instruction to modify the interface is received, then an access permission verification process is performed on the user.
[0126] If the user passes the access permission verification, the modification interface is opened, and the browser settings information of the browser is displayed on the modification interface.
[0127] In one embodiment, when the processor 110 performs access permission verification for the user, it specifically performs the following operations:
[0128] Display an access verification window in the browser and obtain the access permission verification information entered by the user in the access verification window;
[0129] If the access permission verification information exists in the access whitelist, then the user is determined to have passed the access permission verification process.
[0130] In one embodiment, when the processor 110 executes the modification processing of the browser settings information based on the data modification instruction, it specifically performs the following operations:
[0131] Determine the target setting parameters for the data modification instruction, and obtain the modification value in the data modification instruction;
[0132] Change the value of the target setting parameter to the modified value.
[0133] In one embodiment, before executing the user-initiated access command to open the browser's modified interface, the processor 110 also performs the following operations:
[0134] Create and modify the interface within the browser engine.
[0135] In one embodiment, when executing the browser debugging method, the processor 110 also performs the following operations:
[0136] Generate target modification information based on the data modification instructions;
[0137] The target modification information is saved to the browser's history modification record.
[0138] In this embodiment, a modification interface is created within the browser kernel to reduce the risk of data exposure and improve data acquisition efficiency. If a user's access command for the modification interface is received, access permission verification is performed. If the user passes the access permission verification, the modification interface is opened, displaying the browser's settings information, thus improving the security of the browser settings. The system acquires the user's data modification command for the modification interface, determines the target setting parameter, and obtains the modification value from the command. A secondary confirmation can be provided to the user before modification to prevent accidental operation. Restrictions on modification parameters can be set, and user modification permissions can be verified to prevent important settings from being incorrectly changed, leading to browser vulnerabilities or malfunctions. The target setting parameter value is changed to the modified value, and the browser operation is controlled based on the modified browser settings. Displaying all browser settings facilitates users' viewing and modification of browser status data, and the browser can run directly with the modified settings without restarting, ensuring a normal workflow for browser debugging and improving debugging efficiency. Target modification information is generated based on the data modification command and saved to the browser's historical modification record for user review and retrospective analysis of browser settings modifications.
[0139] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. The storage medium can be a magnetic disk, optical disk, read-only memory, or random access memory, etc.
[0140] The above-disclosed embodiments are merely preferred embodiments of this application and should not be construed as limiting the scope of this application. Therefore, any equivalent variations made in accordance with the claims of this application shall still fall within the scope of this application.
[0141] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.), and signals involved in the embodiments of this specification are all authorized by the user or fully authorized by all parties, and the collection, use, and processing of related data must comply with the relevant laws, regulations, and standards of the relevant countries and regions. For example, browser settings information, access permission information, etc. involved in this specification were obtained under full authorization.
Claims
1. A browser debugging method, characterized in that, The method includes: The browser's modification interface is opened based on the user's access command, and the browser settings information of the browser is displayed on the modification interface. Obtain the data modification instructions input by the user on the modification interface; The browser settings are modified based on the data modification instructions, and the browser is controlled to run according to the modified browser settings.
2. The method according to claim 1, characterized in that, The browser settings information includes the browser's local configuration parameters, user preference settings parameters, and memory data.
3. The method according to claim 1, characterized in that, The modification interface in the browser kernel is opened based on the user's access command, and the browser settings information of the browser is displayed on the modification interface, including: If a user's access instruction to modify the interface is received, then an access permission verification process is performed on the user. If the user passes the access permission verification, the modification interface is opened, and the browser settings information of the browser is displayed on the modification interface.
4. The method according to claim 3, characterized in that, The access permission verification process for the user includes: Display an access verification window in the browser and obtain the access permission verification information entered by the user in the access verification window; If the access permission verification information exists in the access whitelist, then the user is determined to have passed the access permission verification process.
5. The method according to claim 1, characterized in that, The modification of browser settings based on the data modification instruction includes: Determine the target setting parameters for the data modification instruction, and obtain the modification value in the data modification instruction; Change the value of the target setting parameter to the modified value.
6. The method according to claim 1, characterized in that, Before opening the browser's modification interface based on the user's access command, the process also includes: Create and modify the interface within the browser engine.
7. The method according to claim 1, characterized in that, The method further includes: Generate target modification information based on the data modification instructions; The target modification information is saved to the browser's history modification record.
8. A browser debugging device, characterized in that, The device includes: The interface display unit is used to open the browser's modification interface based on the user's access command, and to display the browser's browser settings information on the modification interface. The instruction acquisition unit is used to acquire the data modification instruction input by the user for the modification interface; The modification processing unit is used to modify the browser settings information based on the data modification instruction, and control the browser to run according to the modified browser settings information.
9. A computer storage medium, characterized in that, The computer storage medium stores a plurality of instructions, which are adapted to be loaded by a processor and executed as method steps as claimed in any one of claims 1 to 7.
10. An electronic device, characterized in that, include: A processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and executed the method steps as claimed in any one of claims 1 to 7.