Re: Intent to implement: HTML5 element

2016-12-23 Thread Tantek Çelik
On Fri, Dec 23, 2016 at 4:02 PM, Martin Thomson wrote: > On Fri, Dec 23, 2016 at 6:20 PM, Boris Zbarsky wrote: >>> I mean, the attribute is probably a lost cause >> >> Why? Is there significant usage, or at least wide implementation, of that >> part of the

Re: Intent to implement: HTML5 element

2016-12-23 Thread Xidorn Quan
On Fri, Dec 23, 2016, at 02:33 PM, Tim Nguyen wrote: > Non-modal dialogs should just work fine in a chrome window (the dialog > would just be like a centered absolute positioned div). As for modal > dialogs (eg. dialogs that makes everything else inert), it would depend > on > whether the current

Re: Intent to implement: HTML5 element

2016-12-23 Thread Martin Thomson
On Fri, Dec 23, 2016 at 6:20 PM, Boris Zbarsky wrote: >> I mean, the attribute is probably a lost cause > > Why? Is there significant usage, or at least wide implementation, of that > part of the API already? The original intent said that only Chrome is > shipping this. Fair

Re: Intent to implement: HTML5 element

2016-12-22 Thread Boris Zbarsky
On 12/22/16 10:03 PM, Martin Thomson wrote: On Fri, Dec 23, 2016 at 7:14 AM, Boris Zbarsky wrote: Note that I expect that this spec was written before Promise was a thing. The setup where we return a value in an attribute of the element (!) is pretty bizarre... Is this

Re: Intent to implement: HTML5 element

2016-12-22 Thread Martin Thomson
On Fri, Dec 23, 2016 at 7:14 AM, Boris Zbarsky wrote: > Note that I expect that this spec was written before Promise was a thing. > The setup where we return a value in an attribute of the element (!) is > pretty bizarre... Is this irredeemable? I mean, the attribute is

Re: Intent to implement: HTML5 element

2016-12-22 Thread Tim Nguyen
Non-modal dialogs should just work fine in a chrome window (the dialog would just be like a centered absolute positioned div). As for modal dialogs (eg. dialogs that makes everything else inert), it would depend on whether the current top-layer implementation works within a chrome window and I

Re: Intent to implement: HTML5 element

2016-12-22 Thread Justin Dolske
What's the expected experience if chrome code uses this feature? (In a chrome window, interaction with a content window isn't the thing I'm wondering about.) Justin On Tue, Dec 20, 2016 at 3:56 PM, Tim Nguyen wrote: > *Summary*: > The *HTML element* represents a dialog box

Re: Intent to implement: HTML5 element

2016-12-22 Thread Boris Zbarsky
On 12/21/16 4:13 PM, Xidorn Quan wrote: This is a question for the spec. I guess it theoretically can return a Promise, though I suspect that there might be some weird corner cases which is hard to handle. Note that I expect that this spec was written before Promise was a thing. The setup

Re: Intent to implement: HTML5 element

2016-12-21 Thread Xidorn Quan
On Thu, Dec 22, 2016, at 05:41 AM, Joe Hildebrand wrote: > > On Dec 20, 2016, at 6:25 PM, Xidorn Quan wrote: > > > >> So dialog.showModal() does not need to block script like other > >> modal APIs? > > > > > > Definitely not. I think this is designed to replace those blocking

Re: Intent to implement: HTML5 element

2016-12-21 Thread Joe Hildebrand
> On Dec 20, 2016, at 6:25 PM, Xidorn Quan wrote: > >> So dialog.showModal() does not need to block script like other >> modal APIs? > > > Definitely not. I think this is designed to replace those blocking API. Why doesn't showModal() return a Promise? -- Joe Hildebrand

Re: Intent to implement: HTML5 element

2016-12-20 Thread Xidorn Quan
On Wed, Dec 21, 2016, at 12:23 PM, Ben Kelly wrote: > On Tuesday, December 20, 2016, Xidorn Quan wrote: > > On Wed, Dec 21, 2016, at 11:12 AM, Mats Palmgren wrote: > >> Hi Tim, can you describe how the modality of dialog.showModal() > >> works? > >> Does a web page have the

Re: Intent to implement: HTML5 element

2016-12-20 Thread Xidorn Quan
On Wed, Dec 21, 2016, at 11:21 AM, Tantek Çelik wrote: > I'm also curious how interactions between dialog.showModal() and then > controls inside of that going Fullscreen work (and then perhaps a > dialog inside that fullscreen view, etc.) That's a... good question. Per spec, it should just

Re: Intent to implement: HTML5 element

2016-12-20 Thread Astley Chen
A simple example if you are interested in how it works on Chrome. http://codepen.io/astleychen/pen/Obqzrr —-- Best Regards, Astley Chen | Mozilla Taiwan On 21 Dec 2016, at 8:21 AM, Xidorn Quan wrote: On Wed, Dec 21, 2016, at 11:12

Re: Intent to implement: HTML5 element

2016-12-20 Thread Tantek Çelik
I'm also curious how interactions between dialog.showModal() and then controls inside of that going Fullscreen work (and then perhaps a dialog inside that fullscreen view, etc.) Does "escape" key escape out of one layer of dialog/fullscreen? multiple? all? Tantek On Tue, Dec 20, 2016 at 4:12 PM,

Re: Intent to implement: HTML5 element

2016-12-20 Thread Xidorn Quan
On Wed, Dec 21, 2016, at 11:12 AM, Mats Palmgren wrote: > Hi Tim, can you describe how the modality of dialog.showModal() works? > Does a web page have the power to block the user from interacting > with the entire browser (all windows)? Or is it just one window? > or just one tab? or something

Intent to implement: HTML5 element

2016-12-20 Thread Tim Nguyen
*Summary*: The *HTML element* represents a dialog box or other interactive component, such as an inspector or window. It will initially be implemented behind a pref. *Bug*: https://bugzilla.mozilla.org/show_bug.cgi?id=840640 *Link to standard*: