W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > September 2010

[Bug 10723] support for media fragment URIs in relevant HTML5 elements

From: <bugzilla@jessica.w3.org>
Date: Wed, 29 Sep 2010 13:34:54 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1P0woA-0006pD-LY@jessica.w3.org>

RaphaŽl Troncy <raphael.troncy@eurecom.fr> changed:

           What    |Removed                     |Added
                 CC|                            |raphael.troncy@eurecom.fr

--- Comment #2 from RaphaŽl Troncy <raphael.troncy@eurecom.fr> 2010-09-29 13:34:53 UTC ---

Indeed, the URI RFC states that fragment identifiers are defined on a
per-MIME-type basis.

We have made an analysis to find out if there are any media types registered
with IANA that contain information about how fragment/anchor identifiers are
constructed for use in conjunction with this media type. as defined in RFC4288
(Media Type Specifications and Registration Procedures). As a matter of fact,
almost none of the media type RFC states something about fragments. You can
read about this analysis at

Note that we have also an open issue about this in our tracker:

Having said this, the Media Fragment specification contains currently a note
for implementers, read
that states how a UA (e.g. an HTML5 compliant browser) could render/display a
media fragment. The Working Group is currently discussing whether we should
describe or mandate particular behaviors depending on the UA. Some followers
(of both groups) have expressed strong views on what a browser should do, such
as highlighting or cropping an image in case of a spatial media fragment.
Another possibility is to have a new attribute in the media element that
indicate what a browser should do. This bug has been entered to discuss and
resolve this issue.

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, 29 September 2010 13:34:59 UTC

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