If the "compatibility" label and browser width are just the wrong one, "break-word" can lead to browsers deciding to line-wrap every "ss" but *just the "ss" from "Dart Sass", "LibSass" and "Ruby Sass", which looks very strange and is quite hard to read.
Tables of contents are now statically rendered in their appropriately
open/closed states, rather than updated via JavaScript, so they render
correctly on the first page load. In order to make the "page sections"
table still usable without JS, this adds a stylesheet in a <noscript>
tag that forces the sections into an open state.
This gives us a place to disambiguate between implementation statuses
that refer to the entire feature under discussion, and those that just
refer to sub-features.
* Make the font smaller to make them less prominent and help visually
associate the callout with the list.
* Decrease the top margin to more clearly associate them with their
preceding header.
* Lighten the callout background when in another callout to make it
more visible.
* Animate the expand button.
