Use of 'transform: translateZ(0px);' in the cs-TabLayoutPanel class prevents subpixel anti-aliasing. Removing it doesn't seem to hurt anything, but allows the panel to subpixel anti-alias the text. It also removes an extra layer.

Changing the 'body' to 'position: absolute' instead of 'position: fixed' allows the rest of the text of the page to be subpixel anti-aliased and removes more layers.

Making these changes to allow code search results to render with subpixel anti-aliased text makes text easier to read, which is beneficial to users. 

These proposed changes may or may not cause issues with browsers other than Chromium, I haven't tested. Also, while I've used code search for a bit with these changes patched in, there may be corner cases I'm missing, which of course should be checked.

Of course, Chromium could do a better job of determining when to use subpixel anti-aliasing too.