- все
Hi folks, minutes are at https://www.w3.org/2017/04/17-html-minutes.html and below:
Next meeting in 2 weeks time.
- DRAFT -
HTML meeting
17 Apr 2017
See also: [2]IRC log
[2] http://www.w3.org/2017/04/17-html-irc
Attendees
Present
JoshuaBell, chaals, PLH, Léonie, SteveF, Travis, Arron,
AGColom
Regrets
AlexD
Chair
Léonie
Scribe
chaals
Contents
* [3]Topics
1. [4]Issue #829 Hooks for IndexedDB StructuredSerialize
2. [5]Milestone progress
3. [6]High priority issues
4. [7]Diff progress
5. [8]timelines
6. [9]other business
7. [10]Next meeting in 2 weeks time
* [11]Summary of Action Items
* [12]Summary of Resolutions
__________________________________________________________
Issue #829 Hooks for IndexedDB StructuredSerialize
LJW: What do you need?
JB: recently because of Web Assembly there has been a rework in
wwg of "structured clones" or passing structured data, en
PostMessage, and storage API, IndexedDB, Notifications API.
... It has been split from a single structured clone, assuming
object in -> object out, there are now to parts, structured
serialise to turn a live object into a storage-ready
representation, and a corresponding reverse operation.
Additionally there are places where we would like to treat
storage APIs differently.
... so we're looking at something like different structured
serialisations for storage and transfer. Difference being that
a shared arraybuffer can't be stored, so would throw if you try
to store instead of transfer where it might be fine.
... Some of this has landed or been made into PRs for wwg, and
IndexedDB needs to integrate with this. So we would like the
specs to match…
s/match …/match for these pieces./
LJW: Do you have a sense for timeline on this?
JB: Hope the design can be done within a couple of weeks…
LJW: What about implementation interop on this?
JB: Not perfect… there was a thread in Chrome identifying
behavioural differences between Chrome/Firefox/Safari
... we'll aim to align in a few weeks, when we've got clear
design.
LJW: SO we should be tracking this for the moment?
JB: Sure.
... we dont have anything stable yet for design.
<jsbell>
[14]https://groups.google.com/a/chromium.org/d/topic/blink-dev/
dnzvgTswfbc/discussion
[14] https://groups.google.com/a/chromium.org/d/topic/blink-dev/dnzvgTswfbc/discussion
PLH: What's the impact on deployed indexedDB applications -
will they have to change anything?
JB: No, this is a new datatype introduced - breakage might hit
people who are experimenting with the new stuff, but not
already-deployed stable standard things.
[CMN outlines process for making changes]
PLH: I assume that there are tests being built too so that we
ca see what the interop is when we're looking to put this into
the spec.
LJW: Sounds like a question of work then...
... Thanks Josh for joining us.
JB: cheers…
Milestone progress
[Josh leaves]
CMN: I expdect to have most of my milestone issues done for the
milestone, at risk is #819 - is td in thead a header cell…
SF: I expect to get my issues for this milestone done.
PLH: I'm not going to resovle issues...
LJW: We pushed all yours across to Xiaoqian.
... so you should be fine.
PLH: I expect Xiaoqian to be busy next week with the AC
meeting.
LJW: We have #785 (rAF) and #281 ruby content assigned to PLH
[Travis/Arron arrive]
LJW: Travis has 10 issues open on this milestone including one
high-priority, Arron 3...
TL: Mike's rewrite of linking is the high-priority one?
CMN: Is that editorial?
TL: Believe so - I didn't include new content here.
PLH: Good - there is a spec for the things you might have added
already.
... rel=prerender is on the way out, I would not rely on it as
a developer.
<plh> q/me :)
LJW: Travis, you expect to be able to clear your issues?
TL: Yes.
AE: #254 - srcdoc rendering with quirks mode doctype - looks
like it is at risk, the other two should be ok.
<agcolom> Hi, I'm able to join if the meeting is not finished
yet...
LJW: Sangwhan has 11 issues for this milestone and we don't
expect him to make much progress in this month.
... he has one high priority, @@
TL: That's close to stuff I was doing, I can take that.
<agcolom> I think I need a password to join?
LJW: another high priority one: #756
AE: I'll look at that, I think I fixed it.
TL: We are doing a rebuild for 5.1 with errata?
LJW: looks likely.
TL: Then if this is just a linking issue it would be nice to
fix it as well. Who is going to build the spec.
[I assume Xiaoqian, for publishing purposes]
CMN: It is possible, given the very small number of changes to
be made, that we actually do it by editing the existing source
code directly. So I don't think this is high priority for 5.1,
but is for 5.2 if it still happens.
LJW: If anyone gets their work done, and has capacity, please
grab issues from Sangwhan.
High priority issues
LJW: we added a high priority, but as predicted we are
struggling with getting them done as a high priority.
TL: I find it to be helpful in giving me a good sort order. We
haven't had a lot of new stuff come in in the last couple of
weeks...
LJW: We might want to set aside time at these meetings to
triage issues for priority.
AE: Sure.
SF: I did my high priority work. I'd love more…
... have a when it's ready issue 584 and there is a whenever we
can issue I have.
[Welcome to Anne-Gaelle]
CMN: Xiaoqian and AlexD have a high-priority security issue…
<scribe> ACTION: PLH to ask Yves and Xiaoqian to check their
issues and let us know if they don't expect to meet the
milestones. [recorded in
[15]http://www.w3.org/2017/04/17-html-minutes.html#action01]
[15] http://www.w3.org/2017/04/17-html-minutes.html#action01
Diff progress
LJW: How are we getting on with measuring the diff to wwg
TL: Arron and I haven't looked at that in a while.
<Travis>
[16]https://cdn.rawgit.com/w3c/html/master/SOURCES.html
[16] https://cdn.rawgit.com/w3c/html/master/SOURCES.html
TL: looks like we don't have very good coverage even for
assigning owners of sections.
<tink> SF: Will take semantics sections.
[/me will put himself down for acknowledgements, having done
most of that so far]
TL: Think we should assign someone the job of getting a report
on the diff and getting back for this on the next call.
LJW: I hear you are volunteering...
TL: OK. After High Prority bugs.
timelines
LJW: Next WD goes out at end of May - that's the last milestone
where we can put stuff in before CR.
... closes on June 2nd, is called CR draft not WD8 in github.
Currently we have few closed issues and some open ones against
that.
[Note that we also need to assess stuff for marking "at-risk"]
scribe: CMN: Any thoughts on the implementation report?
CMN: If you merged something and didn't leave a trail to show
implementation (where it's new), I guess you will be wasting my
holidays tracking it down, and I will feel accordingly about
you…
other business
<agcolom>
[17]https://docs.google.com/document/d/1qg5FrSsjNimllfPb6Vk0MgC
AQCuU6-ielC81SrHeOes/edit?usp=sharing
[17] https://docs.google.com/document/d/1qg5FrSsjNimllfPb6Vk0MgCAQCuU6-ielC81SrHeOes/edit?usp=sharing
LJW: Note there is a CfC open to publish a 2nd edition - small
edits to fix a problem where we broke something with bad links.
AGC: This is some stuff I am doing to review - won't be a
perfect thing but is questions I have as I go along. Which
means sometimes I find the answers later...
... I haven't found anything major, just minor things I am
happy to fix, if someone want to go through it with me I would
appreciate that.
LJW: Thank you for chasing this.
... I would be happy to go through it with you.
SF, CMN also volunteer…
AGC: This is the sort of thing I like doing.
[ \o/ ]
LJW: for things like typos, we welcome all the help we can get :)
AGC: I am reading the spec from start to finish, taking notes
as I go.
Next meeting in 2 weeks time
[adjourn]
Summary of Action Items
[NEW] ACTION: PLH to ask Yves and Xiaoqian to check their
issues and let us know if they don't expect to meet the
milestones.
--
Charles McCathie Nevile - standards - Yandex
chaals@yandex-team.ru - - - Find more at http://yandex.com