Re: [whatwg] Installable web apps

ately fetched. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Installable web apps

otentially more vulnerable. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Installable web apps

top of what we have already that gives a few extra features. At least that's what I make out of the rough summary. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] element, streams and peer-to-peer connections

be leaving peer-to-messaging out... Streaming video via WebSocket is something we definitely want to enable in due course, irrespective of whether peer-to-peer messaging comes to fruition. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Speech input element

types? -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Speech input element

input) and build up from there. But maybe I'm wrong and speech input is a case that needs to be considered separately. It would still not be like synchronous XMLHttpRequest though. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Speech input element

past discussions, scrolling through a document we're discussing, etc. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Speech input element

On Tue, 18 May 2010 10:52:53 +0200, Bjorn Bringert wrote: On Tue, May 18, 2010 at 8:02 AM, Anne van Kesteren wrote: I wonder how it relates to the proposal already in the draft. In theory that supports microphone input too. It would be possible to implement speech recognition on top of

Re: [whatwg] Java language bindings for HTML5

On Wed, 19 May 2010 08:40:16 +0200, Shiki Okasaka wrote: On Tue, May 18, 2010 at 3:27 PM, Anne van Kesteren wrote: Can't they all just use org.w3c.dom? We cannot make the interface names overlap anyway. I think one module name for all of the Web platform would work fine for progra

Re: [whatwg] Speech input element

the proposal already in the draft. In theory that supports microphone input too. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Java language bindings for HTML5

. Hopefully more people will revisit this issue sometime soon. Can't they all just use org.w3c.dom? We cannot make the interface names overlap anyway. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Directory upload via

On Sat, 24 Apr 2010 17:58:10 +0200, Ojan Vafai wrote: On Fri, Apr 23, 2010 at 8:41 PM, Anne van Kesteren wrote: On Fri, 23 Apr 2010 07:11:08 +0900, Ojan Vafai wrote: But there is already a default UI that lets you select a folder, a file or both (drag-drop). I don't see why this f

Re: [whatwg] Need document.available_fonts() call

. However, for portability it would probably be better if these were limited to fonts already on the Web. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Request for new DOM property textarea.selectionText

large text content is slow in Firefox due to https://bugzilla.mozilla.org/show_bug.cgi?id=190147 But I know if we paste manually it works fast enough. So may be having .selectionText helps -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Type Date

r as I can tell. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] onshow event

/wiki/Companion_specifications Issues with the current specification I mostly track through email. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Do we really need to introduce a element for giving access to webcams and mikes?

et.) -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] The real issue with HTML5's sectioning model

of mixing h1-h6 with section/h. HTML5 did. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] The real issue with HTML5's sectioning model

On Sat, 01 May 2010 03:57:42 +0900, Eduard Pascual wrote: XHTML2's approach was clean and simple: , , and @role do everything. Period. Bullshit: http://www.w3.org/TR/2006/WD-xhtml2-20060726/mod-structural.html#sec_8.5. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Directory upload via

pose extra UI on top of drag-drop to let you do so. Again, no more so than they already have to expose extra UI to deal with multiple inputs. How does the drag & drop API support this use case? -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Directory upload via

rrent files are added it starts the download process for them. I could imagine something similar being useful for an image sharing site such as Flickr. (This use case does not really fit on top of however.) -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Canvas 2D Context Proposal: resetOriginClean

. the requests makes). Has Opera implemented cross domain origin-clean images? Not yet. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Canvas 2D Context Proposal: resetOriginClean

uld be required? It is designed to make this "just work" so if anything is wrong I'd like to know. Specifically the "resource sharing check" is what HTML would use here. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Introduction of media accessibility features

On Fri, 16 Apr 2010 16:54:12 +0900, Silvia Pfeiffer wrote: On Fri, Apr 16, 2010 at 5:03 PM, Anne van Kesteren wrote: It would simply always be UTF-8, much like text/cache-manifest and text/event-stream. There are plenty of SRT files out there that are not UTF-8. We do not control the

Re: [whatwg] Introduction of media accessibility features

On Fri, 16 Apr 2010 15:49:38 +0900, Silvia Pfeiffer wrote: On Fri, Apr 16, 2010 at 3:32 PM, Anne van Kesteren wrote: A spec would also need to be written if we go for this new TTML-minus-certain-features-and-using-CSS-rather-than-XSL-FO format. That would probably be worse since we would

Re: [whatwg] Introduction of media accessibility features

we really want to do "SRT + HTML + CSS", then we should start completely from a blank page. It makes things easier for people familiar with authoring SRT. It also makes it easier to change existing SRT files into rich SRT files. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Introduction of media accessibility features

does. CSS is by design, optional. I would hope a captioning format is not, since captions are somewhat essential content information. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Questions about the keygen element specification

ortant if I remember correctly. (More details can be found in the public-h...@w3.org archives.) -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Forms feedback

n: details:not(open) > :not(summary) { display: none; } (Plus general default styling of and , of course.) That does not work well for text nodes. (Also, you meant [open], i.e. including braces.) -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Will you consider about RFC 4329?

and HTML documents (and increasingly other applications in general) is Unicode based. In theory this is correct. In practice nobody follows this outdated default encoding requirement. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] [html5] r4949 - [giow] (0) The CSS rules need to do attribute value matching consistently across [...]

e an ASCII case-insensitive flag for attribute value selectors to deal with this issue. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Why are form fields without a name barred from constraint validation?

. So, those controls do not need to be validated, I think. Thanks! FWIW, there have been some requests on dropping this since nowadays form controls are not always associated with a form, but the validity concept can still be useful in such scenarios. -- Anne van Kesteren http

Re: [whatwg] Web Workers feedback

ally a fallback position, so it doesn't matter if we send null or throw an exception. Isn't the fallback there to draw the on a and then extract an ImageData object and pass that through to the worker? -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] WebSocket bufferedAmount includes overhead or not

e protocol overhead isn't reported. Why? Progress events are completely different from this. This is about not saturating the network with too much data; it makes sense if the actual amount of data that is going to hit the network is known. (Yes, I changed my mind.) -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] WebSocket bufferedAmount includes overhead or not

that send(DOMString) can eventually send very different things over the wire depending on how the server reacts to the initial handshake request? How do the various options we have evaluate against the potential scenarios coming out of that? -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] WebSocket bufferedAmount includes overhead or not.

. to not impose details of the protocol on the API. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] expanding to LF

://mxr.mozilla.org/mozilla-central/source/layout/style/test/test_parse_rule.html This was apparently originally requested by Anne: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2007-June/011689.html I'm fine with changing it back, assumin[g] Anne's ok with it too. Anne? Sure. -- Anne va

Re: [whatwg] Lifting cross-origin XMLHttpRequest restrictions?

uld a header be required on compliant browsers to send a header along with their request indicating the originating server's domain? No, existing servers would still be vulnerable. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Lifting cross-origin XMLHttpRequest restrictions?

ready free to obtain and mix in content from other sites, so why can't client-side HTML JavaScript be similarly empowered? Because you would also have access to e.g. IP-authenticated servers. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] meter and progress elements and constraint validation

from constraint validation ? Seems to be a bug, unless the elements were intended to be in the category "listed". -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] [html5] Attaching option elements to select elements in different documents

irefox disagrees (it changes the [[Prototype]] to be that it would have been if the node had been created anew in the destination document). -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] [html5] Attaching option elements to select elements in different documents

pera both just ignore the standard and get this wrong. Chrome just seems to get confused. This changed a while ago due to compatibility problems. Consensus at the time was to change DOM Core. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Adding FormData support to

mElement.getFormData() It might be ok, but it is a bit inconsistent. Why not: formData = new FormData(); formData = new FormData(myFormElement); ah... +1 the ctor Indeed, constructor syntax makes it very clear that you are getting a new object. I like. I could add this to XMLHttpRequest Le

Re: [whatwg] Offscreen canvas (or canvas for web workers).

canvas to an onscreen one. Perhaps via a canvas ID. postMessage() supports ImageData so you could use that. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] HTML Cookie API

ter API for cookies then? -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Customize HTML5 forms placeholder style

? You could e.g. style the border of the input element to show it has not been used yet. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Adding FormData support to

On Thu, 18 Feb 2010 23:06:12 +0100, Jonas Sicking wrote: On Wed, Feb 17, 2010 at 11:30 PM, Anne van Kesteren wrote: On Thu, 18 Feb 2010 00:15:25 +0100, Jonas Sicking wrote: So I suggest we add a method like interface HTMLFormElement : HTMLElement { ... FormData getFormData

Re: [whatwg] Customize HTML5 forms placeholder style

webkit.org/show_bug.cgi?id=21299 -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Customize HTML5 forms placeholder style

their default style rule has higher specificity than style= or some such to work around the issue WebKit ran into. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Adding FormData support to

van Kesteren http://annevankesteren.nl/

Re: [whatwg] canvas, img, file api and blobs

this experimental stage it is not really clear whether your use case hits the 80/20 or is actually rather uncommon and can be dealt with using a jQuery wrapper or some such. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] canvas, img, file api and blobs

rted working on XMLHttpRequest Level 2. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] canvas, img, file api and blobs

op of images in the canvas, etc. Seems easier to take care of this by allowing extraction of metadata (some W3C WG is working on this I think) and maybe a way to put it back in... -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] validationMessage

nterface for the above that should be allowed too.) -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] script postonload

ich browsers do not create a element? I thought we fixed our bug. Also, introducing new features mainly to work around existing bugs is generally not a good idea. We'd only increase the potential for interoperability issues. -- Anne van Kesteren http://annevankesteren.nl/

[whatwg] Lists and legal documents

-stadskanaal.nl/ I think it would be good if we either solved this problem natively or at least gave some advice for people finding themselves in a similar situation. (That editor/site also has ordered definition lists, with similar markup.) -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Qs about element

, and that a details element should expand/ contract for user agents that have JS disabled. Is that correct? Yeah, once UAs have native support. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] api for fullscreen()

On Sun, 31 Jan 2010 03:43:49 +0100, Simon Fraser wrote: On Jan 30, 2010, at 1:24 PM, Anne van Kesteren wrote: To stop polluting the Window object, might it make sense to put the new members (other than event handler attributes) on window.screen? This would require that the current window

Re: [whatwg] api for fullscreen()

eption if already fullscreen? To stop polluting the Window object, might it make sense to put the new members (other than event handler attributes) on window.screen? -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Fixing the submit event by exposing submitter and data set

simple as .formData which seems better than tying it to the submit event. (This has been suggested various times before as well by the way. We are just waiting for some more stabilization of various other and XMLHttpRequest features first.) -- Anne van Kesteren http

Re: [whatwg] HTMLCanvasElement.toFile()

On Fri, 08 Jan 2010 10:44:05 +0100, Henri Sivonen wrote: Image types can be reliably distinguished from the magic number, so having the MIME type isn't critical in that sense. Since SVG this is no longer really true. Though I doubt anyone will support -> SVG... -- Anne van

Re: [whatwg] using postMessage() to send to a newly-created window

* I guess, but can't you just check before invoking postMessage() anyway?) -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] window.print() when printing is not supported

ing application on a phone is getting pretty common.) -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] window.print() when printing is not supported

main menu, or the toolbar that contains the print button. Even if we encourage authors to not use the print() method they might still do it and we'd still have to answer Olli's question one way or another... -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] window.print() when printing is not supported

ight* make sense to throw some error if printing isn't supported. Or should browsers which don't support window.print() just not have print() method in the window object? (problem is that I'd guess everyone just expects .print() to be there) Throwing an error does not seem very c

Re: [whatwg] Canvas tag - single or multiple contexts?

quot; context and others don't? That's rhetorical, right? :-) -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Canvas tag - single or multiple contexts?

pported 2d, opera-2dgame, and opera-3d for a while. However it seems that for certain contexts, in particular webgl, using it together with other contexts is not possible (for now anyway). -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Appcache feedback

ons are doing now and we do this as well. What Michael suggested makes sense and I suppose as the effects are indistinguishable in the end that (delaying either the events or the download process) should be fine. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Cross Origin Workers

or XMLHttpRequest (not everywhere yet) for cross-origin communication if that is your main use case. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Cross Origin Workers

/gears_faq.html#crossOriginWorker FYI: They're not HTML5 Workers, just Web Workers. And no, they do not have cross-origin functionality currently. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Uploading directories of files

rtainly more important IMO.) Note that extensions to File should be discussed on public-weba...@w3.org. At least, that's where they have been so far. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Uploading directories of files

On Fri, 11 Dec 2009 09:33:06 +0100, Markus Ernst wrote: Anne van Kesteren schrieb: On Fri, 11 Dec 2009 09:13:52 +0100, Markus Ernst wrote: I have no idea how to handle such inconsistent behaviour on the server side (except adding extra code to flatten all uploaded directory structures

Re: [whatwg] Uploading directories of files

upload tasks should be handled with specialized applications, such as RadUpload[1]. [1] http://www.radinks.com I don't think we want to rely on the availability of Java on the end user's platform (or the availability of any other plug-in for that matter). -- Anne van Kes

Re: [whatwg] "offscreen canvas" /Access to canvas functionality from a worker

in in a worker? you don;t have image elements, you can't xhr unsafely to other origins, but maybe i'm missing something? can only be tainted by unsafe or elements. Neither is applicable, so no. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Inconsistent behavior for empty-string URLs

esn't make a request in all of these cases, so I'm guessing that Web Workers is an exception? It only doubles the load if you have crappy markup (or server setup, depending on your goals). Not sure why we are not loading the resource. That'd be a bug per the current specific

Re: [whatwg] Inconsistent behavior for empty-string URLs

fine. What is wrong with having this work as is? -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Thread to run Web Socket feedback from the protocol ?

rence from XMLHttpRequest events. XMLHttpRequest network events are "asynchronous" too. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Canvas pixel manipulation and performance

details so that we can eventually convert into some kind of octet array if we get native support for that. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] insertAdjacentHTML

On Tue, 24 Nov 2009 13:24:58 -0200, Daniel Glazman wrote: Anne van Kesteren wrote: The problem is that it is a legacy feature, much like innerHTML. That's not a problem. Make insertHTML with the new values and make insertAdjacentHTML with the old values just an alias to the new ones. O

Re: [whatwg] insertAdjacentHTML

On Tue, 24 Nov 2009 13:01:26 -0200, Daniel Glazman wrote: I think that insertAdjacentHTML as defined in current section 3.5.7 [1] could be much cleaner and clearer if [...] The problem is that it is a legacy feature, much like innerHTML. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] sessionStorage and the Storage event

sessionStorage at all. I simply don't a case when two or more documents would share a single sessionStorage object. sessionStorage is shared with e.g. same-origin child browsing contexts so it is not limited to a single Document. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Example wrong in web workers

!= 'undefined') , as the event property is presumably 'null' by the time of the test. ("onmessage" in this) might be somewhat safer fwiw. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Workers and addEventListener

more than just registering an event listener for the given event. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Restarting the media element resource fetch algorithm after "load" event

, correct me if I'm wrong. The loadend event is dispatched for XMLHttpRequest and that might be in Gecko I suppose. I'm not particularly attached to it though. I just added it for consistency with the media elements and the progress events specification. -- Anne van Kes

Re: [whatwg] localStorage feedback

at the document and bubble to the window, scroll events on elements with 'overflow' not 'visible' fire at that element and don't bubble. I forwarded this to www-style by the way. It's on the pile for cssom-view now. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] disabled and readonly attributes

On Tue, 13 Oct 2009 18:07:16 +0200, Aryeh Gregor wrote: It seems like I'm not the only one confused by the difference between disabled and readonly, then. Disabled controls are not submitted. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] document.head

text node there firstChild would get it as expected. I think that is already covered. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Cache Manifest: why have NETWORK?

On Thu, 24 Sep 2009 10:43:57 +0200, Anne van Kesteren wrote: On Wed, 23 Sep 2009 20:09:03 +0200, Michael Nordman wrote: For cases where you don't want to, or can't, 'fallback' on a cached resource. ex 1. http://server/get/realtime/results/from/the/outside/worldC

Re: [whatwg] Closing tags for empty content model

not). This does suck a little when introducing new void elements, but keeping the syntax consistent is worth it in my opinion. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Workers and addEventListener

not modify the semantics of addEventListener. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Please always use utf-8 for Web Workers

is not exactly the "default", since it cannot be changed. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Please always use utf-8 for Web Workers

On Fri, 25 Sep 2009 19:16:47 +0200, Drew Wilson wrote: Certainly. If I explicitly override the charset, then that seems like reasonable behavior. It does not need to be overridden per se. If the document character encoding is different from UTF-8 then a script loaded through

Re: [whatwg] Please always use utf-8 for Web Workers

On Fri, 25 Sep 2009 18:39:48 +0200, Drew Wilson wrote: Are you saying that if I load a script via a

Re: [whatwg] Cache Manifest: why have NETWORK?

ggested giving non-wildcard NETWORK resources priority. You suggest this might make sense, but I've yet to see a good argument as to why the current approach makes sense. It certainly does not help with the example above. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Cache Manifest: why have NETWORK?

so in cases like this FALLBACK: / /fallback NETWORK /realtime-api /update ... you do not get /fallback all the time. -- Anne van Kesteren http://annevankesteren.nl/

[whatwg] Cache Manifest: why have NETWORK?

If you use a fallback namespace it will always try to do a network fetch before using the fallback entry so why is there a need for a NETWORK entry in the cache manifest? -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] registerProtocolHandler - allow site to specify more info and do custom handling

On Tue, 22 Sep 2009 17:32:59 +0200, Michael A. Puls II wrote: On Tue, 22 Sep 2009 09:10:02 -0400, Anne van Kesteren wrote: The IRI specification dictates UTF-8 already. But sites might not follow it. Then they will need to be updated if they want to work with registerProtocolHandler

Re: [whatwg] registerProtocolHandler - allow site to specify more info and do custom handling

erProtocolHandler work. And if user agents want to support sites that do not support registerProtocolHandler that is their business I think and not an necessarily an issue for the feature. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] HTML 5 drag and drop feedback

ually made based on merit, not popularity. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] size content attribute on

an idea of likely values but don't want to actually prohibit values outside the range, but I can't think of a very good example offhand. step="any" -- Anne van Kesteren http://annevankesteren.nl/

<    5   6   7   8   9   10   11   12   13   14   >