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: Thu, 07 Apr 2011 07:57:35 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Q7k5v-0000C1-U0@jessica.w3.org>

--- Comment #13 from Philip Jägenstedt <philipj@opera.com> 2011-04-07 07:57:31 UTC ---
My concern with supporting #xywh for still images is that it would require
rewriting code all over the place (<img>, CSS backgrounds/borders) that
previously used the physical size of the image to also consider the fragment
size. This is of course possible, but it's really a question if it's worth the
implementation cost (and future bugs) to support these use cases, which IMO are
rather marginal.

If HTTP pipelining were completely inadequate, I'd have expected to see
JavaScript libraries to work around this using CSS or canvas in common use.

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 Thursday, 7 April 2011 07:57:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:46 UTC