Re: Ideas for MWABP? Slides from Peter-Paul Koch on the use of Javascript in Web pages

Thanks Francois... The recommendations you give here definitely tally
similar we've seen elsewhere and that are already in the doc. I'll make sure
I fold all these into the latency section (name tbd) in the next revision
and will take a look at the others to see if there is anything suitable
there.

On Wed, Oct 29, 2008 at 1:50 PM, Francois Daoust <fd@w3.org> wrote:

>
> Hi,
>
> I stumbled upon the following blog post today:
>
>  http://www.quirksmode.org/blog/archives/2008/10/slides_from_ace.html
>
> ... and found that some of the slides match our discussions on Mobile Web
> Application Best Practices, so I thought I would just share it:
>
> http://www.quirksmode.org/presentations/fundamentosweb08/fundamentosweb.pdf
>
>
> In particular:
>
> - how to use onfocus and onblur events to replace onmouseover and
> onmouseout (slides 88-110).
>  That's probably too technical for MWABP. But then we already have fairly
> detailed parts.
>
> - how to do drag-and-drop using the keyboard (slides 135-148).
>  Same thing, probably too detailed for MWABP.
>
> - rules to improve performance (slides 154-193).
>  That's the part that best matches what we have in the spec.
>  The list is extracted from a book by Steve Souders entitled "High
> performance Web Sites" (this explains the apparently irrationale numbering
> below):
>
>  1) Make fewer HTTP requests
>  In MWABP, matches "Minimize External Resources"
>
>  4) Gzip components (slide 158):
>  I don't think he had the mobile context in mind here when he recommands to
> compress everything
>  In MWABP, matches "Use Transfer Compression for Content"
>
>  5) Put stylesheets at the top [and use <link> tags instead of @import]
> (slide 159-160)
>  The browser needs all the style sheets before it can start rendering the
> page.
>
>  6) Put scripts at the bottom
>  It seems that, when scripts are loaded, all the other downloads are
> blocked because the script might contain a document.write() directive. I am
> not sure what "blocked" really means.
>
>  8) Make JavaScript and CSS external
>  For caching purposes.
>  In MWABP, matches the CACHING best practice in the Mobile Web Best
> Practices 1.0 Recommendation
>
> He also mentions the idea to combine different icons into one image and use
> CSS Sprites (slides 170-178)
> In MWABP, matches "Sprite Static Images Into a Single Request"
>
> Francois.
>
>