Shortcut key compatible method and device for browser environment and medium

Abstract

The invention discloses a shortcut key compatibility method and device for a browser environment and a medium, and the method comprises the steps: recognizing an available browser shortcut key and a designer shortcut key when a designer is initialized; comparing the browser shortcut key with the designer shortcut key to obtain a shortcut key conflict combination; the shortcut key conflict combination comprises a conflict browser shortcut key and a conflict designer shortcut key; analyzing the shortcut key conflict combination, and adjusting a conflict designer shortcut key; in the operation process of the designer, when shortcut key conflicts are monitored, determining conflicting shortcut keys; and according to the conflict scene and a temporary shortcut key locking mechanism, performing priority analysis on the conflict shortcut key, and determining an effective object of the conflict shortcut key. In the design initialization stage, a shortcut key for conflicting between the designer and the browser is automatically adjusted, and in the operation process of the designer, conflicts between the designer and the browser and between the designer and the component shortcut key are automatically solved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a shortcut key compatibility method, device and medium for a browser environment. Background Art

[0002] When developing large-screen designers, shortcut keys are an important means to improve user operation efficiency. However, designers running in a browser environment often face shortcut key conflicts, because the browser itself has defined a series of shortcut keys, and the designer and components on the canvas may also need to use shortcut keys. Such conflicts not only reduce the smoothness of user operations, but may also cause problems such as misoperation and data loss.

[0003] At present, the methods for handling shortcut key conflicts are mostly limited to simple shortcut key modification or cancellation, and lack a systematic compatibility solution. Therefore, these methods can often only solve partial conflicts and easily introduce new conflict points. In addition, components dragged into the designer will also cause shortcut key conflicts. Therefore, it is impossible to efficiently and accurately achieve shortcut key compatibility for the browser environment. Summary of the invention

[0004] The embodiments of the present application provide a method, device and medium for shortcut key compatibility for a browser environment, which are used to solve the problem that shortcut key compatibility for a browser environment cannot be achieved efficiently and accurately.

[0005] The present application embodiment adopts the following technical solutions:

[0006] On the one hand, an embodiment of the present application provides a shortcut key compatibility method for a browser environment, the method comprising: when the designer is initialized, identifying available browser shortcut keys and designer shortcut keys; comparing the browser shortcut keys and the designer shortcut keys to obtain a shortcut key conflict combination; the shortcut key conflict combination includes a conflicting browser shortcut key and a conflicting designer shortcut key; analyzing the shortcut key conflict combination and adjusting the conflicting designer shortcut key; during the operation of the designer, monitoring the browser shortcut keys, designer shortcut keys and component shortcut keys, and determining the conflicting shortcut keys when a shortcut key conflict is detected; performing a priority analysis on the conflicting shortcut keys based on the conflict scenario and the temporary shortcut key locking mechanism, and determining the effective objects of the conflicting shortcut keys.

[0007] In one example, analyzing the shortcut key conflict combination and adjusting the conflict designer shortcut key specifically includes: retrieving the user's operation preference list in a preference database; determining the target key with the highest preference level in the operation preference list; adding the target key to the conflict designer shortcut key to determine the automatic change content; sending the shortcut key conflict combination and the automatic change content to the user, and adjusting the conflict designer shortcut key according to the user's operation result.

[0008] In one example, adjusting the conflict designer shortcut key according to the user's operation result specifically includes: when the user confirms the automatic change content, outputting the automatic change content to the shortcut key change queue; when traversing the shortcut key change queue, updating the setting of the conflict designer shortcut key according to the automatic change content to adjust the conflict designer shortcut key.

[0009] In one example, the method further includes: when the user has not confirmed the automatic change content, obtaining the designer shortcut key to be changed according to the user's customized change content for the conflicting designer shortcut key; comparing the designer shortcut key to be changed with the browser shortcut key, and when there is no conflict, outputting the customized change content to the shortcut key change queue; when traversing the shortcut key change queue, updating the setting of the conflicting designer shortcut key according to the customized change content to adjust the conflicting designer shortcut key.

[0010] In one example, before retrieving the user's operation preference list in the preference database, the method also includes: obtaining the user's historical shortcut keys in the designer within a preset period; counting the number of occurrences of each key in the historical shortcut keys; matching the number of occurrences in a pre-constructed preference level table to obtain the preference level of each key; and generating the user's operation preference list based on the identification and preference level of each key.

[0011] In one example, the conflicting shortcut keys are prioritized and analyzed based on the conflict scenarios and the temporary shortcut key locking mechanism to determine the objects in which the conflicting shortcut keys are effective, specifically including: determining whether the mouse is in the design area of ​​the designer; when the mouse is not in the design area of ​​the designer, determining whether the conflicting shortcut key is effective in the browser; when the mouse is in the design area of ​​the designer, determining whether there is a component selected and in editing state in the design area; if not, determining whether to enable the temporary shortcut key locking mechanism; when enabling the temporary shortcut key locking mechanism, determining that the conflicting shortcut key is effective in the designer; when disabling the temporary shortcut key locking mechanism, determining that the conflicting shortcut key is disabled in the component, and performing conflicting shortcut key response actions according to the priority between the designer and the browser.

[0012] In one example, the conflicting shortcut key response action is performed based on the priority of the designer and the browser, specifically including: determining that the priority of the designer is higher than the browser; determining whether the conflicting shortcut key exists in the designer; if so, responding to the action of the conflicting shortcut key in the designer; if not, responding to the action of the conflicting shortcut key in the browser.

[0013] In one example, the method also includes: if there is a component that is selected and in editing state, determining whether the mouse is in the component area; when the mouse is in the component area, determining whether a temporary shortcut key locking mechanism is enabled; when the temporary shortcut key locking mechanism is enabled, determining whether the conflicting shortcut key is effective in the component; when the temporary shortcut key locking mechanism is disabled, performing a response operation according to the priority of the conflicting shortcut keys in the designer, browser, and component.

[0014] On the other hand, an embodiment of the present application provides a shortcut key compatible device for a browser environment, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute any one of the shortcut key compatible methods for a browser environment described above.

[0015] On the other hand, an embodiment of the present application provides a shortcut key compatible non-volatile computer storage medium for a browser environment, storing computer executable instructions, and the computer executable instructions can execute any of the shortcut key compatible methods for a browser environment described above.

[0016] At least one of the above technical solutions adopted in the embodiments of the present application can achieve the following beneficial effects:

[0017] In the design initialization phase, by performing conflict analysis on available browser shortcuts and designer shortcuts, the designer automatically adjusts the shortcuts that conflict with the browser, and automatically resolves the conflicts between the designer shortcuts and the browser shortcuts in advance. Furthermore, during the operation of the designer, shortcut conflicts are monitored, so that different priorities are set between the browser, component and designer in different conflict scenarios, and then combined with the temporary shortcut lock mechanism of the designer, the effective objects of the conflicting shortcuts are automatically adjusted, so as to automatically resolve the conflicts between the designer shortcuts and the browser and component shortcuts, and finally realize the automatic, real-time and efficient implementation of the shortcut compatibility scenario of the browser environment, ensuring the smoothness and efficiency of user operations. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the technical solution of the present application, some embodiments of the present application will be described in detail below in conjunction with the accompanying drawings, in which:

[0019] Figure 1 A flowchart of a shortcut key compatibility method for a browser environment provided in an embodiment of the present application;

[0020] Figure 2 A schematic diagram of a conflict scenario provided in an embodiment of the present application;

[0021] Figure 3 A schematic diagram of a shortcut key compatible system for a browser environment provided in an embodiment of the present application;

[0022] Figure 4 A workflow diagram of a context awareness module provided in an embodiment of the present application;

[0023] Figure 5 A schematic diagram of the structure of a shortcut key compatible device for a browser environment provided in an embodiment of the present application. DETAILED DESCRIPTION

[0024] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.

[0025] Some embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0026] Figure 1 A flowchart of a shortcut key compatibility method for a browser environment provided in an embodiment of the present application. The method can be applied to different business fields, such as the Internet financial business field, the e-commerce business field, the instant messaging business field, the game business field, the official business field, etc. Certain input parameters or intermediate results in the process allow manual intervention and adjustment to help improve accuracy.

[0027] The analysis method involved in the embodiments of the present application can be implemented by a terminal device or a server, and the present application does not impose any special restrictions on this. For the convenience of understanding and description, the following embodiments are described in detail by taking a server as an example.

[0028] It should be noted that the server may be a single device or a system consisting of multiple devices, that is, a distributed server, and this application does not make any specific limitation on this.

[0029] Figure 1 The process in includes the following steps:

[0030] S101: When the designer is initialized, identifying available browser shortcut keys and designer shortcut keys.

[0031] It should be noted that when the designer is initialized, the component shortcut keys cannot be recognized, but when the component takes effect, the component shortcut keys can be recognized. Therefore, when the designer is initialized, all available browser shortcut keys and designer shortcut keys in the browser environment are automatically recognized.

[0032] S102: Compare the browser shortcut key and the designer shortcut key to obtain a shortcut key conflict combination; the shortcut key conflict combination includes a conflicting browser shortcut key and a conflicting designer shortcut key.

[0033] For example, Ctrl+A selects all page elements in the browser, but selects all components in the designer. In this case, Ctrl+A in the browser conflicts with the browser shortcut key, while Ctrl+A in the designer conflicts with the designer shortcut key.

[0034] S103: Analyze the shortcut key conflict combination and adjust the conflict designer shortcut key.

[0035] In some embodiments of the present application, since different users have different usage habits and common operations, the conflicting designer shortcut keys are automatically changed to avoid conflicts by considering the user's usage preferences for each key. In other words, the designer's shortcut key settings are intelligently adjusted to avoid conflicts.

[0036] Based on this, first, the user's operation preference list is retrieved in the preference database. Then, in the operation preference list, the target key with the highest preference level is determined. Then, the target key is added to the conflict designer shortcut key to determine the automatic change content. Finally, the shortcut key conflict combination and the automatic change content are sent to the user, and the conflict designer shortcut key is adjusted according to the user's operation result.

[0037] It should be noted that the operation preference list needs to be built in advance. The process is as follows:

[0038] First, within a preset period, obtain the user's historical shortcut keys in the designer. Then, count the number of occurrences of each key in the historical shortcut keys. Then, match the number of occurrences in the pre-built preference level table to obtain the preference level of each key. Finally, generate the user's operation preference list based on the identification and preference level of each key.

[0039] It should be noted that the more times a key appears, the higher the preference level. For example, the A key has the highest preference level, and the automatic content change can be determined as Ctrl+Alt+A.

[0040] Furthermore, the automatically changed content needs to be confirmed to the user.

[0041] Based on this, when the user confirms the automatic change content, the automatic change content is output to the shortcut key change queue. Then, when the shortcut key change queue is traversed, the setting of the conflict designer shortcut key is updated according to the automatic change content to adjust the conflict designer shortcut key.

[0042] It should be noted that the function of providing user-defined shortcut keys allows users to reset the designer's shortcut keys according to their own usage habits, ensuring the personalization and compatibility of the shortcut keys.

[0043] Based on this, when the user does not confirm the automatic change content, the designer shortcut key to be changed is obtained according to the user's customized change content for the conflicting designer shortcut key. Then, the designer shortcut key to be changed is compared with the browser shortcut key.

[0044] It should be noted that after the user customizes the shortcut key, the customized shortcut key content needs to be compared with all available browser shortcut keys to determine whether there is a conflict.

[0045] Based on this, when there is no conflict, the customized change content is output to the shortcut key change queue. Then, when the shortcut key change queue is traversed, the setting of the conflict designer shortcut key is updated according to the customized change content to adjust the conflict designer shortcut key.

[0046] It should be noted that, if there is still a conflict, the newly generated shortcut key conflict combination is analyzed again.

[0047] S104: During the running of the designer, the browser shortcut keys, the designer shortcut keys and the component shortcut keys are monitored, and when a shortcut key conflict is detected, the conflicting shortcut keys are determined.

[0048] In some embodiments of the present application, it is monitored whether the shortcut key is activated, and when activated, if there is a conflict, the shortcut key is determined as a conflicting shortcut key. It should be noted that when the user presses the shortcut key, it is determined that the shortcut key is activated.

[0049] For example, use the document.onkeydown method in JS to monitor whether the shortcut key is activated.

[0050] It should be noted that, since the conflict between the browser shortcut keys and the designer shortcut keys has been pre-adjusted, the conflict at this time is usually a conflict between the browser shortcut keys and the component shortcut keys, or a conflict between the designer shortcut keys and the component shortcut keys.

[0051] S105: According to the conflict scenario and the temporary shortcut key locking mechanism, priority analysis is performed on the conflicting shortcut keys to determine the effective objects of the conflicting shortcut keys.

[0052] In some embodiments of the present application, different priorities are set for shortcut keys in different scenarios. For example, the priority of shortcut keys inside the designer is higher than that of browser shortcut keys, to ensure that when a conflict occurs, the designer's operational requirements are responded to first.

[0053] First, determine whether the mouse is in the design area of ​​the designer.

[0054] On the one hand, when the mouse is not in the design area of ​​the designer, it is determined that the conflicting shortcut keys are effective in the browser.

[0055] It should be noted that when the conflicting shortcut key is in effect in the browser, when the browser has a conflicting shortcut key, the action of the conflicting shortcut key in the browser is responded to. This means that the conflicting shortcut key exists between the browser and the component, but since the component is not in effect, the action in the component is not responded to at this time.

[0056] When the browser does not have a conflicting shortcut key, no action will be responded to the conflicting shortcut key currently triggered by the user, indicating that the conflicting shortcut key is between the designer and the component. However, since the designer and the component are not effective, no action will be responded to at this time.

[0057] On the other hand, when the mouse is in the design area of ​​the designer, it is determined whether there is a component in the design area that is selected and in an editing state.

[0058] If it does not exist, determine whether to enable the temporary shortcut key locking mechanism.

[0059] When the temporary shortcut lock mechanism is turned on, make sure that the conflicting shortcuts are in effect in the designer.

[0060] It should be noted that when the conflicting shortcut key is in effect in the designer, when the designer has a conflicting shortcut key, the action of the conflicting shortcut key in the designer is responded to. This means that the conflicting shortcut key exists between the designer and the component, but since the component is not in effect, the action in the component is not responded to at this time.

[0061] When the designer does not have conflicting shortcut keys, no action will be taken for the conflicting shortcut keys currently triggered by the user. This means that the conflicting shortcut keys exist between the browser and the component, but since the browser and the component are not effective, no action will be taken at this time.

[0062] When the temporary shortcut key locking mechanism is turned off, it is determined that the conflicting shortcut keys are disabled in the component, and the conflicting shortcut key response action is performed according to the priority between the designer and the browser.

[0063] The process of responding to conflicting shortcut keys based on the priority between the designer and the browser is as follows:

[0064] First, determine whether the designer has a higher priority than the browser. Then, determine whether there are conflicting shortcut keys in the designer.

[0065] If so, respond to the conflicting shortcut key action in the designer.

[0066] If not, respond to the conflicting shortcut key action in the browser.

[0067] It should be noted that when the designer has a conflicting shortcut key, it means that the conflicting shortcut key is actually a conflict between the component and the designer, but since the component is disabled, the component's actions are not responded to. Respond to the actions of the conflicting shortcut key in the designer.

[0068] When the designer does not have a conflicting shortcut key, it means that the conflicting shortcut key is actually a conflict between the browser and the component. However, since the component is disabled, it does not respond to the component's actions, but responds to the actions of the conflicting shortcut key in the browser.

[0069] On the other hand, when there is a component that is selected and in an editing state in the design area, it is determined whether the mouse is in the component area.

[0070] When the mouse is in the component area, determine whether to enable the temporary shortcut key locking mechanism.

[0071] When the temporary shortcut lock mechanism is enabled, make sure that the conflicting shortcuts are in effect in the component.

[0072] It should be noted that when the conflicting shortcut key is effective in the component, if the component has a conflicting shortcut key, the action of the conflicting shortcut key in the component is responded to. When the component does not have a conflicting shortcut key, no action is responded to the conflicting shortcut key currently triggered by the user.

[0073] When the temporary shortcut key locking mechanism is turned off, response operations are performed based on the priority of conflicting shortcut keys in the designer, browser, and component.

[0074] The process of responding to the priorities of the conflicting shortcut keys in the designer, browser, and component is as follows:

[0075] First, make sure that the component takes precedence over the designer, and the designer takes precedence over the browser.

[0076] Then, it is determined whether there are conflicting shortcut keys in the component.

[0077] If so, respond to the conflicting shortcut key action in the component.

[0078] If not, respond to the conflicting shortcut key action in the designer.

[0079] It should be noted that when the conflicting shortcut key is in a component, it means that the conflict exists between the component and the browser or between the component and the designer. Since the component has a high priority, the action in the component that responds to the conflicting shortcut key is performed.

[0080] In addition, when the conflicting shortcut key is not in the component, it means that the conflict exists between the designer and the browser. This situation means that during the initialization process, the conflict between the conflicting shortcut key and the browser was not detected. This is relatively rare because the designer has a high priority. Therefore, respond to the action of the conflicting shortcut key in the designer.

[0081] It should be noted that when a shortcut key conflict is detected, a conflict log will be generated. After the designer runs to the end, the conflict log will be notified to the user in the form of a pop-up window, log, etc., so that the user can change the conflicting shortcut keys.

[0082] In summary, through intelligent conflict detection and resolution strategies, as well as user-defined shortcut key functions, the conflicts between designer shortcut keys and browser shortcut keys and component shortcut keys can be effectively resolved, while taking into account the shortcut key compatibility of the components dragged into the designer, thereby enhancing the flexibility and personalization of the designer, and improving the user operation experience and data security.

[0083] In other words, it can effectively solve the shortcut key conflict problem encountered by the large-screen designer during the development process, and improve the fluency and efficiency of user operations. At the same time, through intelligent conflict detection and resolution strategies, as well as the function of user-defined shortcut keys, the flexibility and personalization of the designer are further enhanced. In addition, the shortcut key compatibility of the components dragged into the designer is also taken into account, ensuring the stability and reliability of the entire designer system. At the same time, it is also highly scalable and maintainable, which facilitates continuous optimization and upgrading based on user feedback and market demand.

[0084] It should be noted that although the embodiments of the present application are based on Figure 1 Steps S101 to S105 are described in sequence, but this does not mean that steps S101 to S105 must be performed in a strict order. Figure 1The order shown in the figure is to introduce and explain step S101 to step S105 in sequence, in order to facilitate those skilled in the art to understand the technical solution of the embodiment of the present application. In other words, in the embodiment of the present application, the order between step S101 to step S105 can be appropriately adjusted according to actual needs.

[0085] pass Figure 1 The method is to analyze the conflicts between the available browser shortcuts and designer shortcuts during the design initialization phase, so that the shortcuts that conflict with the browser are automatically adjusted in the designer, and the conflicts between the designer shortcuts and the browser shortcuts are automatically resolved in advance. Furthermore, during the operation of the designer, the shortcut conflicts are monitored, so that different priorities are set between the browser, the component and the designer in different conflict scenarios, and then the temporary shortcut lock mechanism of the designer is combined to automatically adjust the effective objects of the conflicting shortcuts, so as to automatically resolve the conflicts between the designer shortcuts and the browser and component shortcuts, and finally realize the shortcut compatibility scenario of the browser environment that can be automatically, real-time and efficiently realized, ensuring the fluency and efficiency of user operations.

[0086] More intuitively, Figure 2 A schematic diagram of a conflict scenario provided in an embodiment of the present application.

[0087] exist Figure 2 In the example, when the mouse is in the input box, pressing the ← key on the keyboard has three different results for the browser, designer, and component. For the browser, the possible result is URL rollback, for the designer, the target result is component left movement, and for the component itself, the text cursor left movement. These three results cause conflicts between shortcut keys.

[0088] More intuitively, Figure 3 A schematic diagram of a shortcut key compatible system for a browser environment provided in an embodiment of the present application.

[0089] exist Figure 3 In the system, the user interface layer, business logic layer and data access layer are included. The user interface layer includes the shortcut key setting panel, design area, status bar / notification area. The business logic layer includes the conflict detection module, status monitoring module, context awareness module, shortcut key management module and conflict resolution strategy module. The data access layer includes the conflict log, shortcut key configuration file and browser system interface.

[0090] Based on this, the conflict detection module is mainly responsible for real-time monitoring and detection of conflicts between designer shortcut keys and browser and component shortcut keys. The conflict detection module runs when the designer is just started and during the design operation.

[0091] The status monitoring module uses the document.onkeydown method in JS to monitor whether the shortcut key is activated, and then switches to the context awareness module after activation.

[0092] The context-aware module can dynamically adjust the behavior of shortcut keys according to the user's current operation context (such as whether it is in the design area, whether there are components in the editing state, etc.), and high-priority shortcut keys override conflicting shortcut keys. For example, in the editing state of a specific component, the component shortcut keys take precedence over the designer and browser shortcut keys, ensuring that more important functions can maintain their effectiveness when conflicts occur.

[0093] In addition, a temporary shortcut lock / unlock mechanism is provided, for example, to disable all responses of designer or browser shortcut keys.

[0094] The shortcut key management module provides a shortcut key setting interface for managing all available shortcut keys in the designer and allows users to customize the shortcut keys of the design tool according to their personal habits, ensuring the uniqueness and manageability of the shortcut keys.

[0095] Conflict resolution strategy module: During the design initialization process, it includes intelligent adjustment strategies and user-defined strategies.

[0096] Intelligent adjustment strategy: For detected conflicting shortcut keys, the system will intelligently adjust the designer's shortcut key settings based on the user's usage habits and common operations to avoid conflicts. Adjustment strategies include changing shortcut key combinations, increasing the complexity of shortcut keys, etc.

[0097] User customization strategy: Provides the function of user-defined shortcut keys, allowing users to reset the designer's shortcut keys according to their own usage habits, ensuring the personalization and compatibility of shortcut keys.

[0098] During the designer run, include the priority setting strategy.

[0099] Priority setting strategy: Use the context-aware module to set different priorities for shortcut keys in different scenarios. For example, the priority of the designer's internal shortcut keys is higher than the browser shortcut keys, ensuring that when a conflict occurs, the designer's operation needs are responded to first.

[0100] More intuitively, Figure 4 A workflow diagram of a context awareness module provided in an embodiment of the present application.

[0101] First, determine whether it is in the design area. If not, only the browser shortcut keys will take effect.

[0102] If so, determine whether there is a component selected and in editing state.

[0103] If it does not exist, determine whether to enable the temporary shortcut lock mechanism. When enabled, disable browser and component block shortcuts to ensure that shortcuts are only effective in the designer. When disabled, disable component shortcuts, and conflicting shortcuts have the highest priority in the designer, that is, other shortcuts are executed normally.

[0104] If it exists, determine whether it is within the component area.

[0105] If not, determine whether to enable the temporary shortcut lock mechanism. When enabled, disable browser and component block shortcuts to ensure that shortcuts are only effective in the designer. When disabled, disable component shortcuts, and conflicting shortcuts have the highest priority in the designer, that is, other shortcuts are executed normally.

[0106] If so, determine whether to enable the temporary shortcut lock mechanism. When enabled, disable the designer and browser shortcuts to ensure that the shortcuts are only effective in the component. When disabled, the conflicting shortcuts have the highest priority in the component, and other shortcuts are executed normally.

[0107] Based on the same idea, some embodiments of the present application also provide devices and non-volatile computer storage media corresponding to the above methods.

[0108] Figure 5 A schematic diagram of a structure of a shortcut key compatible device for a browser environment provided in an embodiment of the present application includes:

[0109] at least one processor; and,

[0110] a memory communicatively connected to the at least one processor; wherein,

[0111] The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute any one of the shortcut key compatibility methods for a browser environment described above.

[0112] Some embodiments of the present application provide a shortcut key compatible non-volatile computer storage medium for a browser environment, storing computer executable instructions, wherein the computer executable instructions can execute any of the shortcut key compatible methods for a browser environment described above.

[0113] Each embodiment in this application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device and medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.

[0114] The devices and media provided in the embodiments of the present application correspond one-to-one to the methods. Therefore, the devices and media also have similar beneficial technical effects as the corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be repeated here.

[0115] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

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

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

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

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

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

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

[0122] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0123] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the technical principle of the present application should all fall within the protection scope of the present application.

Claims

1. A shortcut key compatibility method for a browser environment, characterized in that: The method comprises: When the designer is initialized, identify available browser shortcuts and designer shortcuts; Compare the browser shortcut key and the designer shortcut key to obtain a shortcut key conflict combination; the shortcut key conflict combination includes a conflicting browser shortcut key and a conflicting designer shortcut key; Analyze the conflicting shortcut key combinations and adjust the conflicting designer shortcut keys; During the operation of the designer, the browser shortcut keys, the designer shortcut keys and the component shortcut keys are monitored, and when a shortcut key conflict is detected, the conflicting shortcut keys are determined; According to the conflict scenarios and the temporary shortcut key locking mechanism, the conflicting shortcut keys are prioritized and the objects for which the conflicting shortcut keys are effective are determined.

2. The method according to claim 1, characterized in that The analyzing the shortcut key conflict combination and adjusting the conflict designer shortcut key specifically includes: Retrieving the user's operation preference list from the preference database; In the operation preference list, determining the target key with the highest preference level; Adding the target key to the conflict designer shortcut key to determine the automatically changed content; The shortcut key conflict combination and the automatic change content are sent to the user, and the conflict designer shortcut keys are adjusted according to the user's operation results.

3. The method according to claim 2, characterized in that The adjusting the conflict designer shortcut keys according to the user's operation result specifically includes: When the user confirms the automatically changed content, outputting the automatically changed content to a shortcut key change queue; When the shortcut key change queue is traversed, the setting of the conflict designer shortcut key is updated according to the automatic change content to adjust the conflict designer shortcut key.

4. The method according to claim 3, characterized in that The method further comprises: When the user does not confirm the automatic change content, the designer shortcut key to be changed is obtained according to the user's customized change content for the conflicting designer shortcut key; Compare the designer shortcut key to be changed with the browser shortcut key, and when there is no conflict, output the customized change content to the shortcut key change queue; When the shortcut key change queue is traversed, the setting of the conflict designer shortcut key is updated according to the customized change content to adjust the conflict designer shortcut key.

5. The method according to claim 2, characterized in that: Before retrieving the user's operation preference list from the preference database, the method further includes: Within a preset period, obtaining the historical shortcut keys of the user in the designer; Count the number of occurrences of each key in the historical shortcut keys; In a pre-constructed preference level table, the occurrence counts are matched to obtain a preference level for each key; An operation preference list of the user is generated according to the identification and preference level of each key.

6. The method according to claim 1, characterized in that The priority analysis of the conflicting shortcut keys is performed according to the conflict scenario and the temporary shortcut key locking mechanism to determine the effective object of the conflicting shortcut keys, specifically including: Determine whether the mouse is in the design area of ​​the designer; When the mouse is not in the design area of ​​the designer, make sure that the conflicting shortcut keys are effective in the browser; When the mouse is in the design area of ​​the designer, determine whether there is a component in the design area that is selected and in an editing state; If it does not exist, determine whether to enable the temporary shortcut key locking mechanism; When the temporary shortcut key locking mechanism is enabled, it is determined that the conflicting shortcut key is effective in the designer; When the temporary shortcut key locking mechanism is turned off, it is determined that the conflicting shortcut key is disabled in the component, and a conflicting shortcut key response action is performed according to the priority between the designer and the browser.

7. The method according to claim 6, characterized in that The conflicting shortcut key response action is performed according to the priority of the designer and the browser, specifically including: Make sure the designer takes precedence over the browser; Determine whether the conflicting shortcut key exists in the designer; If so, responding to the action of the conflicting shortcut key in the designer; If not, respond to the action of the conflicting shortcut key in the browser.

8. The method according to claim 6, characterized in that The method further comprises: If there is a component that is selected and in editing state, determine whether the mouse is in the component area; When the mouse is in the component area, determine whether to enable the temporary shortcut key locking mechanism; When the temporary shortcut key locking mechanism is enabled, determining that the conflicting shortcut key is effective in the component; When the temporary shortcut key locking mechanism is turned off, response operations are performed based on the priority of conflicting shortcut keys in the designer, browser, and component.

9. A shortcut key compatible device for a browser environment, characterized in that: include: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the shortcut key compatibility method for a browser environment as described in any one of claims 1 to 8.

10. A shortcut key compatible non-volatile computer storage medium for a browser environment, storing computer executable instructions, characterized in that: The computer executable instructions can execute a shortcut key compatibility method for a browser environment as described in any one of claims 1 to 8.

Images