Bottom panel styling, more adaptive palette, shortcuts #937
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
vertical scrollbar on the right of the bottom panel (BP) removed
changed coordinates of the colour picker windows so they appear fully on the screen (previously, those windows were overflowing the editor's container)
the palette is more adaptive to the screenwidth (shrinking, showing less colours if doesn't fit) to prevent earlier scrollbar appearance
if necessary, the palette can be expanded (arrow button to the right), so the whole palette is available without scrolling the BP. The popup can be closed by clicking the same button or anywhere on the svgcanvas
BP's scrollbar's styling is the same as the styling of other toolbars
preventDefault was added to the selectAll shortcut to avoid selecting the whole editor content (as on screenshot) (usually this selection appears after clicking a button on any panel and selecting svg objects with ctrl+A after that)
also, preventDefault was added to rotation shortcuts (crtl+arrowLeft) because some browsers (e.g. OperaGX) are using this shortcut for navigation through routing history.
P.S. My Prettier configurations added some linebreaks to the edited files, but the
npm run lint
didn't catch it as an error, please let me know if I still should undo it.