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

http://www.w3.org/Bugs/Public/show_bug.cgi?id=12427

           Summary: User interface of spatial media fragment URI in <img>
                    or <video> resource, or in browser navigation
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: silviapfeiffer1@gmail.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


Problem: what is a browser to display when the browser navigates to a image or
video resource with a spatial media fragment URI, or when the @src attribute of
a <img> or <video> element contains a spatial media fragment URI

Proposal: a cropped (spliced) image or video is displayed to the user by hiding
the other pixels from the user.

Section affected for image:
http://www.whatwg.org/specs/web-apps/current-work/#update-the-image-data

In particular, this section explains what the image element's image data is:
"The resouce obtained in this fashion is the img element's image data." This
should state that when the resource is obtained with a spatial media fragment,
the img element's image data is restricted to the rectangular region defined by
the spatial media fragment.

Section affected for video:
http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#concept-video-intrinsic-width

The intrinsic width and height of a video element are influenced by provision
of a spatial media fragment URI. The width and height are restricted to the
width and height of the rectangle provided in the spatial media fragment URI.
The browser further needs to remember the x and y offset from which that region
is extracted.

Further, for video, a definition of the video's image data is required similar
to how there is a definition of the img element's image data. This is
particularly important, since video data can be imported into canvas elements
through the drawImage function, so it needs to be clear what the image data is.
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html#dom-context-2d-drawimage

-- 
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 Tuesday, 5 April 2011 22:17:35 UTC