In your screen stylesheet you should have:
display: block;
font-weight: bold;
font-size: 150%;
bottom: 45px;
position: absolute;
This will align the div to the bottom of the screen (what you originally
had) when viewed on a screen.
In your print
I seem to be having an alignment issue that only appears in IE6 on XP. It is fine in all other browsers tested including IE6 on W2k, both Win + Mac FF, Safari Opera.The alignment issues are seen on the vertical lines running at the edges and in the left blue column.
An example page can be viewed
Patrick H. Lauke wrote:
Thierry Koblentz wrote:
The issue is not about the attributes but their value; and in the example I
wrote, the validator would choke on the ID's *value*. Because 1st_Section
is a valid value for the name attribute but it is *not* for the id
attribute.
To expand:
[EMAIL PROTECTED]
Surely any conforming user agent should ignore any markup that it does
not understand, so is there really any need to stop using
name, where it
is being used for 'belt and braces' compatibility?
For XHTML 1.0 (even strict), using name is still fine. Deprecated, yes, but
Hi folks
I was wondering if anyone can help me.
I am using the Dave Shea enhancement to allow for valid H2 text to be visible
to the screenreader whilst maintaining the graphic for the client.
One of the things the client wants now is the heading to be a link.
I have styled this and all
On Wed, 7 Jun 2006 06:48 pm, [EMAIL PROTECTED] wrote:
Surely any conforming user agent should ignore any markup that it does
No, user agents don't ignore markup that is not specified in the DOCTYPE. It
generates (or should) a parse error. Most web sites don't serve XHTML
correctly as
Dear listers,
Is there anyone out there with experience of avoiding page breaks in
daft places? I have a site with the potential to print out some thirty
different pages, with each printout length between 1 page and 4. Each
page has small illustrations scattered unevenly amongst the text,
It might be better to hide the crippled handheld css file from this browserI believe Opera ignores the handheld stylesheet anyway.I devides a neat technique for detecting a small screen device if anyone's interested. Here's the article:
UNSUBSCRIBE THE LIST DISCUSSION
_
Un amor, una aventura, compañía para un viaje. Regístrate gratis en MSN Amor
Amistad. http://match.msn.es/match/mt.cfm?pg=channeltcid=162349
I believe Opera ignores the handheld stylesheet anyway.
Nope. Opera, NetFront and S60Browser are almost the only ones treating
screen/handheld stylesheets right.
--
Jan Brasna :: www.alphanumeric.cz | www.janbrasna.com | www.wdnews.net
**
UNSUBSCRIBE DISCUSSION LIST
_
Descarga gratis la Barra de Herramientas de MSN
http://www.msn.es/usuario/busqueda/barra?XAPID=2031DI=1055SU=http%3A//www.hotmail.comHL=LINKTAG1OPENINGTEXT_MSNBH
I think that the simple way to make nice PDA-site -- make the separate
version for PDA, because for PDA the superfluous information is not
necessary so much then for PC
Design in simplicity ;)
**
The discussion list for
So I've been looking into this whole microformats thing. I'm excited
(to say the very least!)
I've looked over the hCard, hCalendar and xfn overviews. They're
relatively straightforward...but then I looked at the XOXO spec and
was completely snowed...
Can anyone help explain in relatively
On Wed, 07 Jun 2006 13:05:35 +0100, Designer wrote:
[...] I have a site with the potential to print out some thirty
different pages, with each printout length between 1 page and 4. Each
page has small illustrations scattered unevenly amongst the text, and
I'm finding that some pages attempt
14 matches
Mail list logo