Re: [whatwg] Drag-and-drop folders/files support with directory structure using DirectoryEntry

2012-04-05 Thread Kinuko Yasuda
On Fri, Apr 6, 2012 at 12:52 PM, Glenn Maynard wrote: > On Wed, Apr 4, 2012 at 11:36 PM, Kinuko Yasuda wrote: > >> A follow up about this proposal: >> >> Based on the feedbacks we got on this list we've implemented the >> following API to do experiments in Chrome: >> DataTransferItem.getAsEntry(

Re: [whatwg] Drag-and-drop folders/files support with directory structure using DirectoryEntry

2012-04-05 Thread Glenn Maynard
On Wed, Apr 4, 2012 at 11:36 PM, Kinuko Yasuda wrote: > A follow up about this proposal: > > Based on the feedbacks we got on this list we've implemented the following > API to do experiments in Chrome: > DataTransferItem.getAsEntry(in EntryCallback callback) > Does this actually need to be asy

Re: [whatwg] Drag-and-drop folders/files support with directory structure using DirectoryEntry

2012-04-05 Thread Kinuko Yasuda
On Fri, Apr 6, 2012 at 12:32 AM, Eric U wrote: > On Wed, Apr 4, 2012 at 9:36 PM, Kinuko Yasuda wrote: > > A follow up about this proposal: > > > > Based on the feedbacks we got on this list we've implemented the > following > > API to do experiments in Chrome: > > DataTransferItem.getAsEntry(in

Re: [whatwg] Proposal: location.parentOrigin

2012-04-05 Thread Adam Barth
My sense is that's an acceptable risk given that this information commonly leaks in document.referrer anyway. Using sandbox sounds like a worthwhile backstop though. Adam

Re: [whatwg] Proposal: location.parentOrigin

2012-04-05 Thread Michal Zalewski
> Tab suggests (on IRC) that this should just be tied to sandbox="", which > seems reasonable at first blush. Sandbox is opt-in (which means we'd start revealing origins in existing settings without a warning); and has other serious constraints which preclude it from some existing use cases (e.g.,

Re: [whatwg] Client side value for language preference

2012-04-05 Thread Bronislav Klučka
On 30.3.2012 17:41, Tim Streater wrote: On 30 Mar 2012 at 16:05, Jukka K. Korpela wrote: 2012-03-30 17:22, Henri Sivonen wrote: On Fri, Mar 30, 2012 at 5:08 PM, Matthew Nuzum wrote: For example, maybe a site can't afford translation but a small library could be included that formats dat

Re: [whatwg] Proposal: location.parentOrigin

2012-04-05 Thread Ian Hickson
On Wed, 4 Apr 2012, Michal Zalewski wrote: > > In fact, in the vein of opt-in disclosure perhaps something like > discloselocation={none|origin|full} would be more convenient - in which > case, you get something like > window.parentLocations[n].{origin|href|hash|...} > > I constantly fear that

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

2012-04-05 Thread Ian Hickson
On Thu, 5 Apr 2012, Philip Jägenstedt wrote: > On Wed, 04 Apr 2012 20:56:03 +0200, Ian Hickson 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 t

Re: [whatwg] Drag-and-drop folders/files support with directory structure using DirectoryEntry

2012-04-05 Thread Eric U
On Wed, Apr 4, 2012 at 9:36 PM, Kinuko Yasuda wrote: > A follow up about this proposal: > > Based on the feedbacks we got on this list we've implemented the following > API to do experiments in Chrome: >  DataTransferItem.getAsEntry(in EntryCallback callback) > > which takes a callback that return

Re: [whatwg] Fullscreen changes to support

2012-04-05 Thread Anne van Kesteren
On Wed, 04 Apr 2012 01:14:43 +0200, Ian Hickson wrote: If this works, then I'll use this for . Thanks for figuring this out. I was kind of hoping this would end up in a CSS draft, but Fullscreen works for now I guess. http://dvcs.w3.org/hg/fullscreen/raw-file/tip/Overview.html Looking for

Re: [whatwg] Fullscreen changes to support

2012-04-05 Thread Scott González
On Thu, Apr 5, 2012 at 3:58 AM, Anne van Kesteren wrote: > I can see how it makes sense in the abstract. Browsers moved away from > application-global modal dialogs to tab modal dialogs. I could see Twitter > still wanting to you let you switch to @Connect or #Discover or search, > while a modal

Re: [whatwg] Fullscreen changes to support

2012-04-05 Thread Sean Hogan
On 5/04/12 2:53 PM, Ian Hickson wrote: On Thu, 5 Apr 2012, Sean Hogan wrote: So the ::backdrop could be styled to not cover the whole page? Could it default to a "top" layer, but optionally be given a z-index? The ::backdrop specifically would just be immediately below its element in the "top l

Re: [whatwg] seamless iframes

2012-04-05 Thread Markus Ernst
Am 05.04.2012 03:59 schrieb Ojan Vafai: On Wed, Apr 4, 2012 at 6:52 PM, Ojan Vafai wrote: 1. We should add iframe[seamless] { display:block; }. http://www.whatwg.org/specs/web-apps/current-work/#embedded-content-2 already expects iframe:not([seamless]) { border: 2px inset; }. In 90% percent o

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

2012-04-05 Thread Philip Jägenstedt
On Wed, 04 Apr 2012 20:56:03 +0200, Ian Hickson 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. > > I

Re: [whatwg] Fullscreen changes to support

2012-04-05 Thread Anne van Kesteren
On Thu, 05 Apr 2012 06:53:08 +0200, Ian Hickson wrote: Those sound like non-modal dialogs. Do you have any examples of modal dialogs on the Web that have these behaviours? As above, screenshots and URLs to such examples would be really helpful. I can see how it makes sense in the abstract. Bro