Re: Service Workers meeting info

2016-08-11 Thread Léonie Watson

On 11/08/2016 11:41, Jake Archibald wrote:

Notes were taken in IRC, here's a
log https://gist.github.com/jakearchibald/c65009efa2ed9dbe3ad38f5fef5a4ef1. 
Here's
my run-down of the
headlines https://jakearchibald.com/2016/service-worker-meeting-notes/.


Thanks Jake. Both added to the WP meetings page [1].

Léonie.
[1] https://github.com/w3c/WebPlatformWG/blob/gh-pages/Meetings.md



--
@LeonieWatson tink.uk Carpe diem




[Bug 20322] Upload progress events vs CORS

2016-08-11 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20322

Anne  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #22 from Anne  ---
I just went with what implementations do for now:
https://github.com/whatwg/xhr/commit/667d4f3604aaee4e24bde33ed487cf8a98274e70

Basically always require listeners upfront...

I also submitted a correction for Hallvord's test based on what implementations
do today: https://github.com/w3c/web-platform-tests/pull/3451

-- 
You are receiving this mail because:
You are on the CC list for the bug.


Re: CFC: Publish a FPWD of IndexedDB 2.0

2016-08-11 Thread Léonie Watson
With thanks to everyone who responded. This CFC received only positive 
responses, and so passes without objection.


Léonie.


--
@LeonieWatson tink.uk Carpe diem

On 03/08/2016 15:46, Léonie Watson wrote:

Hello WP,

This is a Call For Consensus (CFC) to publish a First Public Working
Draft (FPWD) of IndexedDB 2.0 [1].

We are still exploring different ways of responding to a CFC. Please
choose one of the following methods:

1. Reply by email to this thread (on
public-webapps@w3.org).

2. Reply or +1 on Github:
https://github.com/w3c/IndexedDB/issues/84

There is no need to use more than one method. The WP chairs will collate
the results across all channels.

Please respond by end of day on Wednesday 10th August. Positive
responses are encouraged, but silence will be taken as consent with the
proposal.

Thanks
Léonie on behalf of the WP chairs and team
[1]
http://w3c.github.io/IndexedDB/




Re: Service Workers meeting info

2016-08-11 Thread Jake Archibald
Notes were taken in IRC, here's a log
https://gist.github.com/jakearchibald/c65009efa2ed9dbe3ad38f5fef5a4ef1. Here's
my run-down of the headlines
https://jakearchibald.com/2016/service-worker-meeting-notes/.

On Tue, 12 Jul 2016 at 11:52 Léonie Watson  wrote:

> Hello WP,
>
> Information for the meeting on 28/29 July is here:
>
> https://github.com/w3c/WebPlatformWG/blob/gh-pages/meetings/16-07-28-29SW.md
>
>
> If you plan to attend, it would be helpful if you could create a PR to
> add yourself to the attendees list (or let me know and I'll add you).
>
> Thanks.
> Léonie.
>
>
> It looks like the meeting info is complete on this page, except for --
> @LeonieWatson tink.uk Carpe diem
>
>


Re: CFC on referencing the Image Description (longdesc) extension

2016-08-11 Thread Léonie Watson
A quick reminder that this CFC closes at the end of day tomorrow (Friday 
12th August).


Thanks.
Léonie.

--
@LeonieWatson tink.uk Carpe diem

On 05/08/2016 18:17, Léonie Watson wrote:

Hello WP,

This is a Call For Consensus (CFC) on the following proposal for
referencing the Image Description (longdesc) extension specification
[1]. The CFC is posted to public-webapps@w3.org because this is the
official WP email list, and copied to public-h...@w3.org.

The proposal:

1. Remove the longdesc attribute from the table of attributes in HTML core.
2. Remove the IDL information for the longdesc attribute from HTML core.
3. Keep the longdesc examples in HTML core **.
4. Create a WG Note listing known extension specifications ***.
5. Include a link to the HTML Extension Specifications Note from HTML
core (probably in the index).

** Examples throughout the HTML specification are informative, and we
include informative examples and information for other specifications
and extensions
elsewhere in HTML core.

*** We anticipate that the Note will be updated as we identify new/other
extension specifications.

We are still exploring different ways of responding to a CFC. Please
choose one of the following methods:

1. Reply by email to this thread.
2. Reply or +1 to the original proposal comment on Github [2].

There is no need to use more than one method. The WP chairs will collate
the results across all channels.

Please respond by end of day on Friday 12th August. Positive responses
are encouraged, but silence will be taken as consent with the proposal.

Thanks
Léonie on behalf of the WP chairs and team
[1]  https://www.w3.org/TR/html-longdesc/
[2] https://github.com/w3c/html/issues/507#issuecomment-237068400