The thinking until now has been that
a client that creates a SWT.NONE-style Browser wouldn't/shouldn't care
what the native renderer is. Your case is more interesting though
since the various native browsers have well-known differences in this area.
Providing this API would be easy, and could be helpful to Browser
clients in the same way that SWT.getPlatform()
is occasionally useful. Logging an enhancement request for it seems