'Bug#35069: CSS-Problem'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    Bug#35069: CSS-Problem
From:       Vadim Plessky <lucy-ples () mtu-net ! ru>
Date:       2001-11-21 12:33:33
[Download RAW message or body]

On Wednesday 21 November 2001 10:17, joerg.hau@dplanet.ch wrote:
|   Hi All,
|
|   > 1) 'name' attribute is depreciated, you should not use it in HTML
|   > - use 'id' instead
|
|   It may be depreciated, but nevertheless it remains *valid HTML*.
|   Plus, it is still widely used! If Konqueror can not display
|   "old but still legal" tags, it is clearly Konqueror that has a
|   problem.

*depreciated* meand that *it can be omitted from feature versions*.
Try 
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
            "http://www.w3.org/TR/html4/strict.dtd">
as Doctype for typical HTMl document, you will get a lot of errors even if it 
was validating ok as HTML4 Transitional.
So far, I don't see any rendering problem with *my* testcase (which I sent to 
you), besides I can tell to you that MS IE6/Windows also displays Red letters 
on Black background (while Mozilla and Opera5 - Blue letters on White 
background) - for the last 2 links.
So, do you think that Konqueror should be *broken* for that testcase to be 
compatible with Mozilla (and to become not compatible with MS IE?)
I doubt so.

BTW: if you don't like hover's over anchors, do not use them!
AFAIK only few browsers on a planet can support hover CSS effects (try to add 
border and margin/padding to hover's CSS, you will understand what I mean) 

besides, if you have 
P { color: black; background-color: white }
define class 'nohov' as
 .nohov  {  color: black; background-color: white }
 .nohov:hover {  color: black; background-color: white }

and use it for all anchors without HREF:
<a class="nohov">This text is d... </a>
so, hover will give you the same background and color for those A tags, and 
it will not disturb you :-)

|
|   IMHO there's no sense in being compatible with the very latest HTML
|   standard if you are not backward compatible.

well, it's wery well known that HTML4 (as a language for formatting 
/rendering web pages) is *broken* and *misleading*.
XHTML 1.0 is *better*, but IMHO it's only *half* of solution for 
Standards-Based web, or even less than 50%.

If you make your page in XML, and apply CSS on it - I doubt you will see any 
difference between Konqueror and Mozilla (and/or Opera), at least in cases 
where all browser support same CSS properties.

So, it makes a lot of sence to skip support (*in web development*) for old 
browsers (like NN 4.7, IE 4.0) and move forward to XML+CSS, or at least to 
XHTML+CSS.
Keeping compatibility with old, broken browsers makes no sense, IMO.
(unless you have a company which pays *double the price* of typical web 
project for supporting "Netscape 4.7")

|
|   Greetings from Lausanne,
|
|   - Joerg

Greetings from Moscow,

-- 

Vadim Plessky
http://kde2.newmail.ru  (English)
33 Window Decorations and 6 Widget Styles for KDE
http://kde2.newmail.ru/kde_themes.html
KDE mini-Themes
http://kde2.newmail.ru/themes/

[prev in list] [next in list] [prev in thread] [next in thread]
Configure | About | News | Add a list | Sponsored by KoreLogic