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

[Bug 12427] User interface of spatial media fragment URI in <img> or <video> resource, or in browser navigation

From: <bugzilla@jessica.w3.org>
Date: Wed, 06 Apr 2011 17:43:39 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Q7WlX-00036l-6V@jessica.w3.org>

--- Comment #11 from Philip Jägenstedt <philipj@opera.com> 2011-04-06 17:43:38 UTC ---
(In reply to comment #10)
> (In reply to comment #9)
> > > http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-August/027581.html
> > 
> > I'm not sure I understand this. What is "image sprite support" and why is
> > cutting an image using the canvas 2d api not good enough?
> Consider the general case of CSS spriting, which is currently done in a hacky
> way with background-position.  Spriting into an <img> is just one instance of
> this type of spriting that can't be done even hackily at present (without doing
> something like running script to use <canvas>).

Is the goal of this to save bandwidth by putting several images into a single
physical image?

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 Wednesday, 6 April 2011 17:43:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 6 April 2011 17:43:41 GMT