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

Re: [ResourcePriorities] Implement instead of adding properties to each element

From: Satoru Takagi <sa-takagi@kddi.com>
Date: Thu, 7 Nov 2013 10:23:51 +0900
To: jmann@microsoft.com, public-web-perf@w3.org
Cc: dschulze@adobe.com
Message-Id: <201311071023.BFC12538.JBLBtUTHB@kddi.com>
Hi,

What kind of methods do you think when we want to introduce resource priorities in a different 
element?

'video', 'audio' and 'iframe' are going to be introduced into SVG2.0.[1],[2]
 Naturally resource priorities will be useful in these elements.[3]

[1] http://www.w3.org/Graphics/SVG/WG/wiki/SVG2_Requirements_Commitments
[2] http://www.w3.org/Graphics/SVG/WG/track/actions/3369

[3] http://www.w3.org/Graphics/SVG/WG/wiki/Proposals/ResourcePriorities_for_SVG

Regards,

Satoru Takagi

> Wouldn't having the HTML element interfaces implement the new NoInterfaceObject be 
functionally the same as a partial interface? I'm not sure I understand the benefit of the 
change. We would still need a separate section on each of the elements, as we would need to 
define the content attributes and specific differences between the elements (e.g., script 
behavior is different from img).
> 
> Thanks,
> Jatinder
> 
> -----Original Message-----
> From: Dirk Schulze [mailto:dschulze@adobe.com] 
> Sent: Wednesday, October 30, 2013 12:53 PM
> To: public-web-perf@w3.org
> Subject: [ResourcePriorities] Implement instead of adding properties to each element
> 
> Hi,
> 
> Wouldn't it be easier to define a NoInterfaceObject for the attributes 'lazyload' and '
postpone' from the spec point of view and even more for the implementation point of view?
> 
> Greetings,
> Dirk
> 
Received on Thursday, 7 November 2013 01:24:57 UTC

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