* eng: allow css nesting via postcss plugin
CSS nesting has landed in most browsers at this point, but we don't want
to break users who are still stuck on old browser (mainly older iOS
devices.) This PR adds a postcss plugin to the build process that
de-nests nested CSS.
The plugin required a newer version of postcss as well, so I have
updated that and a couple other modules to their latest versions.
* update build's package.json versions too
* no absolute positioning, scrolltop compute based on sticky lines.
* remove z-index var
* compute re-write, remove init, reduce pop-in
* dispose delayer
* remove debounce
* edge case for cell 0 header, next animation frame instead of debounce
* add delayer back, further improve pop in
* remove unused param, update testing snapshots
* testing: finish up coverage decorations
- Adds an inline decorator for empty-range branches
- Adds hover information for inline coverage hovers
- Fixes the editor not handling decorations that get after/before
content in `updateDecorationOptions`
- Adds an option `label` for branches
- A bunch of other misc tweaks to get coverage looking nice
- Keep decorations in sync if a user makes changes in editor
* update tests
This is the first pass at decorations in-editor. This PR doesn't
actually register the contribution, as it's not ready for selfhosting
yet. This PR creates decorations that look like this. The idea is that
coverage decorations in the glyph margin will always be visibile when
there's coverage, and users can get coverage in their code via hover or
shortcut, with the intention of making coverage unobtrusive and easy to
run all the time.
The notable thing is that there is now a third glyph margin row. I
reworked some of the editor code to handle this.
Some open questions:
- The glyph margin coverage wants doesn't need to be full-width, should
we add a new 'leftmost' glyph lane instead that's thinner?
- Adding breakpoints in files with coverage is a little annoying since
the breakpoint hint widget can expand the glyph margin on lines with
coverage, and jump back over otherwise. Probably we should never
decrease the number of lanes shown whenever the cursor is over the
glyph margin.
This continues on the coverage API I started a few years ago. It adds
initial integration where a "Show Test Coverage" tree item is shown in
the Test Results view, which then opens a dedicated Test Coverage view.
The Test Coverage view is a fairly basic tree view following the draft
design, with further improvements to come.
The 'bars' widget is also built in a reusable way such that it can be
integrated into the explorer, as this was a popular ask both inside and
outside the team.
For #123713.
* chore: rename color var for comment input box
also change the default color to inherit from input.background
* Keep using peekview title background and update editor too
---------
Co-authored-by: Alex Ross <alros@microsoft.com>
