Re: [ResourcePriorities] svg feimage comments

On Thursday, September 12, 2013 at 9:19 AM, Ivan Kotenkov wrote:

> Hello!
> 
> Does appending "lazyload" and "postpone" attributes to svg feImage node affect SVG 1.1 specification? If so, was this discussed with SVG group? If the above mentioned attributes are not added to the SVG spec, for the purpose of compatibility with the SVG spec, using a separate xmlns may be useful, e.g. perf:lazyload
I think we should leave that up to the SVG WG. As I argued in another email: each group should be left to adopt this stuff as they need to, but this group risks missing important stuff by attempting to add this all over the platform.  
> On the lower level, I think another clarification is needed. SVG 1.1 specification contains SVGLoad event:
> "The event is triggered at the point at which the user agent has fully parsed the element and its descendants and is ready to act appropriately upon that element, such as being ready to render the element to the target device. Referenced external resources that are required (http://www.w3.org/TR/SVG/single-page.html#struct-ExternalResourcesRequired) must be loaded, parsed and ready to render before the event is triggered. Optional external resources are not required to be ready for the event to be triggered."
> The draft should explicitly state what should be done when feimage has externalResourcesRequired="true" and a lazyload attribute (it seems to me that these attribute conflict and lazyload should have no effect in this situation).
> 
> Also, I think SVG 1.1 specification should be added to the reference list.

I don't agree that the spec should mention anything about SVG at all.

Received on Thursday, 12 September 2013 11:00:45 UTC