LC Comment: Spatial fragment behavior

2010/11/24 Raphaël Troncy <raphael.troncy@eurecom.fr>:
> Furthermore, following the coffee discussion Mike and I had 2 weeks ago at
> TPAC, I point you to this bug entered in the HTML5 bug tracker:
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=10723 "support for media
> fragment URIs in relevant HTML5 elements".
>
> This bug describes the particular problem of rendering spatial media
> fragment in a HTML browser. The Media Fragments WG has written this non
> normative paragraph [1]:
>
> "For a spatial URI fragment, we foresee two distinct use cases: highlighting
> the spatial region in-context and cropping to the region. In the first case,
> the spatial region could be indicated by means of a bounding box or the
> background (i.e., all the pixels that are not contained within the region)
> could be blurred or darkened. In the second case, the region alone would be
> presented as a cropped area. How a document author specifies which use case
> is intended is outside the scope of this specification, we suggest
> implementors of the specification provide a means for this, for example
> through attributes or stylesheet elements."
>
> We will start discussing with the CSS WG how this styling could be done but
> the Media Fragments WG also thinks that if a default behavior must be
> specified, it should happen in the HTML5 specification.

A default behavior definitely needs to be specified, and it should
definitely be the "cropping" behavior.  The CSSWG has assumed that
this would be the effect of a spatial fragment for some time in our
advice regarding spriting.

I don't think the lightboxing behavior should happen in the Media
Fragments level at all.  That's an additional visual effect that can
be achieved manually by the author through a little bit of CSS or JS
(either one can work, depending on what the author prefers).  It's
also not a "fragment" of a resource - it's a full resource, altered
slightly.

~TJ

Received on Wednesday, 24 November 2010 16:43:56 UTC