Re: [whatwg] JavaScript function for closing tags

We could specify that WebVTT cues of type metadata should contain valid JSON - that would make sense to me. Cues of type captions or subtitles stupid get parsed dune by the addCue() function of the texttrack API - but not all browsers implement this yet. Would be worth registering bugs on browsers

Re: [whatwg] JavaScript function for closing tags

Hi Michael, It seems to me that the TextTrack API is made for this use case. Why does it not work for you? Cheers, Silvia. On Sat, Oct 14, 2017 at 4:36 PM, Michael A. Peters wrote: > There does not seem to be a JavaScript API for closing open tags. > > This is problematic when dealing with Web

Re: [whatwg] metadata

On Mon, Apr 24, 2017 at 5:04 AM, Kevin Marks wrote: > On Sun, Apr 23, 2017 at 5:58 PM, Andy Valencia > wrote: >> === Dynamic versus static metadata >> >> Pretty much all audio formats have at least one metadata format. While >> some apparently can embed them at time points, this is not used by a

Re: [whatwg] Removing mediagroup/MediaController from HTML

On Fri, Oct 2, 2015 at 10:27 AM, Domenic Denicola wrote: > From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of > >> is removal really the right thing to do, given that we have an >> implementation? > > I agree this is a problematic question. I opened > https://github.com/whatwg/htm

Re: [whatwg] Persistent and temporary storage

On 15 Mar 2015 03:35, "Glenn Maynard" wrote: > > On Fri, Mar 13, 2015 at 3:13 PM, Silvia Pfeiffer < silviapfeiff...@gmail.com> wrote: >> >> On 14 Mar 2015 05:49, "Tab Atkins Jr." wrote: >> > Users install a relatively small number of apps, and

Re: [whatwg] Persistent and temporary storage

On 14 Mar 2015 05:49, "Tab Atkins Jr." wrote: > > On Fri, Mar 13, 2015 at 6:58 AM, Janusz Majnert wrote: > > On 13.03.2015 13:50, Anne van Kesteren wrote: > >> A big gap with native is dependable storage for applications. I > >> started sketching the problem space on this wiki page: > >> > >>

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

On Tue, Nov 4, 2014 at 10:24 AM, Brendan Long wrote: > > On 11/03/2014 04:20 PM, Silvia Pfeiffer wrote: >> On Tue, Nov 4, 2014 at 3:56 AM, Brendan Long wrote: >> Right, that was the original concern. But how realistic is the >> situation of n video tracks and m caption tr

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

On Tue, Nov 4, 2014 at 3:56 AM, Brendan Long wrote: > > On 10/27/2014 08:43 PM, Silvia Pfeiffer wrote: >> On Tue, Oct 28, 2014 at 2:41 AM, Philip Jägenstedt wrote: >>> On Sun, Oct 26, 2014 at 8:28 AM, Silvia Pfeiffer >>> wrote: >>>> On Thu,

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

On Tue, Oct 28, 2014 at 2:41 AM, Philip Jägenstedt wrote: > On Sun, Oct 26, 2014 at 8:28 AM, Silvia Pfeiffer > wrote: >> >> On Thu, Oct 23, 2014 at 2:01 AM, Philip Jägenstedt wrote: >> > On Sun, Oct 12, 2014 at 11:45 AM, Silvia Pfeiffer >> > wrote: >>

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

On Thu, Oct 23, 2014 at 2:33 AM, Bob Lund wrote: > > > On 10/22/14, 9:01 AM, "Philip Jägenstedt" wrote: > >>On Sun, Oct 12, 2014 at 11:45 AM, Silvia Pfeiffer >> wrote: >>> >>> Hi all, >>> >>> In the Inband Text Tracks Communi

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

On Thu, Oct 23, 2014 at 2:01 AM, Philip Jägenstedt wrote: > On Sun, Oct 12, 2014 at 11:45 AM, Silvia Pfeiffer > wrote: >> >> Hi all, >> >> In the Inband Text Tracks Community Group we've recently had a >> discussion about a proposal by HbbTV. I'd li

Re: [whatwg] Gapless playback problems with web audio standards

Have you tried media source extensions? Best Regards, Silvia. On 26 Oct 2014 00:30, "David Kendal" wrote: > Hi, > > > > dpk > >

[whatwg] How to expose caption tracks without TextTrackCues

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 thread is at http://lists.w3.org/Archives/Public/public-inbandtracks/2014Sep/0008.html , but

Re: [whatwg] Web API for Health Sensors

; > media/communication thing. >> > >> > To me it's like the difference between geolocation and having an API on >> > top of geolocation that tells you how close you are to a hospital. You have >> > the tools for that. Why the desire for a spe

Re: [whatwg] Adding a property to navigator for getting device model

On 3 Oct 2014 14:25, "eberhard speer jr." wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi, > > Maybe you missed my initial message : I am a contributor [IPMC] to the > Apache DeviceMap Project. [http://incubator.apache.org/devicemap/] > > DeviceMap does expert "UA-sniffing" both

Re: [whatwg] Adding a property to navigator for getting device model

On 3 Oct 2014 04:45, "Mounir Lamouri" wrote: > > On Fri, 3 Oct 2014, at 04:39, Jonas Sicking wrote: > > On Thu, Oct 2, 2014 at 3:57 AM, Mounir Lamouri wrote: > > > On Wed, 1 Oct 2014, at 19:43, Jonas Sicking wrote: > > >> On Wed, Oct 1, 2014 at 2:27 AM, Mounir Lamouri wrote: > > >> > On Wed, 1 O

Re: [whatwg] Adding a property to navigator for getting device model

On Wed, Oct 1, 2014 at 7:43 PM, Jonas Sicking wrote: > On Wed, Oct 1, 2014 at 2:27 AM, Mounir Lamouri wrote: >> On Wed, 1 Oct 2014, at 15:01, Jonas Sicking wrote: >>> On Tue, Sep 30, 2014 at 4:40 AM, Mounir Lamouri >>> wrote: >>> > On Wed, 24 Sep 2014, at 11:54, Jonas Sicking wrote: >>> >> Thoug

Re: [whatwg] Adding a property to navigator for getting device model

On 24 Sep 2014 20:40, "James Graham" wrote: > > On 24/09/14 02:54, Jonas Sicking wrote: > > > In the meantime, I'd like to add a property to window.navigator to > > enable websites to get the same information from there as is already > > available in the UA string. That would at least help with th

Re: [whatwg] (no subject)

On Sun, Sep 14, 2014 at 12:17 PM, wrote: > > > On 9/12/14, Silvia Pfeiffer wrote: >> >> What I'd you're a long way away from any medical help? >> > > What? s/I'd/if/ (sorry - mobile keyboard) >> In my mind this is part of the larger driv

Re: [whatwg] Web API for Health Sensors

ubject matter > experts and devs within that field than general web technology nerds? > > On Fri, Sep 12, 2014 at 5:52 PM, Silvia Pfeiffer < > silviapfeiff...@gmail.com> wrote: > >> Browsers have been dealing with private personal data for a while now, >> that inclu

Re: [whatwg] Web API for Health Sensors

> Delfin Ramirez > +34 633 589231 > del...@segonquart.net > > twitter: delfinramirez > > IRC: segonquart Skype: segonquart > > http://segonquart.net > > http://delfiramirez.info > > On 2014-09-13 00:52, Silvia Pfeiffer wrote: > > Browsers have

Re: [whatwg] Web API for Health Sensors

Browsers have been dealing with private personal data for a while now, that includes video camera & microphone input, geolocation and more. Health data isn't so different in that respect. There are mechanisms to deal with privacy already in the browser. But indeed: a spec would need to consider suc

Re: [whatwg] Web API for Health Sensors

I believe a way to directly read health data into web apps with a browser api (JavaScript) is an interesting idea. You could then have a webrtc video conference with your doctor and he could read out your pulse and other health data directly from your device live and give you an opinion. Seeing as

Re: [whatwg] Canvas-Only Document Type

Has anyone considered the accessibility implications of this? IIUC accessibility for canvas is provided through extra dom elements. So, this would defeat that purpose. Silvia. On Tue, Jul 8, 2014 at 8:39 AM, Brian M. Blakely wrote: > Hi Ashley, > > With the budding of Canvas 2D and WebGL UI fram

Re: [whatwg] HTTP status code from JavaScript

You might want to review http://wiki.whatwg.org/wiki/FAQ . In particular: http://wiki.whatwg.org/wiki/FAQ#Is_there_a_process_for_adding_new_features_to_a_specification.3F HTH, Silvia. On Mon, May 26, 2014 at 10:02 AM, Michael Heuberger wrote: > Hi Jasper > > On 26/05/14 08:09, Jasper St. Pier

Re: [whatwg] HTTP status code from JavaScript

Hi Michael, On Sun, May 25, 2014 at 3:10 PM, Michael Heuberger wrote: > Hi David > > Interesting. Yes and no, I agree with some. See my comments below: > > On 25/05/14 06:53, David Bruant wrote: >> Le 23/05/2014 10:04, Michael Heuberger a écrit : > - Display a beautiful 404 page and hide part

Re: [whatwg] HTTP status code from JavaScript

I had to deal with this on a script created IMG element the other day. I used onerror to deal with it. For xmlhttprequest you can use the status field. Why is that not enough? Silvia. On 23 May 2014 18:06, "Michael Heuberger" < michael.heuber...@binarykitchen.com> wrote: > Good points Mat > > I

Re: [whatwg] Question on HTML5 media element, the seeking algorithm and the seeked event

On Sat, Dec 7, 2013 at 6:31 AM, Ian Hickson wrote: > On Fri, 8 Nov 2013, Andres Gomez wrote: >> >> because of my recent work related to a bug and test in WebKit, I've >> gotten to deal with the HTML5 media element's "seeking" algorithm and >> "seeked" event. >> >> During my analysis I was unable,

Re: [whatwg] responsive imgs proposition (Re: The src-N proposal)

On 13 Nov 2013 11:33, "Jirka Kosek" wrote: > > On 13.11.2013 2:56, Christian Biesinger wrote: > > For a bit more presentation, and while we're inventing new syntax > > anyway, how about this: > > > > > > @media (min-width: 480px) { > > .artdirected { content: replaced url(attr(src-small)); } >

Re: [whatwg] responsive imgs proposition (Re: The src-N proposal)

On Wed, Nov 13, 2013 at 9:56 AM, Christian Biesinger wrote: > On Tue, Nov 12, 2013 at 3:06 PM, Markus Ernst wrote: >> What I don't like about CSS approaches is the fact that changing the source >> of an image is fundamentally different from changing a dimension or color of >> an element. This is

Re: [whatwg] Reconsidering how we deal with text track cues

On Wed, Sep 4, 2013 at 7:38 AM, Ian Hickson wrote: > On Mon, 17 Jun 2013, Silvia Pfeiffer wrote: >> On Thu, Jun 13, 2013 at 3:08 AM, Ian Hickson wrote: >> > On Wed, 12 Jun 2013, Silvia Pfeiffer wrote: >> >> >> >> As we continue to evolve the functionali

Re: [whatwg] Should generate click events?

On Wed, Aug 21, 2013 at 8:59 PM, Simon Pieters wrote: > The problem was this: if you want to do something when a user clicks on a > video but not when the user interacts with the native controls, you're > basically out of luck. > No, you can do as you do below: you can define an onclick handler

Re: [whatwg] Should generate click events?

On Wed, Aug 21, 2013 at 9:11 AM, Tab Atkins Jr. wrote: > On Tue, Aug 20, 2013 at 3:46 PM, Silvia Pfeiffer > wrote: > > On Wed, Aug 21, 2013 at 8:32 AM, Tab Atkins Jr. > > wrote: > >> > >> On Tue, Aug 20, 2013 at 3:28 PM, Silvia Pfeiffer > >> wrote:

Re: [whatwg] Should generate click events?

On Wed, Aug 21, 2013 at 8:57 AM, Bob Lund wrote: > > > On 8/20/13 4:46 PM, "Silvia Pfeiffer" wrote: > > >On Wed, Aug 21, 2013 at 8:32 AM, Tab Atkins Jr. > >wrote: > > > >> On Tue, Aug 20, 2013 at 3:28 PM, Silvia Pfeiffer > >> wr

Re: [whatwg] Should generate click events?

On Wed, Aug 21, 2013 at 8:32 AM, Tab Atkins Jr. wrote: > On Tue, Aug 20, 2013 at 3:28 PM, Silvia Pfeiffer > 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 generate click events?

On Wed, Aug 21, 2013 at 7:52 AM, Edward O'Connor wrote: > Hi, > > >>> [W]e do want users to be able to bring up the native controls via a > >>> context menu and be able to use them regardless of what the page > >>> does in its event handlers. So, I request that the spec be explicit > >>> that int

Re: [whatwg] Forms-related feedback

On Tue, Jul 30, 2013 at 10:43 AM, Ian Hickson wrote: > On Tue, 30 Jul 2013, Silvia Pfeiffer wrote: >> >> I actually think we need to distinguish between local and floating time >> zones. >> >> When using datetime-local, I would actually expect that the browser &

Re: [whatwg] Forms-related feedback

On Tue, Jul 30, 2013 at 9:59 AM, Tab Atkins Jr. wrote: > On Mon, Jul 29, 2013 at 4:50 PM, Jonas Sicking wrote: >> Ian, has *any* implementer expressed a preference for implementing a >> picker which allows selecting date+time+timezone? I.e. one that >> returns UTC dates? > > The Gmail time-picker

Re: [whatwg] Proposal: createImageBitmap should return a "Promise" instead of using a callback

wrote: > On Thu, 18 Jul 2013, Silvia Pfeiffer wrote: >> >> In this case you did remove the non-promise based approach - presumably >> because it has not been implemented in browsers yet, which is fair >> enough for browsers. > > Right. > > >> However, f

Re: [whatwg] Proposal: createImageBitmap should return a "Promise" instead of using a callback

On Thu, Jul 18, 2013 at 10:39 AM, Ian Hickson wrote: > On Thu, 18 Jul 2013, Silvia Pfeiffer wrote: >> >> We have the same issues with WebRTC, which already has a callback based >> API, but there is a suggestion to replace/augment with a Promise based >> API, so I ju

Re: [whatwg] Proposal: createImageBitmap should return a "Promise" instead of using a callback

On Thu, Jul 18, 2013 at 10:00 AM, Ian Hickson wrote: > On Wed, 17 Jul 2013, Justin Novosad wrote: >> On Wed, Jul 17, 2013 at 6:54 PM, Ian Hickson wrote: >> > On Thu, 18 Jul 2013, Silvia Pfeiffer wrote: >> > > At the same time, I think we should follow a clear pa

Re: [whatwg] Proposal: createImageBitmap should return a "Promise" instead of using a callback

On 18 Jul 2013 07:57, "Ian Hickson" wrote: > > On Thu, 18 Jul 2013, Silvia Pfeiffer wrote: > > > > > > There are basically two styles: > > > > > > - constructors (new Date(), new Function(), etc) > > > - f

Re: [whatwg] Proposal: createImageBitmap should return a "Promise" instead of using a callback

On 18 Jul 2013 07:08, "Ian Hickson" wrote: > > On Wed, 19 Jun 2013, Justin Novosad wrote: > > > > I was about to launch the implementation of window.createImageBitmap in > > Blink, and I received feedback on the blink-dev mailing list that the > > "Promise" API is the wave of the future for asynch

Re: [whatwg] Feature Request for the-video-element to support audiochannel descriptions

Note that Mozilla have introduced .mozChannels for this: https://developer.mozilla.org/en-US/docs/Web/API/HTMLMediaElement . The Web Audio API have created what is called an AudioNode, which includes the number of channels: https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html#Audi

Re: [whatwg] Reconsidering how we deal with text track cues

On Tue, Jun 18, 2013 at 12:57 PM, Brendan Long wrote: > On 06/17/2013 12:41 AM, Silvia Pfeiffer wrote: >>> Why VTTCaptionCue and not just HTMLCue? It seems like any cue that can >>> be rendered needs to be able to provide its content as HTML, and once we >>> have th

Re: [whatwg] Reconsidering how we deal with text track cues

On Thu, Jun 13, 2013 at 3:08 AM, Ian Hickson wrote: > On Wed, 12 Jun 2013, Silvia Pfeiffer wrote: >> >> As we continue to evolve the functionality of text tracks, we will >> introduce more complex other structured content into cues and we will >> want browsers to pars

[whatwg] Reconsidering how we deal with text track cues

Hi all, The model in which we have looked at text tracks ( element of media elements) thus far has some issues that I would like to point out in this email and I would like to suggest a new way to look at tracks. This will result in changes to the HTML and WebVTT specs and has an influence on othe

Re: [whatwg] Pull requests for HTML5 spec?

You can make pull requests for the master branch for https://github.com/w3c/html , which will end up in the HTML5.1 spec [1]. Patches to the CR branch end up in the HTML5.0 spec [2] if accepted. For anything that's more than editorial, register a bug on https://www.w3.org/Bugs/Public/enter_bug.cgi?

Re: [whatwg] Forced subtitles

default subtitle should be the language specified of the page or video. > But, if a specific subtitle language is told to the browser it should use > that. > > > On Thu, Apr 11, 2013 at 7:35 PM, Eric Carlson >wrote: > > > > > On Apr 11, 2013, at 3:54 PM, Silvia Pfei

Re: [whatwg] Forced subtitles

I think Eric is right - we need a new @kind="forced" or @kind="forcedSubtitles" value on track elements, because they behave differently from the subtitle kind: * are not listed in a track menu * are turned on by browser when no other subtitle or caption track is on * multiple forced subtitles trac

Re: [whatwg] Proposal: channel attribute on HTMLMediaElement

These all sound like important use cases. What I am reading is that there is a need to manage mute state override, playback state management based on browser state, and latency management (some sort of urgency measure). Is there a reason that you have munged these into a single attribute? I am aski

Re: [whatwg] Hide placeholder on input controls on focus

On 23 Mar 2013 10:00, "Tim Streater" wrote: > > On 22 Mar 2013 at 22:32, Glenn Maynard wrote: > > > I start typing after I read the placeholder. Hiding placeholder text just > > because I focused the input is wrong; I may not have read it yet. > > You shouldn't start typing until you *have* read

Re: [whatwg] use of article to markup comments

On Mon, Feb 18, 2013 at 12:19 AM, Nils Dagsson Moskopp < n...@dieweltistgarnichtso.net> wrote: > "Bruce Lawson" schrieb am Sat, 26 Jan 2013 13:30:18 > -: > > > In short, why should the spec suggest any specific method of marking > > up comments? > > As someone who is interested in semantics a

Re: [whatwg] Is now an official HTML5 element?

> I will try to determine what topic > belongs to which group in the future. The simple answer is: have your discussion wherever you feel comfortable to have it. Even if the specs differ, in the end what matters is what browsers implement. If a discussion about a topic is more appropriate in a di

Re: [whatwg] A plea to Hixie to adopt

On Wed, Nov 28, 2012 at 4:26 PM, Ian Hickson wrote: > > All of this has already been discussed on this mailing list, so this is > not new information. I would please refer you to the earlier messages on > this topic. In general, unless there is substantial new information, > please don't keep pos

Re: [whatwg] A plea to Hixie to adopt

On Wed, Nov 28, 2012 at 10:35 AM, Ian Hickson wrote: > On Wed, 28 Nov 2012, Silvia Pfeiffer wrote: > > > > > > But we already have this. The main content is whatever content isn't > > > marked up as not being main content (anything not marked up with > >

Re: [whatwg] A plea to Hixie to adopt

On Sat, Nov 17, 2012 at 11:01 AM, Ian Hickson wrote: [..] > > On Sat, 10 Nov 2012, Maciej Stachowiak wrote: > > > > I personally think would be useful. I don't think it has a huge > > benefit, but it has modest benefits, like , , > > and . I also think the implementation costs are low. The > >

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

On Tue, Nov 27, 2012 at 11:10 AM, Nils Dagsson Moskopp < n...@dieweltistgarnichtso.net> wrote: > > Maybe I am misunderstanding you here, but I think the fragment > identifier abuse by JavaScript authors can be of use here – it would > allow for a simple polyfill that could quickly propagate use an

Re: [whatwg] [mimesniff] Handling container formats like Ogg

For Ogg, if you rely on the Ogg files having a Skeleton track [1], it's not actually difficult at all, since the mime type of the codecs used in the tracks that Skeleton is describing are explicitly included in Skeleton. Then all you have to do is check which codec mime types are present to make t

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

Can you provide an example markup and an example URL that you think will solve your use case? I'm asking because we don't use the name attribute any more in HTML5, because we have the id attribute on all elements. Thus, it is always possible to hyperlink directly to a video element using a hash on

Re: [whatwg] A plea to Hixie to adopt

On Fri, Nov 16, 2012 at 12:21 PM, Eitan Adler wrote: > On 15 November 2012 19:20, Silvia Pfeiffer > wrote: > > On Fri, Nov 16, 2012 at 1:45 AM, Tim Leverett wrote: > > > >> >> Con: Adding a element adds redundancy to the [role="main"] > >>

Re: [whatwg] A plea to Hixie to adopt

On Fri, Nov 16, 2012 at 1:45 AM, Tim Leverett wrote: > >> Con: Adding a element adds redundancy to the [role="main"] > attribute. > > I don't see why this is a con, if main is mapped to role=main in the > browser it means that authors won't have to. Also adding > aside/article/footer etc adds re

Re: [whatwg] A plea to Hixie to adopt

On Thu, Nov 15, 2012 at 12:17 PM, Tim Leverett wrote: > > > Are you fundamentally distrusting the author in all semantic markup? > > In some circumstances, yes. Most of the work I've done so far has been in > environments where programmers write code, and editors write content. > Typically the co

Re: [whatwg] A plea to Hixie to adopt

ng to make the point that an algorithmic approach to > finding the main content of a document would still be necessary with or > without the element. > > ☺ > > > > On Tue, Nov 13, 2012 at 7:03 PM, Silvia Pfeiffer < > silviapfeiff...@gmail.com> wrote: > >&g

Re: [whatwg] A plea to Hixie to adopt

On Wed, Nov 14, 2012 at 4:25 AM, Tim Leverett wrote: > > Explicit author markup would make such a task so much easier. > > Only if every author marked up their code correctly. If some authors use > incorrect markup, then an algorithm would still be necessary for > determining if each usage was co

Re: [whatwg] A plea to Hixie to adopt

g and evaluation algorithm. I'm sure a lot of other people had to solve this problem as well and have done so in their own special way. Explicit author markup would make such a task so much easier. Regards, Silvia. On Tue, Nov 13, 2012 at 11:53 AM, Silvia Pfeiffer wrote: > On Tue, Nov 13,

Re: [whatwg] A plea to Hixie to adopt

On Tue, Nov 13, 2012 at 5:26 AM, Jens O. Meiert wrote: > Should be optional or required? > > I’d deem an optional to be nonsense because it suggests > documents are inherently without goal, or focus. > > I’d deem a required to be nonsense because we already have an > (implied) element, and b

Re: [whatwg] A plea to Hixie to adopt

On Thu, Nov 8, 2012 at 3:00 AM, Markus Ernst wrote: > Am 07.11.2012 15:48 schrieb Jukka K. Korpela: > > I suppose that the heuristics would include recognizing a element >> to which class "main" has been assigned. Then one could argue that >> is not needed, as authors can keep using , as >> mi

Re: [whatwg] Sortable Tables

On Wed, Nov 7, 2012 at 8:37 PM, Jirka Kosek wrote: > On 6.11.2012 23:18, Silvia Pfeiffer wrote: > > > * data-type: date, number, text etc which determines the comparison > > function used in sort > > It would be very difficult to support sorting on dates and numbers as in

Re: [whatwg] Sortable Tables

On Wed, Nov 7, 2012 at 6:55 AM, Boris Zbarsky wrote: > On 11/6/12 11:39 AM, Ojan Vafai wrote: > >> This is a use-case that I absolutely think it makes sense to address. >> > > Agreed. Not that I can commit to implementing, necessarily, but I do > think this is a common want. > > Great to hear br

Re: [whatwg] feedback

On Wed, Oct 3, 2012 at 6:41 AM, Jer Noble wrote: > On Sep 17, 2012, at 12:43 PM, Ian Hickson wrote: > >> On Mon, 9 Jul 2012, adam k wrote: >>> >>> i have a 25fps video, h264, with a burned in timecode. it seems to be >>> off by 1 frame when i compare the burned in timecode to the calculated >>>

Re: [whatwg] New URL Standard

On Tue, Sep 25, 2012 at 9:48 PM, Robin Berjon wrote: > On 25/09/2012 01:07 , Glenn Maynard wrote: >> >> On Mon, Sep 24, 2012 at 12:30 PM, Tab Atkins Jr. >> wrote: >>> >>> I suggest just making it a map from String->[String]. You probably >>> want a little bit of magic - if the setter receives an

Re: [whatwg] exposing metadata on replaced elements (was: feedback)

On Tue, Sep 18, 2012 at 1:19 PM, Rick Waldron wrote: >> >> While we have somewhat of a proposal for exposing metadata to media >> elements through the W3C media annotations WG [1] with the >> getMediaProperty() > > If the function is going to retrieve meta data, why is it named with words > that d

[whatwg] exposing metadata on replaced elements (was: feedback)

Hi Ralph, all, > On Mon, 11 Jun 2012, Ralph Giles wrote: >> >> Recently, we've been considering adding a 'tags' or 'metadata' attribute >> to HTML media elements in Firefox, to allow webcontent access to >> metadata from the playing media resource. In particular we're interested >> in tag data lik

Re: [whatwg] Problem in the Section "4 Elements of HTML => 4.4 Sections => 4.4.2 The Section element

On Fri, Sep 14, 2012 at 4:15 AM, Tab Atkins Jr. wrote: > On Thu, Sep 13, 2012 at 11:09 AM, Jukka K. Korpela wrote: >> And I suppose by weird formation you mean the example that starts with >> >> >> > >>>> >Graduation Ceremony Summer 2022>>> >>>> >> >>> can anybody tell me if t

Re: [whatwg] Missing alt attribute name bikeshedding (was Re: alt="" and the exception)

On Mon, Aug 6, 2012 at 10:31 AM, Maciej Stachowiak wrote: > > On Aug 1, 2012, at 12:56 AM, Ian Hickson wrote: > >> >> We briefly brainstormed some ideas on #whatwg earlier tonight, and one >> name in particular that I think could work is the absurdly long >> >> >> >> This has several key chara

Re: [whatwg] Comments about the track element

Hi Cyril, On Thu, Jul 26, 2012 at 10:03 PM, Cyril Concolato wrote: >> What do you mean here by "positioning issues"? SVG handles the positioning >> within its viewbox and what I propose is to define the size and position of >> this viewbox in the parent coordinate system, i.e. with respect to the

Re: [whatwg] Comments about the track element

On Wed, Jul 25, 2012 at 11:51 PM, Cyril Concolato wrote: > Hi Silvia, > > Le 7/25/2012 3:42 PM, Silvia Pfeiffer a écrit : > >> On Wed, Jul 25, 2012 at 10:55 PM, Henri Sivonen wrote: >>> >>> On Wed, Jul 25, 2012 at 11:24 AM, Silvia Pfeiffer >>>

Re: [whatwg] Comments about the track element

On Wed, Jul 25, 2012 at 11:45 PM, Cyril Concolato wrote: >> Right now it is fully defined how data in a TextTrack (of the defined >> kinds) is displayed on top of the video. As this is as yet unclear for >> SVG resources, > > I wouldn't say it's unclear, I'd say it needs to be specified ;) meaning

Re: [whatwg] Comments about the track element

On Wed, Jul 25, 2012 at 10:55 PM, Henri Sivonen wrote: > On Wed, Jul 25, 2012 at 11:24 AM, Silvia Pfeiffer > wrote: >> But you can use cue.text and parse it as a SVG fragment. > > That would be RSS all over again. :-( To some extent. If we are very clear about what will be in

Re: [whatwg] Comments about the track element

On Wed, Jul 25, 2012 at 6:00 PM, Anne van Kesteren wrote: > On Wed, Jul 25, 2012 at 4:24 AM, Silvia Pfeiffer > wrote: >> You can even use >> getCueAsHTML() to simply hand the SVG to HTML for rendering. > > FWIW, that is not going to work. You need to parse the SVG using

Re: [whatwg] Comments about the track element

Expanding a bit on what Anne said... On Tue, Jul 24, 2012 at 11:18 PM, Cyril Concolato wrote: > Dear WhatWG, > > During the ongoing SVG F2F meeting, the SVG WG discussed the use case of > displaying SVG graphics on top of a video, in a synchronous manner. > > The SVG WG believes that for such use

Re: [whatwg] Why does CanvasRenderingContext2D.drawImage not draw a video's poster?

On Thu, Jul 19, 2012 at 2:46 AM, Charles Pritchard wrote: > On 7/17/2012 11:06 PM, Silvia Pfeiffer wrote: >> >> On Wed, Jul 18, 2012 at 6:57 AM, Charles Pritchard >> wrote: >>> >>> On Jul 17, 2012, at 9:04 PM, Mark Callow >>> wrote: >

Re: [whatwg] Why does CanvasRenderingContext2D.drawImage not draw a video's poster?

On Wed, Jul 18, 2012 at 6:57 AM, Charles Pritchard wrote: > On Jul 17, 2012, at 9:04 PM, Mark Callow wrote: > >> On 18/07/2012 00:17, Silvia Pfeiffer wrote: >>> I think this is simply an idea that hasn't been raised before. I like >>> it. Though even then

Re: [whatwg] Why does CanvasRenderingContext2D.drawImage not draw a video's poster?

I think this is simply an idea that hasn't been raised before. I like it. Though even then sometimes there may be nothing when there is no explicit poster and preload is set to none. Regards, Silvia. On Tue, Jul 17, 2012 at 9:58 AM, Mark Callow wrote: > The spec. for CanvasRenderingContext2D.dra

Re: [whatwg] frame accuracy breaking case for 25fps / status of 29.97fps

On Mon, Jul 9, 2012 at 8:17 PM, Odin Hørthe Omdal wrote: > On Mon, 09 Jul 2012 18:46:20 +0200, adam k wrote: > >> i have a 25fps video, h264, with a burned in timecode. it seems to be off >> by 1 frame when i compare the burned in timecode to the calculated timecode. >> i'm using rob coenen's te

Re: [whatwg] Proposal for HTML5: Motion sensing input device (Kinect, SoftKinetic, Asus Xtion)

On Wed, Jun 27, 2012 at 1:56 PM, Robert O'Callahan wrote: > On Tue, Jun 26, 2012 at 8:22 AM, Tab Atkins Jr. wrote: > >> The ability to capture sound and video from the user's devices and >> manipulate it in the page is already being exposed by the getUserMedia >> function.  Theoretically, a Kinect

Re: [whatwg] make always focusable and interactive content

On Thu, Jun 21, 2012 at 9:09 AM, Chris Double wrote: > On Wed, Jun 20, 2012 at 5:47 PM, Silvia Pfeiffer > wrote: >>> They are in Opera. The spec allows it. >> >> Yes, thankfully one browser has video keyboard interaction. >> > > I just tested Firefox and th

Re: [whatwg] make always focusable and interactive content

On Wed, Jun 20, 2012 at 2:51 PM, Simon Pieters wrote: > On Wed, 20 Jun 2012 05:43:20 +0200, Silvia Pfeiffer > wrote: > >> Hi all, >> >> I recently experimented with keyboard accessibility of media elements. >> >> I found that browsers don't provide a

[whatwg] make always focusable and interactive content

Hi all, I recently experimented with keyboard accessibility of media elements. I found that browsers don't provide a default tabfocus on media elements nor do they provide keyboard interactivity. I had to put explicit @tabindex attributes onto the media elements to allow them to at least receive

Re: [whatwg] metadata attribute for media

On Tue, Jun 12, 2012 at 7:53 AM, Ralph Giles wrote: > Recently, we've been considering adding a 'tags' or 'metadata' attribute > to HTML media elements in Firefox, to allow webcontent access to > metadata from the playing media resource. In particular we're interested > in tag data like creator, t

Re: [whatwg] tabindexscope

On Fri, Jun 8, 2012 at 11:49 AM, Silvia Pfeiffer wrote: > On Fri, Jun 8, 2012 at 6:10 AM, Ian Hickson wrote: >> On Thu, 7 Jun 2012, Silvia Pfeiffer wrote: >>> > >>> > Can you give some examples of real-world pages where the tabindex >>> > attribute h

Re: [whatwg] tabindexscope

On Fri, Jun 8, 2012 at 6:10 AM, Ian Hickson wrote: > On Thu, 7 Jun 2012, Silvia Pfeiffer wrote: >> > >> > Can you give some examples of real-world pages where the tabindex >> > attribute has been used (with difficulty due to the lack of scoping), >> > wh

Re: [whatwg] tabindexscope

On Thu, Jun 7, 2012 at 9:57 AM, Ian Hickson wrote: > On Mon, 30 Jan 2012, Tab Atkins Jr. wrote: >> On Mon, Jan 30, 2012 at 1:54 PM, Ian Hickson wrote: >> > On Tue, 8 Nov 2011, Ojan Vafai wrote: >> >> We keep running into the use case where the physical position matters >> >> for the tab order. Th

Re: [whatwg] s in by quality as well as codec

I believe right now there are two proposals under discussion that are trying to address the adaptive streaming issues: https://dvcs.w3.org/hg/audio/raw-file/tip/streams/StreamProcessing.html and http://dvcs.w3.org/hg/html-media/raw-file/tip/media-source/media-source.html I believe both are still s

Re: [whatwg] Correcting some misconceptions about Responsive Images

On Fri, May 18, 2012 at 6:01 PM, Bruce Lawson wrote: > On Fri, 18 May 2012 01:16:52 +0100, Tab Atkins Jr. > wrote: > >  I believe the CG rules >>> >>> would not allow an employee of a W3C Member company to be a "free agent" >>> though. > > > It appears not. I tried to join the responsive images C

Re: [whatwg] Features for responsive Web design

On Thu, May 17, 2012 at 7:54 PM, Kornel Lesiński wrote: > On Thu, 17 May 2012 02:29:11 +0100, Jacob Mather > wrote: > >> As I said, I understand that it is a hard problem, but the question >> is, is it the correct problem. >> >> There are plenty of reasons not to do it, but is there any actual >>

Re: [whatwg] Features for responsive Web design

On Thu, May 17, 2012 at 3:26 PM, Maciej Stachowiak wrote: > > On May 16, 2012, at 9:39 PM, Silvia Pfeiffer > wrote: > >> On Wed, May 16, 2012 at 10:55 PM, Matthew Wilcox >> wrote: >>> Chalk me up as another making that mistake. Properties on elements >&

Re: [whatwg] Features for responsive Web design

On Wed, May 16, 2012 at 10:55 PM, Matthew Wilcox wrote: > Chalk me up as another making that mistake. Properties on elements > usually describe a property of the element. Not a property of > something else (like the viewport). If it does indeed rely on a rendering issue (like the size of the view

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

On Wed, May 16, 2012 at 9:20 AM, Odin Hørthe Omdal wrote: > Silvia Pfeiffer skreiv Wed, 16 May 2012 00:57:48 > +0200 > >>> Media queries come from the client side. They allow the author of a web >>> page to tell exactly how she want to lay out her design based on the

  1   2   3   4   5   6   >