You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 3, 2024. It is now read-only.
I've noticed that when attempting to select all via multi-clicking (2-4 clicks I think) that the syntax highlighter loses its formatting and can cause the page to scroll to the top and can take a long time before it re-renders. This appears to be the case with all SyntaxHighlighter implementations but embedded instances can cancel out the effect easily by clicking outside the pre/script affected. Unfortunately, since this extension is a full page instance it cannot really be clicked outside of.
I suppose an event handler could be used to overload the multi-clicking action and swallow the event. Not sure though.
Although not directly related to this bug it might be nice to add an event handler to listen to select all key events (e.g. Ctrl+A) to only select the contents of the container and not the gutter.
The text was updated successfully, but these errors were encountered:
I've noticed that when attempting to select all via multi-clicking (2-4 clicks I think) that the syntax highlighter loses its formatting and can cause the page to scroll to the top and can take a long time before it re-renders. This appears to be the case with all SyntaxHighlighter implementations but embedded instances can cancel out the effect easily by clicking outside the pre/script affected. Unfortunately, since this extension is a full page instance it cannot really be clicked outside of.
I suppose an event handler could be used to overload the multi-clicking action and swallow the event. Not sure though.
Although not directly related to this bug it might be nice to add an event handler to listen to select all key events (e.g. Ctrl+A) to only select the contents of the container and not the gutter.
The text was updated successfully, but these errors were encountered: