Bug 75362

At the moment HTMLRenderer (which is a JLabel subclass) takes in its own 
ComponentUI, which we cannot control.

It would be great if it either (and most ideally) opens up its ComponentUI 
(and register in UIDefaults the same way as other JComponent Classes do), or 
at least just simply provides more UIDefaults keys for customisation.

Scenario:

1) Even after setting every possible key to hint for anti-aliasing text, the 
text in HTMLRenderer (despite the fact that it does read in the attribute and 
does set a hint of AA text somewhere in the code) is never AAed.

2) In the case of Napkin we paint a special highlighter-style stroke to denote 
a highlighted component, and we did so by through ComponentUI.update(Graphics, 
JComponent); as that is not possible with HTMLRenderer (cannot force any 
external ComponentUI upon it since it is hard-coded in updateUI()), and the 
fact that it reads in colour information from standard JComponents (JTree, 
JTable etc.), making a trade-off of say simply setting the background colour 
to our highlighter's colour in the view tab trees will break JTree's UI in 
general. No way I'd call this a solution....