W3C home > Mailing lists > Public > public-bpwg@w3.org > July 2005

RE: Best Practices document - not best practices

From: Holley Kevin \(Centre\) <Kevin.Holley@O2.com>
Date: Wed, 27 Jul 2005 12:41:27 +0100
Message-ID: <729015D2FB03A041A00327DCD0836983FB87@Uksthmsx014>
To: "Daniel Barclay" <daniel@fgm.com>, <public-bpwg@w3.org>, "Luca Passani" <luca.passani@openwave.com>

Dear All,

Further to the message below I was having a discussion offline with Luca
regarding the capabilities of HTML.  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?  Wouldn't it make
more sense to have the tool put the "meat" at the top and then put the
descriptive stuff (stylesheet info) towards the bottom?  Or even allow
browsers to load ONLY the text in case they are not capable or bandwidth
constrained for receiving rich content descriptions?  Are the tools we
have as flexible as HTML in the first place or does the fault lie in
HTML?  Or is it to do with the way we have crafted stylesheets onto
HTML?

I also note that more and more websites are hard to view in smaller
windows as Daniel points out.  One of the points of a Windows-based
system is that you can view several things at the same time!  Scrolling
left and right in this situation is horrible!

Regards,

Kevin

 

-----Original Message-----

=====================================================
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.
=====================================================

From: Daniel Barclay [mailto:daniel@fgm.com] 
Sent: 22 July 2005 15:43
To: public-bpwg@w3.org
Cc: Holley Kevin (Centre)
Subject: Re: Best Practices document - not best practices


Holley Kevin (Centre) wrote:

> Could I ask how we tell the difference between "mobile web" and 
> "regular web" ?

If you ask Barbara.  :-)

(I wasn't advocating such a distinction, just countering her argument in
terms of her own distinctions.)

> Personally I use a mobile device to view "web" pages.  In many cases I

> can read what is there irrespective of whether the target is 
> "mainstream web" or "mobile web".

I wish I had such good luck reading pages even on a regular computer and
screen.  Apparently, most page designers can't understand the concept of
using a large screen to have multiple, smaller windows and assume
everyone's using one full-screen browser window.

If designers were more aware of mobile device limititations (e.g.,
browser display width), maybe they'd use more-flexible page layouts,
which would also help pages display better in non-full-screen browsers
on non-mobile computers.



Daniel
Received on Wednesday, 27 July 2005 11:41:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:09:49 UTC