W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2002

Re: more CSS and tables

From: Vadim Plessky <lucy-ples@mtu-net.ru>
Date: Tue, 8 Jan 2002 22:26:03 +0000
Message-Id: <200201081923.g08JNsH07028@post.cnt.ru>
To: w3c-wai-ig@w3.org
On Tuesday 08 January 2002 06:47, David Woolley wrote:
|   Vadim Plessky wrote:
|     > ok, do you have better replacement for the FONT tag?
|
|   It depends on the context.

please provide content when FO)NT can't be replaced with SPAN or DIV

|
|     > Yes, you can replace <FONT></FONT> even with
|
|   <TABLE><TR><TD></TD></TR></TABLE>
|
|     > but *why* you may want to do this?.
|
|   NO! I can see no reason why you might even think that I thought
|   this.

ok, ok :-)
|
|     > so, how you suppose to change color inline? (word "suppose" in this
|   sentence?)
|
|
|   Using inline styles, although, a possibly classed, stylesheet would be
|   better.  Also assuming that the background colour is well defined.
|
|   so, how you <em style="font-weight: inherit; font-style: inherit; color:
|   green">suppose</em> to change color inline? (word "suppose" in this
|   sentence?)

what's wrong with:

 so, how you <span style="color: green">suppose</span> to change color inline?

I mean, why do you prefer <em> to <span>?

|
|   As part of a page where you generally didn't want font changes, you
|   would certainly override them in the style sheet, not inline.  For a
|   consistent house style, this would probably reduce to:
|
|   so, how you <em>suppose</em> to change color inline? (word "suppose" in
|   this sentence?)

Hmm... Are you sure that all browsers (or all future versions of browsers) 
will support <em>?
I think more and more that we need One More Browser - which will have very 
light memory footprint (say, <1MB) and will run on a variety of platforms, in 
particular, on embedded devices.
I can tell you more: may be, I will even go for developing such browser!.  :-)
But I need really cool platform to emerge as a motivation factor.
I am somewhat tired of so-called "new models" of mobile phones.
They add useless functions to it and even can't built it RJ-45 jack - so I 
even can't plug my mobile into Ethernet network, and forced to do 
"syncronization" via some obsolete technologies like infrared or outdated 
serial cable, etc.
Do not want Ethernet jack? Add Radio Ethernet - it's much more col 
technology. Anyone?...

I have heard that Samsung has mobile phone in development based on Linux.
Plus, IBM joined efforts with Casio (? nort sure here) to produce commercial 
version of their "Linux watch".
So, I guess one of those platforms will give me enough motivation.
(and YES, I do not want to support TABLE tags in browser built-in into my 
Linux Watch!)
    
|
|     > I would prefer to use DIV instead of H2, as different browsers have
|   different
|     > opinion what H2 tag is :-(
|
|   H2 tags start H2 elements; all browsers should agree on that.  If you
|   have problems with proper structural markup, it probably means that
|   you want pixel perfect control but are not willing to fully specify
|   the style sheet; fully specify it if you don't like the browser's
|   default.  However the HTML philosophy is that the user controls the
|   detailed appearance and the author provides them with the information
|   about the document structure to allow them to do that - this results
|   in a consistent presentation that makes it easier for the user to
|   find things.

from html4.css (coming with Konqueror 2.2.2):

H2 {
	display: block;
	font-size: 1.4em;
	margin: .83em auto;
	font-weight: bolder;
}

do you see any difference with:

aa {
	display: block;
	font-size: 1.4em;
	margin: .83em auto;
	font-weight: bolder;
}

and using
<aa>Hello, World!</aa>
instead of
<H2>Hello, World!</H2>

assuming that it's XML document?
-- 

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/
Received on Tuesday, 8 January 2002 14:24:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:00 GMT