A never ending story.

[Dirk Mueller]

On Mon, 30 Sep 2002, Michael Reiher wrote:

> thus "wrong". I guess the possible problem is that a certain widget class might
> not want to follow the common colors(allthough, I can't imagine such a case).
> So the only way would be to recalculate the widget class defaults to follow the
> "right" palette. But no clue how.

Yeah, me neither. 

kapp->palette() returns the default palette, i.e. not the one that is 
inverted ? Otherwise I don't see how your patch would make a difference.

BTW, why did you change the loading of the color definitions for window 
decoration colors etc ? I don't think there was any page depending on 
"wrong" colors in this case, were they ?

BTW, do you have a default color palette that matches all requirements for 
webpages ?


> The only _real_solution_  I see is to let khtml run in an own color environment
> where all colors(text, background, widgets, links) match. And the IMHO easiest
> and most flexible way, from the users POV, is to use existing colorschemes. 

The funny part is that we behave just like IE when it comes to color 
defaults, so apparently nobody is disturbed that IE is broken with inverted 
color shemes. Or do they still do something different from us ?

I actually very much like the idea that khtml reacts to user color styles 
automatically :/

> No idea:) What did I break regarding CSS requirements?

the changing of the color definitions in misc/helper.cpp


-- 
Dirk (received 97 mails today)