W3C home > Mailing lists > Public > public-web-perf@w3.org > November 2013

Re: [ResourcePriorities] Spec updates

From: Bruno Racineux <bruno@hexanet.net>
Date: Thu, 21 Nov 2013 15:27:19 -0800
To: Marcos Caceres <w3c@marcosc.com>, Jonas Sicking <jonas@sicking.cc>
CC: Jatinder Mann <jmann@microsoft.com>, "public-web-perf@w3.org" <public-web-perf@w3.org>
Message-ID: <CEB3D2AB.7D89B%bruno@hexanet.net>
On 11/21/13 3:00 PM, "Marcos Caceres" <w3c@marcosc.com> wrote:


>On Thursday, 21 November 2013 at 22:50, Jonas Sicking wrote:
>
>> > Reading the Resource Priorities draft they describe lazyload as
>>postponing and vice versa."
>> 
>> Maybe it would help to use clearer names than argue which means what.
>> lowpriority seems clearer than postpone.

lowpriority is skewed because is doesn't carry the 'order of importance'
as much.


>I agree... these names are not very clear. I also tend to get them the
>wrong way around and often find myself having to look them up.

I have suggested 'delay' in the past. Just a shorter synonym to defer.

Though 'postpone' seems proper, as it carries the same semantics as defer,
which provides 'ordered deferred' behavior (IE10+) for scripts.


Free Dictionary definitions being:
postpone [pəʊstˈpəʊn pəˈspəʊn]vb (tr)
1. to put off or delay until a future time
2. to put behind in order of importance; defer
Received on Thursday, 21 November 2013 23:27:48 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:37 UTC