Re: [ResourcePriorities] Blocking content resources on CSS properties

Similarly to problems raised in previous thread ([ResourcePriorities] Blocking content resources on CSS properties), there is another concern: the lazyload and postpone attributes may be changed via scripts.

In current version of the spec ('postpone' is a MUST and nothing is said about 'initial load' mentioned in the thread) almost no element which supports 'postpone' attribute should be downloaded before all the scripts on the page are executed, which sounds pretty ridiculous.

I suggest that the spec should state that changing the attribute should have no effect if the resource is already being downloaded.

Ivan Kotenkov

Received on Wednesday, 6 November 2013 12:57:12 UTC