- From: Raphaël Troncy <raphael.troncy@eurecom.fr>
- Date: Wed, 17 Nov 2010 10:13:50 +0100
- To: Philip Jägenstedt <philipj@opera.com>
- CC: public-media-fragment@w3.org
Hi Philip, > While this would be very useful, it's not something that can be > standardized in browsers. The URL page.html#t=1 already causes browsers > to scroll to the element with id="t=1". When the browser issues a GET request on page.html, the browser does not know which representation of this resource it will receive, and therefore cannot be prepared to "scroll". If the representation received is of html nature, then yes, it should scroll. If page.html is a video, you could imagine that the browser starts playing from the t=... > Overloading this behavior would > most likely break some pages. See > <http://www.whatwg.org/specs/web-apps/current-work/multipage/history.html#scroll-to-fragid> I really don't see what will be broken. Raphaël -- Raphaël Troncy EURECOM, Multimedia Communications Department 2229, route des Crêtes, 06560 Sophia Antipolis, France. e-mail: raphael.troncy@eurecom.fr & raphael.troncy@gmail.com Tel: +33 (0)4 - 9300 8242 Fax: +33 (0)4 - 9000 8200 Web: http://www.eurecom.fr/~troncy/
Received on Wednesday, 17 November 2010 09:16:58 UTC