After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 78418 - Could process default CSS info from GTK+ text widget settings
Could process default CSS info from GTK+ text widget settings
Status: RESOLVED DUPLICATE of bug 79050
Product: gtkhtml2
Classification: Deprecated
Component: General
unspecified
Other other
: Normal normal
: ---
Assigned To: Anders Carlsson
Anders Carlsson
Depends on:
Blocks:
 
 
Reported: 2002-04-11 18:05 UTC by Jeff Waugh
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jeff Waugh 2002-04-11 18:05:14 UTC
Discussing docs accessibility issues with Bill Haneman, and we came up with
a suggestion for gtkhtml2. Not sure if this is already working or not, but
it's an elegant solution to accessibility issues with HTML rendering
throughout GNOME. Slightly edited, pasted with Bill's permission:

<jdub> (docs would probably do well with the same colours as the textentry
areas?)
<billh> yeah
<jdub> and the new text widget has link colours too
<billh> of course if we shipped with a few "standard" rc themes then if we
somehow correlated them (by name, or something) then that would probably be
good enough
<billh> just less flexible and nice, etc.
<billh> it would be nice if the html link color matched the gtk+ link
color, wouldn't it?
<billh> etc.
<jdub> sounds like if the text widgets settings were correct, we could pull
most of them
<billh> correct?
* billh  scratches his head
<jdub> well, appropriate for the user in question
<billh> right
<billh> that one is not our problem ;-)
<billh> I mean, the default settings should be reasonable
<billh> and the user's startup setting should be configurable by the installer
<billh> (if not the same person as the user)
<billh> but OK,
<billh> if we have a useful theme then we should be OK if we scavenge for
things like font and colors
<jdub> but it's close enough to a 1:1 mapping between the text editor and
the doc view - we'd need to pull those out and generate the appropriate css
fragment
<billh> at the moment there is only one "font" and "size", so from there we
just use relative styling
<billh> that would be the ideal and elegant solution.
<billh> a fallback would be to have a CSS sheet corresponding to each
standard gtkrc file
<jdub> that said, why wouldn't gtkhtml2 be doing that *all* the time?
<billh> and a capplet linking them together.
<billh> jdub: hmm, well, gtkhtml2 probably has a "standard" style sheet it
uses.
<billh> jdub: which maybe a mistake, probably better if it used gtk+ styles for
<jdub> yeah
<jdub> 'cos it's a gtk+ widget
<billh> jdub: "default" values in the absence of a style sheet
<jdub> and even if you had odd themes, it would still look like arse
<jdub> (like black and green themes that people seem to like)
<billh> jdub: yeah, but it's very CSS-oriented, so people don't usually
think to themselves "what if there is no stylesheet" if their whole world
revolves around stylesheets ;-)
<jdub> heh
<jdub> it's a pity we don't have a gtkhtml2 maintainer to suggest this to :)
<billh> I think that if you like a fugly broken theme, might as well have
fugly broken web pages too
<billh> heh
* jdub  lodges a bug
<billh> jdub: it may be that the right solution is to make gtkhtml2
<billh> jdub: do the "right" thing if there is no stylesheet applied
<billh> jdub: but without diving into the code I don't know if this would
be easy, hard, or maybe already there waiting to be uncovered
Comment 1 Mikael Hallendal 2002-06-01 14:12:53 UTC
resolving this as a duplicate of #79050, please reopen if that was
incorrect.

*** This bug has been marked as a duplicate of 79050 ***