W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > November 2011

[Bug 12715] When used to include data blocks (as opposed to scripts), the data must be embedded inline

From: <bugzilla@jessica.w3.org>
Date: Sat, 05 Nov 2011 23:07:30 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1RMpKk-00063l-Hc@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12715

Simon Pieters <simonp@opera.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|NEEDSINFO                   |

--- Comment #7 from Simon Pieters <simonp@opera.com> 2011-11-05 23:07:28 UTC ---
Reopening to let the editor consider the request.

(In reply to comment #6)
> Doesn't the 'defer' attribute, and 'onload' events cover this? besides, for
> synchronous cases, separating fetch from parse solves most of the perceived
> performance issues.

The problem is that browsers don't want to download a script that won't be run.
(Some pages use bogus type="" and don't use it as a "data block", and there
it's just wasted bandwidth and time.)

> Imagine if the same restriction applied to <img>.

<img> can't be used for data blocks, so I don't follow.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Saturday, 5 November 2011 23:09:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 5 November 2011 23:09:36 GMT