Re: Best Practices document - not best practices

Thanks Michael, Daniel,

so it sounds like one best practice is to use a separate stylesheet and not put that information in the header. 

I have another question though. 

Is it possible for the server to detect the size of window in use - as opposed to the display capability?

Regards, 

Kevin


-- 
Kevin Holley 
O2 Group Technology
Tel: +44 1473 782214 _ Fax: +44 7711 752031 _ Mobile: +44 7802 220811
IM: kevinaholley (AIM/MSN/Y!/Skype)



-----Original Message-----
From: public-bpwg-request@w3.org <public-bpwg-request@w3.org>
To: public-bpwg@w3.org <public-bpwg@w3.org>
Sent: Wed Jul 27 20:58:04 2005
Subject: Re: Best Practices document - not best practices


Daniel Barclay wrote:

>
> Holley Kevin (Centre) wrote:
>
>> ....  When looking at the WURFL site I
>> note that the real content of the page (not the links or the photos but
>> the meat of the page ... i.e. text about WURFL ...)  ... is towards the
>> bottom of the HTML.  I rather suspect that HTML tools deliberately put
>> "meat" text at the bottom of the HTML.  Why is this?  
>
>
> If you're talking about CSS style information that is embedded in an HTML
> document, it's at the top of the document because of HTML format:  The
> STYLE element has to be within the HEAD element, which is comes before
> the
> BODY element.

Also, if you don't have your rendering metadata before you start
receiving your data, then you really have to wait until the end of the
document to render anything. This leads to bad error handling (you can't
display a partial document) and slow page load times (you cannot begin
to render until the last byte has arrived).

Keeping the styling information at the top, or somehow first to the
rendering engine means that you can display content as soon as you get
it. Whether this is by putting it inline (like the wurfl site does) or
external to the page (like an xsl stylesheet, or a css link), it has to
be better.

Michael




=====================================================
This electronic message contains information from O2 which may be privileged or confidential. The information is intended to be for the use of the individual(s) or entity named above. If you are not the intended recipient be aware that any disclosure, copying distribution or use of the contents of this information is prohibited. If you have received this electronic message in error, please notify us by telephone or email (to the numbers or address above) immediately.
=====================================================

Received on Saturday, 30 July 2005 09:06:52 UTC