Re: Art steps down - thank you for everything

many of you know, without him it would have been a much >>> poorer group, and run much less smoothly. He did a great deal of work >>> for the group throughout his time as co-chair, efficiently, reliably, >>> and quietly. >>> >>> Now we are three co-chairs, we will work between us to fill Art's shoes. >>> It won't be easy. >>> >>> Thanks Art for everything you've done for the group for so long. >>> >>> Good luck, and I hope to see you around. >>> >>> Chaals >>> >>> >> > -- Jungkee Song

RE: Service Workers

ilestone%3A%22Version+1%22> > [2] <https://github.com/slightlyoff/ServiceWorker/commits/master> > [3] <https://github.com/slightlyoff/ServiceWorker/issues/> > [4] <https://lists.w3.org/Archives/Public/public-webapps/> > > > On 9/18/15 2:22 AM, Jungkee Song wr

Re: Service Workers 1 and Nightly

ks, Jungkee > > -Thanks, AB > > [1] <http://www.w3.org/2015/Process-20150901/#maturity-levels> > [2] <http://www.w3.org/2015/Process-20150901/#wide-review> > > -- Jungkee Song

Service Workers 1 and Nightly

[4] https://slightlyoff.github.io/ServiceWorker/spec/service_worker/ -- Jungkee Song Samsung Electronics

RE: W3C's version of XMLHttpRequest should be abandoned

tance, not the other editors. Domenic's suggestion sound reasonable to me if we are not coming up with a better plan. Best regards, Jungkee > -Original Message- > From: Arthur Barstow [mailto:art.bars...@gmail.com] > Sent: Friday, August 07, 2015 8:37 PM > To: Hallvord Reia

RE: PSA: publishing new WD of Service Workers on June 25

Thanks for comments. I'll address them in the ED. I didn't get through them all yet, but > * in parallel isn't defined, but it sounds like you mean "in parallel to the > main sequence" not "in parallel to themselves", I'd strongly encourage a > definition. "in parallel" is defined here: https

Re: [push-api] Moving "PushManager push" onto ServiceWorkerRegistration

On Jul 12, 2014 2:11 AM, "Jake Archibald" wrote: > > On 11 July 2014 17:59, Jonas Sicking wrote: >> >> On Fri, Jul 11, 2014 at 8:17 AM, Jake Archibald wrote: >> > navigator.serviceWorker.ready.then(function(reg) { >> > reg.push.register(...) >> > }); >> >> I agree this looks good. Though maybe

Re: Why do keys() and values() on CacheList in ServiceWorkers not return promises

On May 9, 2014 1:16 PM, "Boris Zbarsky" wrote: > > In particular, given that get() wants to return a Promise, why do we want values() to return a list of Cache objects synchronously? > > Similar for keys(): if has() needs to be async, then how can has() be sync. > Exactly. both values() and keys(

Re: It doesn't make sense to use [MapClass] for the CacheList interface

On May 9, 2014 12:18 PM, "Boris Zbarsky" wrote: > > I'm looking at https://slightlyoff.github.io/ServiceWorker/spec/service_worker/index.html#cache-listhere. > > The point of [MapClass] (assuming [MapClass] stays in the WebIDL spec at all) is to declare interfaces that quack enough like Map that i

Re: Service worker spec should probably not use IDL arrays

On May 9, 2014 12:19 PM, "Boris Zbarsky" wrote: > > IDL arrays are not really supported by any UA, and it's not clear to me that any plan to do it. The trend has been toward using ES arrays instead (which typically means IDL sequences). > > At first glance, every use of IDL arrays in service work

Re: XMLHttpRequest Level 1- specification history

On Mon, Mar 31, 2014 at 2:44 AM, Ian Hickson wrote: > On Sun, 30 Mar 2014, Jungkee Song wrote: > > > > I presume the author originally put the part rather informatively. I > > made it a single sentence as clarified here: > > > https://dvcs.w3.org/hg/xhr/raw-fi

Re: XMLHttpRequest Level 1- specification history

tation.) > > If this was the meaning, you would need a comma after "Long after". > > -- > Ian Hickson U+1047E )\._.,--,'``.fL > http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. > Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.' > > -- Jungkee Song

Re: WebKit interest in ServiceWorkers (was Re: [manifest] Utility of bookmarking to home screen, was V1 ready for wider review)

On Mon, Feb 17, 2014 at 9:38 PM, Arthur Barstow wrote: > On 2/17/14 6:47 AM, ext Jungkee Song wrote: > >> On Feb 17, 2014 8:02 PM, "Maciej Stachowiak" > m...@apple.com>> wrote: >> >> I personally would like to see it become an official draft of the Worki

Re: WebKit interest in ServiceWorkers (was Re: [manifest] Utility of bookmarking to home screen, was V1 ready for wider review)

e actively collaborating there using the GH issues. I think we should keep using it unless otherwise determined by the contributors. I'll fix the above text to point to the GH issues. > -Thanks, AB > > > -- Jungkee Song

Re: WebKit interest in ServiceWorkers (was Re: [manifest] Utility of bookmarking to home screen, was V1 ready for wider review)

On Feb 17, 2014 8:02 PM, "Maciej Stachowiak" wrote: > On Feb 16, 2014, at 2:16 AM, Marcos Caceres wrote: >> >> On Sunday, February 16, 2014, Alex Russell wrote: >>> >>> On Sat, Feb 15, 2014 at 5:56 AM, Marcos Caceres wrote: tl;dr: I strongly agree (and data below shows) that installab

Re: [progress-events] Progress Events is a W3C Recommendation

Thanks Art. The work is attributed to Anne, Chaals and Ms2ger. Thanks! On Feb 12, 2014 9:28 PM, "Arthur Barstow" wrote: > Congratulations to Anne, Jungkee and Chaals on the publication of a > Progress Events Recommendation REC-progress-events-20140211/ >. > > (I upda

Re: "Officially" deprecating main-thread synchronous XHR?

t; http://xhr.spec.whatwg.org/#sync-warning > > > -- > http://annevankesteren.nl/ > > -- Jungkee Song

Re: [XHR] XHR 1 / XHR 2

On Feb 3, 2014 11:41 PM, "Dominique Hazael-Massieux" wrote: > > Hi, > > The TR draft says that the URL of the editors draft is: > https://dvcs.w3.org/hg/xhr/xhr-1/raw-file/tip/Overview.html > I believe it is meant to be: > https://dvcs.w3.org/hg/xhr/raw-file/tip/xhr-1/Overview.html > That's right

[xhr-1] XMLHttpRequest Level 1 WD update

s" wrote: > >> Hi Art, >> I'm wondering if we can change the group's work mode to not requiring >> CFCs for ordinary working drafts? Unless I'm not getting something, they >> seem to add an unnecessary delay to getting stuff published. >> >>

Re: "W3C" XHR, was Re: [admin] Draft of updated charter available for review

On Fri, Jan 24, 2014 at 8:22 PM, Arthur Barstow wrote: > On 1/23/14 8:48 PM, ext Jungkee Song wrote: > >> I understand your concern. Indeed, we editors should have made it clearer >> providing updates on the status and more importantly a new TR. >> >> The goal of th

Re: "W3C" XHR, was Re: [admin] Draft of updated charter available for review

On Jan 24, 2014 7:48 AM, "Marcos Caceres" wrote: > > > > On Thursday, January 23, 2014 at 10:36 PM, Marcos Caceres wrote: > > > On Thursday, January 23, 2014 at 9:29 PM, Arthur Barstow wrote: > > > I don't recall any discussions about stopping the current work, although > > > I think it would be u

RE: CfC: publish Proposed Recommendation of Progress Events; deadline November 25

Hi, I've prepared the PR-ready version of the Progress Events spec: https://dvcs.w3.org/hg/progress/raw-file/tip/TR/Overview.html Please use this version to review and give further comments during the CfC period, if any. Jungkee > -Original Message- > From: J

RE: CfC: publish Proposed Recommendation of Progress Events; deadline November 25

cs.w3.org/hg/progress/rev/964030fa5727 [2] https://dvcs.w3.org/hg/progress/raw-file/tip/Overview.html -- Jungkee Song Samsung Electronics

[xhr-1] Keep the responseType "json"

> -Original Message- > From: Jungkee Song [mailto:jungkee.s...@samsung.com] > Sent: Wednesday, October 30, 2013 9:48 PM > > As planned, we editors prepared XMLHttpRequest Level 1 [1] as a > Recommendation track version. Initially, we'd planned to put together a >

[xhr][xhr-1] status and plans

t-test/ [5] http://xhr.spec.whatwg.org [6] http://fetch.spec.whatwg.org -- Jungkee Song

Re: [XHR] request error distinction: abort and error

x27;t really understand that they interrupted something, or > what they interrupted, especially since I believe browsers do not tend to > have "stop" UI for XHR traffic). > > By that logic I think having it classified as an 'error' event is better, > but IMO this is a minor detail and not really worth our time.. > -Hallvord > -- Jungkee Song

[XHR] request error distinction: abort and error

-index=&resultsperpage=20&sortby=date [2] https://dvcs.w3.org/hg/xhr/raw-file/tip/Overview.html#infrastructure-for-the-send()-method [3] http://xhr.spec.whatwg.org/#infrastructure-for-the-send()-method [4] https://developer.mozilla.org/en-US/docs/Web/API/window.stop [5] https://github.com/w3c/web-platform-tests/issues/241#issuecomment-22750928 -- Jungkee Song

RE: [PE] Interop Status Update

> -Original Message- > From: Arthur Barstow [mailto:art.bars...@nokia.com] > Sent: Monday, July 01, 2013 7:20 AM > > On 6/27/13 1:05 AM, ext Jungkee Song wrote: > > Hi, > > > > I updated the Interop status of Progress Events: > > http://www.w3.

[PE] Interop Status Update

not tested the WebKit nightly build yet. It would be appreciated if someone shares the result. To Microsoft team, Do you have any dev update in IE10 which brings any changes in the test result? Thanks and regards, Jungkee Jungkee Song Samsung Electronics

RE: RE: [XHR] readystatechange for multiple open calls

> -Original Message- > From: Hallvord Reiar Michaelsen Steen [mailto:hallv...@opera.com] > Sent: Thursday, May 16, 2013 7:02 PM > > The conclusion is this commit: > https://github.com/whatwg/xhr/commit/972797fb12106ca00292b9a2e2cb91d8766c4 > 640 > The ED has been updated with the change:

RE: [XHR] readystatechange for multiple open calls

I just noticed that the topic has been discussed in another thread early this week. Sorry for rushing around after all that. BTW, what was the conclusion? > -Original Message- > From: Jungkee Song [mailto:jungkee.s...@samsung.com] > Sent: Thursday, May 16, 2013 5:33 PM &g

[XHR] readystatechange for multiple open calls

owser implementations show: - Firefox fires. - Chrome and Opera do not. Jungkee Jungkee Song Samsung Electronics

[XHR.Bleeding-edge] ED update

Hi, I just updated ED with WHATWG changes: https://dvcs.w3.org/hg/xhr/raw-file/tip/Overview.html We are now mostly in sync with the WHATWG version. Here's the changelog: https://dvcs.w3.org/hg/xhr/log Please reply if you find any issues with the applied changes. Jungkee Jungkee Song Sa

Re: [admin] Call for Agenda topics for April 25-26 f2f meeting

gt; > FYI, the HTMLWG and WAI PF WG will have co-located f2f meetings that week > (see [HTMLWG-Agenda]). > > -Regards, Art and Chaals > > [Agenda] <> > [HTMLWG-Agenda] > <http://www.w3.org/wiki/HTML/**wg/2013-04-Agenda<http://www.w3.org/wiki/HTML/wg/2013-04-Agenda> > > > > > > > -- Jungkee Song

RE: [XHR] remove "user cancels request"

> From: Timmy Willison [mailto:timmywill...@gmail.com] > Sent: Monday, February 25, 2013 2:55 AM > > > On Feb 24, 2013, at 11:18 AM, Glenn Maynard wrote: > > > On Sun, Feb 24, 2013 at 8:18 AM, Anne van Kesteren > > > wrote: > > > Currently the XMLHttpRequest Standard special cases the conditio

RE: Declarative invocation and progressing Web Intents

+1 Regards, Jungkee 2013. 1. 23. 오후 9:38에 "Nilsson, Claes1" 님이 작성: > +1 > > ** ** > > *From:* frederick.hir...@nokia.com [mailto:frederick.hir...@nokia.com] > *Sent:* den 22 januari 2013 21:14 > *To:* freda...@live.com > *Cc:* frederick.hir...@nokia.com; public-...@w3.org; > public-web-inte..

Re: RfR: Progress Events Test Cases; deadline January 28

2013. 1. 20. 오전 12:39에 "Arthur Barstow" 님이 작성: > > On 1/19/13 10:20 AM, ext Jungkee Song wrote: >> >> I've pushed the php file in < http://dvcs.w3.org/webapps/ProgressEvents/tests/submissions/Samsung/resources/> but cannot find it at mirror. Can anyone

Re: RfR: Progress Events Test Cases; deadline January 28

org/hg/webapps/rev/52b745cebe4f Thanks for comments. Jungkee > > > -- > http://annevankesteren.nl/ > -- - Jungkee Song Samsung Electronics

Re: CfC: publish WD of XHR; deadline November 29

On Sun, Dec 2, 2012 at 11:07 AM, James Robinson wrote: > > Sure there is if the W3C version is stale, as is the case here. I don't think it's a technical issue to discuss. There should be corresponding publication rules. Art, Charles, Doug, Can you help clarifying which links we have to use? In

RE: CfC: publish WD of XHR; deadline November 29

> From: Arthur Barstow [mailto:art.bars...@nokia.com] > Sent: Tuesday, November 27, 2012 3:05 AM > > I think the next step is for the XHR Editors to create a TR version > using the WD template so that everyone can see exactly what is being > proposed for publication as a TR. Please create that vers

RE: CfC: publish WD of XHR; deadline November 29

> From: Arthur Barstow [mailto:art.bars...@nokia.com] > Sent: Monday, November 26, 2012 9:46 PM > > On 11/26/12 1:38 AM, ext Jungkee Song wrote: > > I suggest we put the following wordings for Anne's work and WHATWG to be > credited. If we make consensus, let me use t

RE: CfC: publish WD of XHR; deadline November 29

Hi, I suggest we put the following wordings for Anne's work and WHATWG to be credited. If we make consensus, let me use this content for publishing the WD. As the co-Editors of W3C XHR spec wrote in the threads, we have our role and contribution in moving this spec toward the W3C REC. Up to the

[PE] interface MessageEvent : ProgressEvent

already a CR, I am planning to focus on satisfying the > exit criteria to ship it. Please see inline comments and questions. > > Jungkee > > > > From: Arthur Barstow [mailto:art.bars...@nokia.com] > > Sent: Thursday, November 15, 2012 10:51 PM > > > > On 11/

[PE] Start working on Progress Events

; Sent: Thursday, November 15, 2012 10:51 PM > > On 11/15/12 3:11 AM, ext Jungkee Song wrote: > > Hi Art, Charles and Anne, > > > > At this stage, it will be of great help if you give me some comments on > any issues, concerns, expected actions, etc. > > Since the s

[XHR] ED update

the ED contains annotation for test coverage now. [1] http://dvcs.w3.org/hg/xhr/raw-file/tip/Overview.html Jungkee Jungkee Song Samsung Electronics

RE: RE: [XHR] Open issue: allow setting User-Agent?

> -Original Message- > From: Hallvord Reiar Michaelsen Steen [mailto:hallv...@opera.com] > Sent: Wednesday, October 17, 2012 3:50 PM > > > > The point is that a browser can act as if every single server response > > > included "Vary: User-Agent". And perhaps should. Intermediary caches >

RE: [XHR] Open issue: allow setting User-Agent?

> -Original Message- > From: Boris Zbarsky [mailto:bzbar...@mit.edu] > Sent: Wednesday, October 17, 2012 2:09 AM > > On 10/16/12 1:04 PM, Mark Baker wrote: > > That would be an improvement, but wouldn't solve the problem of > > intermediary cache poisoning. > > Ah, yes. Intermediary cache

RE: [XHR] Open issue: allow setting User-Agent?

> -Original Message- > From: Boris Zbarsky [mailto:bzbar...@mit.edu] > Sent: Monday, October 15, 2012 9:50 PM > > On 10/15/12 7:18 AM, Jungkee Song wrote: > > but if certain backend intends to provide its content under some browser > requirements, isn't

RE: [XHR] Open issue: allow setting User-Agent?

> -Original Message- > From: Boris Zbarsky [mailto:bzbar...@mit.edu] > Sent: Sunday, October 14, 2012 12:49 AM > > On 10/13/12 5:08 AM, Hallvord R. M. Steen wrote: > > I came across an article [1] that describes some of the reasoning for > > Flash's change in security policy when it banned

RE: [XHR] Open issue: allow setting User-Agent?

scenarios. Jungkee > -Original Message- > From: Hallvord R. M. Steen [mailto:hallv...@opera.com] > Sent: Wednesday, October 10, 2012 12:34 AM > To: Julian Aubourg; annevankeste...@gmail.com > Cc: Anne van Kesteren; Jungkee Song; public-webapps@w3.org > Subject: Re: [XHR

RE: [XHR]

be in several states. The readyState attribute must return the current state, ...", sounds reasonable assuming non-blocking scenarios. It also supports the use case that Hallvord mentioned above. Regards, Jungkee Jungkee Song Samsung Electronics

RE: [WEBIDL] nullable dictionary members

Thanks for the comment, Boris! Jungkee > -Original Message- > From: Boris Zbarsky [mailto:bzbar...@mit.edu] > Sent: Thursday, August 16, 2012 3:26 PM > To: public-webapps@w3.org > Subject: Re: [WEBIDL] nullable dictionary members > > On 8/15/12 10:05 PM, Jungkee S

[WEBIDL] nullable dictionary members

ld like to explicitly describe certain dictionary members are required while others are not. Regards, Jungkee Jungkee Song Samsung Electronics

[WEBIDL] nullable dictionary

le type or has a dictionary type as one of its flattened member types. ->8- It does not allow "nullable" here. >From the mail history I looked up, the intention is to not allow nullable dictionary type any more. It that right? Regards, Jungkee Jungkee Song Samsung Electronics

RE: Lazy Blob

make > more sense to me to make the changes directly to the relevant specs, > namely FileAPI and XHR. I've copied Anne, Arun, and Jonas - any thought? > In either case, I'm happy to provide the content. Having hammered out a consensus, I would like to contribute to providing the content. Jungkee Jungkee Song Samsung Electronics

RE: Lazy Blob

have all the existing file reader options with no additional concern such that they do any further operations with the result reader.readAsDataURL(blob); // or reader.readAsBinaryString(blob); // or reader.readAsText(blob); // or reader.readAsArrayBuffer(blob); } Regards, Jungkee Jungkee Song Samsung Electronics

RE: Lazy Blob

Hi Glenn and all, > From: Glenn Maynard [mailto:gl...@zewt.org] > Sent: Thursday, August 02, 2012 12:45 AM > To: Robin Berjon > Cc: WebApps WG; Jungkee Song > Subject: Re: Lazy Blob > >> On Wed, Aug 1, 2012 at 9:59 AM, Robin Berjon wrote: >> var bb