[whatwg] Closing the WHATWG mailing lists

Hi all, This list has not been very active in recent years and maintaining the mailing list setup as our hosting infrastructure change has become a bit of a burden. Because of this, I'm proposing that this and the other (even less active) lists are closed in favor of GitHub issues. If you have

Re: [whatwg] metadata

On Mon, Apr 10, 2017 at 8:38 AM Andy Valencia wrote: > What follows is a first pass at addressing a missing ability > when dealing with Internet streams, usually radio ones. > Comments and suggestions are quite welcome; as my first > attempt--ever--at submitting to

Re: [whatwg] VIDEO and pitchAdjustment

On Wed, Sep 28, 2016 at 5:18 PM, Garrett Smith <dhtmlkitc...@gmail.com> wrote: > On Wed, Mar 2, 2016 at 2:36 AM, Philip Jägenstedt <phil...@opera.com> wrote: >> On Wed, Mar 2, 2016 at 5:08 PM, Paul Adenot <pade...@mozilla.com> wrote: >>> >>> Gecko use

Re: [whatwg] VIDEO and pitchAdjustment

On Wed, Mar 2, 2016 at 5:08 PM, Paul Adenot wrote: > > Gecko uses code that can do arbitrary pitch adjustment, unrelated to > time-stretching (which is speed change with pitch compensation). That's neat. If you're interested in exposing this as an API on HTMLMediaElement,

Re: [whatwg] VIDEO and pitchAdjustment

On Wed, Mar 2, 2016 at 9:19 AM, Garrett Smith <dhtmlkitc...@gmail.com> wrote: > On Thu, Nov 12, 2015 at 11:32 AM, Philip Jägenstedt <phil...@opera.com> wrote: >> On Thu, Nov 12, 2015 at 10:55 AM, Garrett Smith <dhtmlkitc...@gmail.com> >> wrote: >>> On 11/1

Re: [whatwg] Removing mediagroup/MediaController from HTML

On Tue, Nov 3, 2015 at 4:20 PM, David Singer wrote: > >> On Oct 3, 2015, at 13:39 , Silvia Pfeiffer wrote: >> >> On Fri, Oct 2, 2015 at 10:27 AM, Domenic Denicola wrote: >>> From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On

Re: [whatwg] VIDEO and pitchAdjustment

On Thu, Nov 12, 2015 at 9:43 AM, Eric Carlson <eric.carl...@apple.com> wrote: > >> On Nov 12, 2015, at 9:34 AM, Philip Jägenstedt <phil...@opera.com> wrote: >> >> On Thu, Nov 12, 2015 at 9:07 AM, Garrett Smith <dhtmlkitc...@gmail.com >> <mailto:dhtmlk

Re: [whatwg] VIDEO and pitchAdjustment

On Thu, Nov 12, 2015 at 10:55 AM, Garrett Smith <dhtmlkitc...@gmail.com> wrote: > On 11/12/15, Philip Jägenstedt <phil...@opera.com> wrote: >> On Thu, Nov 12, 2015 at 9:07 AM, Garrett Smith <dhtmlkitc...@gmail.com> >> wrote: >>> >>> On 10

Re: [whatwg] VIDEO and pitchAdjustment

On Thu, Nov 12, 2015 at 9:07 AM, Garrett Smith <dhtmlkitc...@gmail.com> wrote: > > On 10/19/15, Philip Jägenstedt <phil...@opera.com> wrote: > > On Tue, Sep 1, 2015 at 11:21 AM, Philip Jägenstedt <phil...@opera.com> > > wrote: > >> On Mon, Aug 31, 2015

Re: [whatwg] VIDEO and pitchAdjustment

On Tue, Sep 1, 2015 at 11:21 AM, Philip Jägenstedt <phil...@opera.com> wrote: > On Mon, Aug 31, 2015 at 9:48 PM, Domenic Denicola <d...@domenic.me> wrote: >> From: Eric Carlson [mailto:eric.carl...@apple.com] >> >>> FWIW, Safari supports negative play

Re: [whatwg] W3C Timed Text Working Group proposal for HTMLCue

Hi Nigel, I'm trying to spend less time on WebVTT and related questions these days, but here's my high-level feedback, inline: On Thu, Sep 10, 2015 at 11:46 PM, Nigel Megitt wrote: > Dear WhatWG, Jer, Eric, Silvia, Philip, > > W3C Timed Text Working Group kindly requests

Re: [whatwg] deprecating

On Wed, Sep 2, 2015 at 1:00 PM, henry.st...@bblfish.net wrote: > >> On 1 Sep 2015, at 19:56, Ian Hickson wrote: >> >> As far as I can tell, therefore, things here are working exactly as one >> should expect. > > Indeed: they seem to be working as one would

Re: [whatwg] VIDEO and pitchAdjustment

On Mon, Aug 31, 2015 at 9:48 PM, Domenic Denicola wrote: > From: Eric Carlson [mailto:eric.carl...@apple.com] > >> FWIW, Safari supports negative playback rates on the desktop and on iOS. >> >> ... >> >> The crash Garrett noted in Safari 8 is a bug that “only" happens with

Re: [whatwg] preload=metadata elements don't necessarily fire canplay

On Thu, Jul 16, 2015 at 4:32 AM, Robert O'Callahan rob...@ocallahan.org wrote: On Thu, Jul 16, 2015 at 1:59 AM, Philip Jägenstedt phil...@opera.com wrote: On Wed, Jul 15, 2015 at 12:43 AM, Robert O'Callahan rob...@ocallahan.org wrote: On Tue, Jul 14, 2015 at 11:24 PM, Philip Jägenstedt phil

Re: [whatwg] Proposal: Allow disabling of default scroll restoration behavior

On Mon, Jul 13, 2015 at 5:56 PM, Majid Valipour maji...@google.com wrote: On Mon, Jul 13, 2015 at 10:55 AM Philip Jägenstedt phil...@opera.com If the StateOptions interface could be implemented with no internal reference back to its owning History object it seems pretty harmless, a mere holder

Re: [whatwg] preload=metadata elements don't necessarily fire canplay

On Wed, Jul 15, 2015 at 12:43 AM, Robert O'Callahan rob...@ocallahan.org wrote: On Tue, Jul 14, 2015 at 11:24 PM, Philip Jägenstedt phil...@opera.com wrote: Basically a I trust the browser to decide and promise not to assume anything state? The auto state is already suitable named

Re: [whatwg] preload=metadata elements don't necessarily fire canplay

On Tue, Jul 7, 2015 at 11:56 AM, Robert O'Callahan rob...@ocallahan.org wrote: On Tue, Jul 7, 2015 at 9:41 PM, Philip Jägenstedt phil...@opera.com wrote: Unsurprisingly, I like this, as it's basically what Presto did. However, I think preload=metadata should reach HAVE_CURRENT_DATA, because

Re: [whatwg] preload=metadata elements don't necessarily fire canplay

On Tue, Jul 14, 2015 at 3:15 AM, Robert O'Callahan rob...@ocallahan.org wrote: Apart from the problems already discussed here, there is currently no specced or interoperably implemented way to set a preload value that guarantees HAVE_CURRENT_DATA, HAVE_FUTURE_DATA or HAVE_ENOUGH_DATA will be

Re: [whatwg] preload=metadata elements don't necessarily fire canplay

On Tue, Jul 14, 2015 at 1:08 PM, Robert O'Callahan rob...@ocallahan.org wrote: On Tue, Jul 14, 2015 at 10:33 PM, Philip Jägenstedt phil...@opera.com wrote: I see, is this a policy that's applied even with a single video in a page, or is it something like a limit on the total number of players

Re: [whatwg] preload=metadata elements don't necessarily fire canplay

On Tue, Jul 14, 2015 at 11:57 AM, Robert O'Callahan rob...@ocallahan.org wrote: On Tue, Jul 14, 2015 at 8:51 PM, Philip Jägenstedt phil...@opera.com wrote: Would it solve the same practical problems if auto were redefined to mean that the goal readyState is HAVE_ENOUGH_DATA? Probably

Re: [whatwg] preload=metadata elements don't necessarily fire canplay

On Tue, Jul 14, 2015 at 1:17 PM, Robert O'Callahan rob...@ocallahan.org wrote: On Tue, Jul 14, 2015 at 11:13 PM, Philip Jägenstedt phil...@opera.com wrote: If the behavior could be made interoperable for when resources are not a problem, that would be a good start at least. The spec can say

Re: [whatwg] Proposal: Allow disabling of default scroll restoration behavior

On Mon, Jul 13, 2015 at 4:26 PM, Anne van Kesteren ann...@annevk.nl wrote: On Mon, Jul 13, 2015 at 3:58 PM, Majid Valipour maji...@chromium.org wrote: It is only used as way to group properties (perhaps similar to ValidityState?) and to keep History interface clean and stack-like. If that is

Re: [whatwg] DOM Events Proposal: EventListenerOptions 'mayCancel' for improved scroll performance

On Thu, Jul 9, 2015 at 3:44 PM, Rick Byers rby...@chromium.org wrote: On Thu, Jul 9, 2015 at 9:39 AM, Rick Byers rby...@chromium.org wrote: On Thu, Jul 9, 2015 at 9:05 AM, James Ross w3c-20040...@james-ross.co.uk wrote: Date: Thu, 9 Jul 2015 14:42:07 +0200 From: phil...@opera.com I

Re: [whatwg] DOM Events Proposal: EventListenerOptions 'mayCancel' for improved scroll performance

On Thu, Jul 9, 2015 at 6:40 PM, Boris Zbarsky bzbar...@mit.edu wrote: On 7/9/15 8:42 AM, Philip Jägenstedt wrote: Would there be any way to feature detect support for EventListenerOptions as the third argument? Yes. You call addEventListener and pass an object that has getters

Re: [whatwg] DOM Events Proposal: EventListenerOptions 'mayCancel' for improved scroll performance

On Thu, Jul 9, 2015 at 5:30 PM, Rick Byers rby...@chromium.org wrote: On Thu, Jul 9, 2015 at 11:22 AM, Anne van Kesteren ann...@annevk.nl wrote: On Thu, Jul 9, 2015 at 5:15 PM, Rick Byers rby...@chromium.org wrote: I think there's a big opportunity to substantially improve scroll

Re: [whatwg] DOM Events Proposal: EventListenerOptions 'mayCancel' for improved scroll performance

On Wed, Jul 8, 2015 at 9:12 PM, Rick Byers rby...@chromium.org wrote: [Cross-posted to www-...@w3.org - please let me know if there's a better way to account for the DOM spec duality] In Chromium we've long worked hard at maximizing scroll performance, with scroll-blocking DOM events (wheel

Re: [whatwg] preload=metadata elements don't necessarily fire canplay

On Tue, Jul 7, 2015 at 4:48 AM, Robert O'Callahan rob...@ocallahan.org wrote: On Tue, Jul 7, 2015 at 1:44 AM, Philip Jägenstedt phil...@opera.com wrote: On Mon, Jul 6, 2015 at 2:19 PM, Robert O'Callahan rob...@ocallahan.org wrote: On Mon, Jul 6, 2015 at 11:17 PM, Philip Jägenstedt phil

Re: [whatwg] preload=metadata elements don't necessarily fire canplay

On Wed, Jun 10, 2015 at 6:53 AM, Robert O'Callahan rob...@ocallahan.org wrote: In Gecko, video preload=metadata doesn't fire canplay. This is allowed (encouraged, even) by the spec, since we can efficiently satisfy preload=metadata by stopping decoding after one frame, and if we only decode

Re: [whatwg] preload=none and HTMLMediaElement.load()

On Wed, Jun 17, 2015 at 2:55 AM, Brian Birtles bbirt...@mozilla.com wrote: The HTMLMediaElement.load()[1] method currently cancels playback of the current resource and runs the resource selection algorithm[2] (and in turn the resource fetch algorithm[3]). When preload=none, however, the

Re: [whatwg] preload=metadata elements don't necessarily fire canplay

On Mon, Jul 6, 2015 at 2:19 PM, Robert O'Callahan rob...@ocallahan.org wrote: On Mon, Jul 6, 2015 at 11:17 PM, Philip Jägenstedt phil...@opera.com wrote: On Wed, Jun 10, 2015 at 6:53 AM, Robert O'Callahan rob...@ocallahan.org wrote: In Gecko, video preload=metadata doesn't fire canplay

[whatwg] Announcing the Media Session Standard

Hi all, https://mediasession.spec.whatwg.org/ has been live since April 30, and we'd like to let everyone know of its existence. I recommend reading the introduction and https://github.com/whatwg/mediasession/blob/master/README.md for an overview of what we're trying to enable. We're doing a

Re: [whatwg] Effect of image-orientation on naturalWidth/Height

For video the rotation is applied to videoWidth and videoHeight, at least in Chromium/Blink. A video with rotation metadata is thus indistinguishable from one where the frame themselves are rotated. If there's any hope that doing the same for img could be Web compatible, and Safari's behavior

Re: [whatwg] How to expose caption tracks without TextTrackCues

On Sun, Oct 26, 2014 at 8:28 AM, Silvia Pfeiffer silviapfeiff...@gmail.com wrote: On Thu, Oct 23, 2014 at 2:01 AM, Philip Jägenstedt phil...@opera.com wrote: On Sun, Oct 12, 2014 at 11:45 AM, Silvia Pfeiffer silviapfeiff...@gmail.com wrote: Hi all, In the Inband Text Tracks Community

Re: [whatwg] How to expose caption tracks without TextTrackCues

On Wed, Oct 22, 2014 at 5:33 PM, Bob Lund b.l...@cablelabs.com wrote: On 10/22/14, 9:01 AM, Philip Jägenstedt phil...@opera.com wrote: On Sun, Oct 12, 2014 at 11:45 AM, Silvia Pfeiffer silviapfeiff...@gmail.com wrote: Hi all, In the Inband Text Tracks Community Group we've recently had

Re: [whatwg] How to expose caption tracks without TextTrackCues

On Sun, Oct 12, 2014 at 11:45 AM, Silvia Pfeiffer silviapfeiff...@gmail.com wrote: Hi all, In the Inband Text Tracks Community Group we've recently had a discussion about a proposal by HbbTV. I'd like to bring it up here to get some opinions on how to resolve the issue. (The discussion

Re: [whatwg] Memory management problem of video elements

On Tue, Aug 19, 2014 at 3:54 PM, duanyao duan...@ustc.edu wrote: 于 2014年08月19日 20:23, Philip Jägenstedt 写道: On Tue, Aug 19, 2014 at 11:56 AM, duanyao duan...@ustc.edu wrote: If the media element object keeps track of its current playing url and current position (this requires little memory

Re: [whatwg] Memory management problem of video elements

On Wed, Aug 20, 2014 at 12:04 PM, duanyao duan...@ustc.edu wrote: 于 2014年08月20日 15:52, Philip Jägenstedt 写道: On Tue, Aug 19, 2014 at 3:54 PM, duanyao duan...@ustc.edu wrote: I'm not familiar with game programing. Are sound effects small audio files that are usually played as a whole

Re: [whatwg] Memory management problem of video elements

On Tue, Aug 19, 2014 at 9:12 AM, duanyao duan...@ustc.edu wrote: Hi, Recently I have investigated memory usage of HTML video element in several desktop browsers (firefox and chrome on windows and linux, and IE 11), and have found some disappointing results: 1. A video element in a playable

Re: [whatwg] Memory management problem of video elements

On Tue, Aug 19, 2014 at 11:56 AM, duanyao duan...@ustc.edu wrote: 于 2014年08月19日 16:00, Philip Jägenstedt 写道: On Tue, Aug 19, 2014 at 9:12 AM, duanyao duan...@ustc.edu wrote: Hi, Recently I have investigated memory usage of HTML video element in several desktop browsers (firefox and chrome

Re: [whatwg] Media sink device selection on audio/video

On Tue, Jan 14, 2014 at 5:51 AM, Ami Fischman fisch...@chromium.org wrote: On Sun, Jan 12, 2014 at 8:47 PM, Philip Jägenstedt phil...@opera.com wrote: [...] Do you mean to make this per-origin as well? (It will require storing that information per-origin forever, or until some invisible

Re: [whatwg] Media sink device selection on audio/video

a conversation for public-media-capture? On Mon, Jan 13, 2014 at 3:30 PM, Philip Jägenstedt phil...@opera.com wrote: On Tue, Jan 14, 2014 at 5:51 AM, Ami Fischman fisch...@chromium.org wrote: On Sun, Jan 12, 2014 at 8:47 PM, Philip Jägenstedt phil...@opera.com wrote: [...] Do you mean

Re: [whatwg] Media sink device selection on audio/video

On Thu, Dec 19, 2013 at 2:45 PM, Ami Fischman fisch...@chromium.org wrote: On Wed, Dec 18, 2013 at 8:38 PM, Ian Hickson i...@hixie.ch wrote: On Tue, 17 Dec 2013, Ami Fischman wrote: Recently https://www.w3.org/Bugs/Public/show_bug.cgi?id=23263 Navigator acquired the ability to enumerate

[whatwg] Specify Location.ancestorOrigins

https://bugs.webkit.org/show_bug.cgi?id=83493 It looks like this fell off the radar, because I can't find it in any spec. The reason I noticed is that it's implemented using DOMStringList in Blink, an interface which I also can't find a spec for... Philip

Re: [whatwg] Specify Location.ancestorOrigins

Thanks Jonas and Ian, I'll follow those two bugs! On Thu, Dec 12, 2013 at 11:50 PM, Ian Hickson i...@hixie.ch wrote: On Thu, 12 Dec 2013, Philip Jägenstedt wrote: https://bugs.webkit.org/show_bug.cgi?id=83493 It looks like this fell off the radar, because I can't find it in any spec

[whatwg] Specify getSVGDocument

http://software.hixie.ch/utilities/js/live-dom-viewer/?saved=2643 In my testing, getSVGDocument is supported on embed, frame, iframe and object in Firefox Nightly, IE11 Preview, Safari 7.0 and Opera 12.16, the only exception being frame.getSVGDocument in Firefox. I don't know if this API is

Re: [whatwg] Specify getSVGDocument

On Mon, Nov 18, 2013 at 8:02 PM, Boris Zbarsky bzbar...@mit.edu wrote: On 11/18/13 1:37 PM, Philip Jägenstedt wrote: http://software.hixie.ch/utilities/js/live-dom-viewer/?saved=2643 In my testing, getSVGDocument is supported on embed, frame, iframe and object in Firefox Nightly, IE11

Re: [whatwg] Should onfoo event handler properties be on Element or HTMLElement?

On Wed, Oct 9, 2013 at 12:02 AM, Ian Hickson i...@hixie.ch wrote: On Tue, 8 Oct 2013, Simon Pieters wrote: I think it would be bad to have an IDL attribute without a working content attribute for a given element. That's just confusing. Yeah, that's the main reason I wouldn't put this on

Re: [whatwg] Should onfoo event handler properties be on Element or HTMLElement?

On Wed, Oct 9, 2013 at 1:29 PM, Erik Dahlstrom e...@opera.com wrote: On Wed, 09 Oct 2013 10:53:29 +0200, Philip Jägenstedt phil...@opera.com wrote: ... OK, I hadn't considered that moving this to Element would imply the content attributes being reflected for all namespaces. Even though

Re: [whatwg] Should onfoo event handler properties be on Element or HTMLElement?

On Tue, Oct 8, 2013 at 5:26 PM, Anne van Kesteren ann...@annevk.nl wrote: On Tue, Oct 8, 2013 at 4:26 PM, Erik Dahlstrom e...@opera.com wrote: On Tue, 08 Oct 2013 15:49:48 +0200, Philip Jägenstedt phil...@opera.com wrote: 1. Do what Gecko does, even though there's no SVG spec requiring it yet

Re: [whatwg] Should onfoo event handler properties be on Element or HTMLElement?

On Tue, Oct 8, 2013 at 8:21 PM, Boris Zbarsky bzbar...@mit.edu wrote: On 10/8/13 9:49 AM, Philip Jägenstedt wrote: Gecko has HTMLElement implements GlobalEventHandlers in its IDL,[1] but somewhat surprisingly also SVGElement implements GlobalEventHandlers.[2] Note that in Gecko SVG

Re: [whatwg] Should video controls generate click events?

On Wed, Sep 11, 2013 at 10:48 AM, Simon Pieters sim...@opera.com wrote: On Wed, 11 Sep 2013 01:35:00 +0200, Ian Hickson i...@hixie.ch wrote: On Wed, 21 Aug 2013, Robert O'Callahan wrote: I think you basically have to assume that if you specify controls then the controls may accept clicks

Re: [whatwg] Should video controls generate click events?

On Wed, Sep 11, 2013 at 11:18 AM, Simon Pieters sim...@opera.com wrote: On Wed, 11 Sep 2013 10:51:44 +0200, Philip Jägenstedt phil...@opera.com wrote: That might be good so that the behavior is consistent between browsers. However, I think it should be conditional on whether the controls

Re: [whatwg] Should video controls generate click events?

On Wed, Aug 21, 2013 at 12:57 AM, Bob Lund b.l...@cablelabs.com wrote: What about a Web page that uses JS to control pause/play/etc based on external messages, say from a WebSocket? The sender in this case acts as a remote control. That would involve neither video controls nor click/touch

Re: [whatwg] Should video controls generate click events?

On Wed, Aug 21, 2013 at 3:11 AM, Peter Occil pocci...@gmail.com wrote: On Tue, Aug 20, 2013 at 3:28 PM, Silvia Pfeiffer silviapfeiff...@gmail.com wrote: IMHO, the example that Philip provided in http://people.opera.com/~** philipj/click.html http://people.opera.com/~philipj/click.html is not

Re: [whatwg] Should video controls generate click events?

On Tue, Aug 6, 2013 at 11:30 PM, Ian Hickson i...@hixie.ch wrote: On Thu, 27 Jun 2013, Philip Jägenstedt wrote: In a discussion about a click to play/pause feature for Opera on Android, the issue of click event handlers came up.[1] The problem is that pages can do things like

[whatwg] Should video controls generate click events?

://codereview.chromium.org/17391015 [2] http://people.opera.com/~philipj/click.html [3] http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-June/031916.html (search for As with the post Simon cites above) -- Philip Jägenstedt Opera Software

Re: [whatwg] Feature Request: Media Elements as Targets for Links

of the spec that would be affected is http://www.whatwg.org/specs/web-apps/current-work/multipage/history.html#scroll-to-fragid, can you give more details about the changes you'd make? -- Philip Jägenstedt Core Developer Opera Software

Re: [whatwg] [mimesniff] Review requested on MIME Sniffing Standard

in the spec even if not all browser vendors want to do the same. -- Philip Jägenstedt Core Developer Opera Software

Re: [whatwg] TextTrack and addCue

element and then move the cues to the actual track, why is this less than ideal? -- Philip Jägenstedt Core Developer Opera Software

Re: [whatwg] metadata attribute for media

that would be better than just letting authors pass that metadata out-of-band using any representation they like, but what use cases are you trying to cover here? -- Philip Jägenstedt Core Developer Opera Software

Re: [whatwg] TextTrack and addCue

On Thu, 27 Sep 2012 10:35:26 +0200, Cyril Concolato cyril.concol...@telecom-paristech.fr wrote: Hi Philip, Le 9/27/2012 10:30 AM, Philip Jägenstedt a écrit : On Wed, 26 Sep 2012 21:41:34 +0200, Cyril Concolato cyril.concol...@telecom-paristech.fr wrote: Hi all, Has it been considered

Re: [whatwg] alt and title attribute exception

browser users and likely to remain so. I don't know what conclusions to draw or what the spec should say, but to me it seems unwise to use the title attribute at all... -- Philip Jägenstedt Core Developer Opera Software

Re: [whatwg] alt and title attribute exception

On Wed, 01 Aug 2012 14:56:23 +0200, Henri Sivonen hsivo...@iki.fi wrote: On Tue, Jul 31, 2012 at 12:18 PM, Philip Jägenstedt phil...@opera.com wrote: When this was last discussed in the HTML WG (January 2012) I opened a bug (MOBILE-275) for Opera Mobile to expose the title attribute in our

Re: [whatwg] alt and title attribute exception

to use any other new or existing attribute unless mobile browsers expose them in some way. -- Philip Jägenstedt Core Developer Opera Software

Re: [whatwg] alt and title attribute exception

On Tue, 31 Jul 2012 11:48:52 +0200, Chaals McCathieNevile w...@chaals.com wrote: On Tue, 31 Jul 2012 11:18:37 +0200, Philip Jägenstedt phil...@opera.com wrote: AFAICT there's also no way to read the alt attribute on Opera Mobile. You mean title, right? (alt can be read by turning

Re: [whatwg] video element not ready for prime time

source elements are added, and I still am. -- Philip Jägenstedt Core Developer Opera Software

Re: [whatwg] So if media-queries aren't for determining the media to be used what are they for?

tell, it's mostly useless and I've never heard of it actually being used. The correct way to handle different screen sizes and bandwidth constraints is adaptive streaming. Simon Pieters has suggested simply dropping the attribute and I would not object to that. -- Philip Jägenstedt Core

Re: [whatwg] source media attribute behavior, static or dynamic ?

that this is exactly what has been implemented in Opera -- the media attribute is only considered at the point in the resource selection algorithm that the spec requires. -- Philip Jägenstedt Core Developer Opera Software

Re: [whatwg] [media] played member expected behavior.

this yet, but I agree that must be played, since an empty range would violate the definition http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html#normalized-timeranges-object. -- Philip Jägenstedt Core Developer Opera Software

Re: [whatwg] Encoding: big5 and big5-hkscs

On Mon, 09 Apr 2012 03:08:20 +0200, Øistein E. Andersen li...@coq.no wrote: On 8 Apr 2012, at 18:03, Philip Jägenstedt wrote: On Sat, 07 Apr 2012 16:04:55 +0200, Øistein E. Andersen li...@coq.no wrote: Suggested change: map C6CD to U+5E7A. These are the existing mappings: C6CD

Re: [whatwg] Encoding: big5 and big5-hkscs

On Sat, 07 Apr 2012 16:04:55 +0200, Øistein E. Andersen li...@coq.no wrote: On Fri Apr 6 14:03:22 PDT 2012, Philip Jägenstedt philipj at opera.com wrote: So, http://people.opera.com/philipj/2012/04/06/big5-foolip.txt is the mapping I suggest, with 18594 defined mappings and 1188 U+FFFD

Re: [whatwg] Encoding: big5 and big5-hkscs

a chunk of UTF-8 in meta, so I looked no further. -- Philip Jägenstedt Core Developer Opera Software

Re: [whatwg] Encoding: big5 and big5-hkscs

On Fri, 06 Apr 2012 12:54:53 +0200, Philip Jägenstedt phil...@opera.com wrote: As a starting point for the spec, I suggest taking the intersection of opera-hk, firefox-hk and chrome-hk. I've written a script in https://gitorious.org/whatwg/big5 to generate the mapping that I think makes

Re: [whatwg] Encoding: big5 and big5-hkscs

On Fri, 06 Apr 2012 15:42:26 +0200, Philip Jägenstedt phil...@opera.com wrote: These are the ranges that need more investigation. Sorry for the monologue, but investigate I did. These are the interesting ones: C6CF = opera-hk: U+FFFD � firefox: U+5EF4 廴 chrome: U+F6DF  firefox-hk: U

Re: [whatwg] [media] startOffsetTime, also add startTime?

On Wed, 04 Apr 2012 20:56:03 +0200, Ian Hickson i...@hixie.ch wrote: On Wed, 4 Apr 2012, Philip Jägenstedt wrote: In current Opera and Firefox the timeline is always normalized to start at 0, so the time that corresponds to 0 in the original timeline would be at a negative currentTime

Re: [whatwg] [media] startOffsetTime, also add startTime?

On Wed, 04 Apr 2012 02:25:01 +0200, Robert O'Callahan rob...@ocallahan.org wrote: On Tue, Apr 3, 2012 at 9:28 PM, Philip Jägenstedt phil...@opera.com wrote: AFAIK, no browser supports any format for video that does not have timestamps. I have patches being reviewed that add support

Re: [whatwg] [media] startOffsetTime, also add startTime?

On Tue, 03 Apr 2012 19:13:12 +0200, Ian Hickson i...@hixie.ch wrote: On Tue, 3 Apr 2012, Philip Jägenstedt wrote: It could also do with a good example. The spec says: If the media resource specifies an explicit start time and date, then that time and date should be considered

Re: [whatwg] [media] startOffsetTime, also add startTime?

Thanks for the spec changes, startDate is now in a state where I'd be happy to implement it! More comments inline: On Tue, 03 Apr 2012 02:21:43 +0200, Ian Hickson i...@hixie.ch wrote: On Fri, 9 Mar 2012, Philip Jägenstedt wrote: On Thu, 08 Mar 2012 19:16:40 +0100, Ian Hickson i...@hixie.ch

Re: [whatwg] Encoding: big5 and big5-hkscs

of all browsers? 2. Does that subset include anything mapping to the PUA? 3. Do Hong Kong or Taiwan sites depend on charCodeAt returning values in the PUA? 4. Would hacks be needed on the font-loading side if browsers started using a more correct mapping? -- Philip Jägenstedt Core Developer

Re: [whatwg] [media] startOffsetTime, also add startTime?

On Fri, 09 Mar 2012 15:40:26 +0100, Philip Jägenstedt phil...@opera.com wrote: let me first try to summarize what I think the spec says: * currentTime need not start at 0, for streams it will typically represent for how long the server has been serving a stream. * duration

Re: [whatwg] [media] startOffsetTime, also add startTime?

On Thu, 08 Mar 2012 19:16:40 +0100, Ian Hickson i...@hixie.ch wrote: (Oops, sorry. Missed these e-mails in my earlier reply.) On Thu, 8 Mar 2012, Philip Jägenstedt wrote: On Wed, 07 Mar 2012 11:56:42 +0100, Odin Hørthe Omdal odi...@opera.com wrote: startOffsetTime seem to leave people

Re: [whatwg] [media] startOffsetTime, also add startTime?

suggest dropping it from the spec. -- Philip Jägenstedt Core Developer Opera Software

Re: [whatwg] [media] startOffsetTime, also add startTime?

On Thu, 08 Mar 2012 11:11:06 +0100, Philip Jägenstedt phil...@opera.com wrote: As hinted above, I don't think that startOffsetTime should really be the first choice for trying to sync live streams. However, knowing the date of a video is still useful, potentially even for the streaming

Re: [whatwg] video element not ready for prime time

interface. For audio controls you could always make the controls look dead of course, to make it more clear that there was a problem. -- Philip Jägenstedt Core Developer Opera Software

Re: [whatwg] Microdata feedback

On Thu, 08 Dec 2011 22:04:41 +0100, Ian Hickson i...@hixie.ch wrote: I changed the spec as you suggest. Thanks! -- Philip Jägenstedt Core Developer Opera Software

Re: [whatwg] WebVTT feedback (and some other video feedback that snuck in)

language metadata, this is impossible to do reliably for CJK text. We're going to be doing the same script detection heuristics that we do on web pages. Differentiating between simplified Chinese, traditional Chinese and Japanese isn't particularly hard. -- Philip Jägenstedt Core Developer

Re: [whatwg] WebVTT feedback (and some other video feedback that snuck in)

On Sat, 03 Dec 2011 17:47:15 +0100, Glenn Maynard gl...@zewt.org wrote: On Sat, Dec 3, 2011 at 11:38 AM, Philip Jägenstedt phil...@opera.comwrote: We're going to be doing the same script detection heuristics that we do on web pages. Differentiating between simplified Chinese, traditional

Re: [whatwg] WHATWG on Google+

. -- Philip Jägenstedt Core Developer Opera Software

Re: [whatwg] HTML5 video seeking

. -- Philip Jägenstedt Core Developer Opera Software

Re: [whatwg] HTML5 video seeking

it? [1] http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-January/029806.html -- Philip Jägenstedt Core Developer Opera Software

Re: [whatwg] DOMTokenList methods would be more useful with a space separated token list

token is added or if all tokens are added? -- Philip Jägenstedt Core Developer Opera Software

Re: [whatwg] SRT research: timestamps

the fault of overly-lenient parsers that these things happen in the first place. A point Philip Jägenstedt has made is that it's sufficiently tedious to verify correct subtitle playback that authors are unlikely to do so with any vigilance. Therefore the better trade-off is to make the parser

Re: [whatwg] SRT research: timestamps

On Thu, 06 Oct 2011 05:46:15 +0200, Glenn Maynard gl...@zewt.org wrote: On Wed, Oct 5, 2011 at 7:51 PM, Ralph Giles gi...@mozilla.com wrote: A point Philip Jägenstedt has made is that it's sufficiently tedious to verify correct subtitle playback that authors are unlikely to do so with any

[whatwg] track / WebVTT issues

, and be modified to the startTime of the following cue (in source order) if there is a following cue. This would IMO be quite neat, but is the use case strong enough? [1] http://openvideoconference.org/standards-for-video-accessibility/ [2] http://wiki.whatwg.org/wiki/WebVTT -- Philip Jägenstedt

Re: [whatwg] video preload implementation feedback

On Thu, 18 Aug 2011 04:50:17 +0200, Chris Pearce cpea...@mozilla.com wrote: I implemented preload support in Firefox. On 18/08/2011 3:44 a.m., Philip Jägenstedt wrote: I'd very much like to see feedback from other implementors. Are you happy with treating autoplay and preload as just

Re: [whatwg] video preload implementation feedback

On Thu, 18 Aug 2011 05:36:42 +0200, Bjartur Thorlacius svartma...@gmail.com wrote: Þann mið 17.ágú 2011 15:44, skrifaði Philip Jägenstedt: I'd very much like to see feedback from other implementors. Are you happy with treating autoplay and preload as just hints as in [4] or do you think

[whatwg] video preload implementation feedback

/show_bug.cgi?id=12595 [9] http://www.w3.org/Bugs/Public/show_bug.cgi?id=12596 [10] http://www.w3.org/Bugs/Public/show_bug.cgi?id=12608 -- Philip Jägenstedt Core Developer Opera Software

Re: [whatwg] Microdata - Handling the case where a string is upgraded to an object

On Mon, 18 Jul 2011 22:01:37 +0200, Tab Atkins Jr. jackalm...@gmail.com wrote: On Mon, Jul 18, 2011 at 4:20 AM, Philip Jägenstedt phil...@opera.com As for the solution, are you suggesting that .itemValue return a special object which is like HTMLElement in all regards except for how

Re: [whatwg] Microdata - Handling the case where a string is upgraded to an object

that .itemValue return a special object which is like HTMLElement in all regards except for how it toString()s? -- Philip Jägenstedt Core Developer Opera Software

Re: [whatwg] Microdata feedback

want to ensure that RDF consumers don't depend on non-treeness, then this should change as well. [1] http://www.whatwg.org/specs/web-apps/current-work/multipage/microdata.html#examples-4 -- Philip Jägenstedt Core Developer Opera Software

  1   2   3   4   >