* better lightbulb scenario for when we are very close to edge
* fix and change logic for last line
* clean up whitespace
* helper func, check whitespace
* remove extra model check
* add new logic for when blocked above and below
* remove whitespace
* Fix opening select boxes
This fixes a regression caused by #213465Closes#214303Closes#214345
* Fix another regression caused by #213465
---------
Co-authored-by: Benjamin Pasero <benjamin.pasero@microsoft.com>
* allow null value
* allow unsetting color
* undo change
* delete color
* undo changes
* remove unused code
* unset right map
* add function to create nullable color schema
* use nullable schema
* undo change
* fix nullable object
* use default value
* update both schemas on timeout
* simplifications & polish
---------
Co-authored-by: Martin Aeschlimann <martinae@microsoft.com>
* Allow to configure a list of encodings to use when guessing #36951
* Bump up the jschardet version into 3.1.2 #36951
* missing merge
* some polish
* renames
* some polish
* some polish
* cleanup
---------
Co-authored-by: Benjamin Pasero <benjamin.pasero@microsoft.com>
* Replace removeChild with remove
This replaces most uses of `parent.removeChild(child)` with
`child.remove()`.
The two are almost equivalent. The only difference is that
`parent.removeChild(child)` throws if the given node is not a child of
the parent, whereas `child.remove()` never throws. There is no noticable
performance difference. The only reason to use `removeChild` is to
support Internet Explorer, but that’s no longer supported by Monaco
editor.
* Fix broken CSP hash
The script content changed, so the sha256 hash changed too.
* Update src/vs/editor/browser/config/charWidthReader.ts
Co-authored-by: Logan Ramos <lramos15@gmail.com>
---------
Co-authored-by: Logan Ramos <lramos15@gmail.com>
Bug (previous behavior):
1.Press Ctrl+Shift+F to open the search panel.
2.Enter any text into the search input.
3.Press PageUp/PageDown.
4.The layout shifts to the right, hiding the line that indicates the current tab in the activity bar.
Solution:
When search results are displayed, pressing PageUp or PageDown now moves the cursor to the start or end of the search input, respectively. This is achieved by assigning specific functionality to these keys, overriding their default behavior of moving through the page.
Testing:
A smoke test was implemented to assess the fix. The test involves entering text into the search editor, pressing the PageUp and PageDown keys, and checking for any changes in the activity bar's layout.
