2009/11/17 Arne Babenhauserheide <arne_...@web.de>: > Am Dienstag, 17. November 2009 14:32:29 schrieb Michal Suchanek: >> Similarly, if you want to put a single warning sign somewhere in >> yellow on red then you just add it. If you want your site to have some >> particular text color you better ensure that you define a background >> on which the text is visible. > > But with warnings the same happens as with the text: They are invisble on some > backgrounds.
They aren't because the warning has both background and text color set but they may not be as distinguished on some backgrounds. > > I agree though, that the effect with the main content is stronger :) > >> Yes, if you want to write a theme you usually start by coping a >> working theme and only change the things you want to change. > > I don't - I learned HTML and CSS from the ground up - working directly with > pencil and paper for the draft and then coding it by hand. Yes, with HTML you typically don't have a working site to start from, unlike KDE theme authors you have to start from scratch. That's probably why many people are surprised that a site that works for them breaks in another browser. >> > "Disharmonizes" defined by "is in the table as really not working >> > together with the background". >> >> Even detecting the situation when an element has colors which >> originate from different styles would probably need non-trivial >> support in the HTML rendering engine. > > When I think about how hard it is for the Firefox people to fix the "I can > read > your browser history with a simple css trick" bug (because they do some really > complex stuff internally), I don't think the complexity of that would be high > compared with what they already do. You are wrong on this one. Exactly because the current rendering engine is complex making even simple changes to it has unpredictable results. That's why fixing anything on it takes ages. Thanks Michal
