monodoc-browser: Only GtkHtml renderer included; unusable on dark GTK+ themes

[Jo Shields]

Bug #262719 was written to allow webkit-sharp to enter main, specifically so mono-tools could make use of it. Whilst the build dependencies for mono-tools were altered to take advantage, an oversight in packaging means that only the old GtkHtml renderer is currently included in the monodoc-browser package. The problem with GtkHtml is it does not support CSS at all, and ends up looking unusable with dark GTK+ themes. Attached is a screenshot using "High Contrast Inverse", though the effect is equally visible with themes like DarkLooks.

A 1-line change to debian/monodoc-browser.install is sufficient to use the nicer WebKit renderer only.

[Jo Shields (directhex)]

This bug may well not meet SRU criteria, but it's worth a shot, given monodoc-browser is unusable for people with dark themes right now

[Jo Shields (directhex)]

TEST CASE: Switch to the HighContrast-Inverse theme. Run "monodoc", from the "monodoc-browser" package. mono-tools_2.0-0ubuntu2 produces results like those on the left in the above screenshot (i.e. unusable), post-patch mono-tools_2.0-0ubuntu2.1 produces results like those on the right.

[Martin Pitt (pitti)]

This is a very borderline SRU. How much testing did the webkit backend get? It might break other documentation pages easily. Exchanging the entire rendering backend in an SRU doesn't seem like a wise idea to me, at least it should get some further testing in karmic first.

Also, we don't configure a dark theme by default, so it doesn't even affect the default installation (just people who don't particularly care about ergonomic colors in the first place :-P, SCNR).

[Jo Shields (directhex)]

Fixed in Karmic