05:28
<botie>
othermaciej, at 2015-08-23 01:26 UTC, MikeSmith said: Wondering if you have any opinion on implementation of Subresource Integrity https://bugs.webkit.org/show_bug.cgi?id=148363
05:29
<othermaciej>
MikeSmith: We are interested and looking into it, no firm commitment.
05:31
<MikeSmith>
othermaciej: ok, thanks
05:32
<MikeSmith>
othermaciej: as far as the WebAppSec group in general, it seems like it's turned out to an exceptionally productive and useful group
05:32
<MikeSmith>
which may not be saying much relative to some other W3C groups
05:33
<MikeSmith>
so even in absolute terms it seems like a highly productive place to get some Web-security-related problems solved
05:47
<othermaciej>
I don't know if this has happened yet but we were planning to put people from both WebKit and some Apple security teams in WebAppSec
05:51
<MikeSmith>
othermaciej: ah cool
05:51
<MikeSmith>
genuinely glad to hear that
05:51
<othermaciej>
We are pretty positive on what WebAppSec has been coming up with, as a matter of general sentiment.
05:54
<MikeSmith>
yeah it's an encouraging group
05:55
<MikeSmith>
they have a very good chair and one particularly good focused-on-just-getting-stuff-done editor
05:55
<MikeSmith>
it all comes down to individual people in the end
05:55
<MikeSmith>
regardless of where the work takes place
05:57
<MikeSmith>
anyway, I think the additional active involvement will definitely help a lot too
09:07
<zcorpan>
hello everyone
09:10
<hasather>
zcorpan: hi!
09:11
<zcorpan>
sup hasather
09:12
<Ms2ger>
Aloha
09:13
<Ms2ger>
Wanna review https://github.com/w3c/web-platform-tests/pull/2082 so I don't have to?
09:14
<zcorpan>
my first day and you give me document.write? why thank you
09:16
<Ms2ger>
It has document.write?
09:16
<Ms2ger>
Then I definitely want someone else to do it :)
09:19
<Ms2ger>
zcorpan, actually, while I have you here...
09:22
<Ms2ger>
Apparently Opera wrote a bunch of reftests for css21 tests back in the day, and lastorset released the references, but not which tests they were references for, any chance you could find that out? :)
09:25
<zcorpan>
Ms2ger: possibly. got a link to PR?
09:25
<Ms2ger>
https://github.com/operasoftware/presto-testo/commit/a0acfbef13a3f8cae67cc7145216d31b67aa8eb4
09:27
<zcorpan>
"There is an old database matching them to tests, but we're waiting to gain access."
09:28
zcorpan
lunch
09:59
<roc>
"my first day"?
10:00
<Ms2ger>
He's been on vacation for a while
10:00
<Ms2ger>
We haven't poached him, sadly :)
10:21
<MikeSmith>
welcome back zcorpan
10:43
<zcorpan>
Ms2ger: reviewed
10:47
<nox>
Ms2ger: Upstream'd test btw.
11:01
zcorpan
-> Paris
11:08
<Ms2ger>
nox, yeah, I saw, thank you
11:12
<nox>
Ms2ger: I was so confused.
11:12
<nox>
Ms2ger: "Where is css21_dev? Where are the HTML files?"
11:13
<Ms2ger>
Yeah :/
12:42
<annevk>
ooh, zcorpan is back, but not on IRC
12:42
<annevk>
maybe finally we can start specifying when synchronous layout happens
13:12
<smaug____>
hmm, where is .style property defined
13:12
<smaug____>
I thought CSSOM but no
13:12
<smaug____>
oh, maybe I'm looking at wrong spec
13:12
<tantek>
smaug____: well this is the attribute part: http://www.w3.org/TR/css-style-attr/
13:13
<annevk>
smaug____: https://drafts.csswg.org/cssom/#the-elementcssinlinestyle-interface
13:14
<smaug____>
does anything define at which point the DOM attribute is updated
13:14
<smaug____>
when .style.foo is set
13:15
<annevk>
smaug____: I don't think so
13:16
<annevk>
smaug____: actually, it seems CSSOM does
13:16
<annevk>
smaug____: "Mutating the declarations must set the style content attribute on the context object to the serialization of the declarations. If the style content attribute is set, changed or removed, the declarations must be updated as appropriate."
13:16
<annevk>
smaug____: bit too hand-wavy for my taste, but it is there
13:17
<smaug____>
indeed
13:17
<smaug____>
the case I'm wondering is .style.foo = "some invalid value"
13:18
<annevk>
If zcorpan was actually on IRC he could go and clarify...
13:20
<MikeSmith>
annevk: zcorpan is apparently on the way to Paris atm
13:21
<MikeSmith>
per earlier comment here
13:21
<MikeSmith>
about 2 hours ago
13:26
<MikeSmith>
annevk: could get botie to leave a comment for him
13:36
<TabAtkins>
annevk: I just pushed the serializer changes. Expect a huge output diff.
13:37
<MikeSmith>
hey TabAtkins about Chris Lord's Navigation Transitions spec
13:37
<MikeSmith>
is there plans for that in the CSS WG?
13:38
<MikeSmith>
as far as taking it up as a deliverable
13:38
<TabAtkins>
I have plans to do review on it this week.
13:38
<MikeSmith>
ok
13:38
<TabAtkins>
We haven't discussed taking it as a CSSWG deliverable yet.
13:38
<MikeSmith>
other Chrome team interest in possibly impelementing it?
13:39
<MikeSmith>
or maybe that th's pending your review
13:39
<TabAtkins>
We've discussed it a bit, but aren't convinced yet that is hitting the important use-cases properly.
13:40
<TabAtkins>
This'll show up in my review, yeah
13:41
<MikeSmith>
ok cool
14:17
<philipj>
TabAtkins: Did you just change something about whitespace in Bikeshed?
14:18
<philipj>
TabAtkins: I now get whitespace before commas where it shouldn't be, and other spurious whitespace changes
14:18
<TabAtkins>
Yup, committed a big serialization change
14:18
<TabAtkins>
To make whitespace less stupid
14:19
<TabAtkins>
Oh weird, file an issue on me with some example text
14:19
<TabAtkins>
Ohhhh I bet I know what I did wrong
14:19
<TabAtkins>
Will fix tonight
14:26
<philipj>
TabAtkins: Should I still file a bug?
14:30
<TabAtkins>
Yeah, so u don't forget
14:30
<TabAtkins>
I
14:33
<philipj>
TabAtkins: https://github.com/tabatkins/bikeshed/issues/464
17:33
<ccardona-work>
Good morning/afternoon WHATWG crew o/
19:27
<zcorpan>
TabAtkins: help? FATAL ERROR: The argument autolink 'other' for 'DOMPoint/fromPoint()' has too many possible overloads to disambiguate. Please specify the full method signature this argument is for. https://drafts.fxtf.org/bikeshed/geometry/
19:38
<wanderview>
Domenic: stupid question... does the Promise constructor call the provided callback synchronously or in a microtask?
19:38
<Domenic>
wanderview: sync
19:38
<wanderview>
thanks... I didn't see anything about the constructor in https://promisesaplus.com/
19:39
<Domenic>
wanderview: yeah, that's just the .then method for promise libraries. ES2015 promise spec is in the ES spec.
19:39
<Domenic>
Promises/A+ is somewhat historical at this point, I'd say?
19:39
<wanderview>
I just searched for "promise spec" and it was the first link
19:40
<Domenic>
huh, will you look at that
19:40
<Domenic>
maybe might be worth adding a link at the top...
19:41
<wanderview>
wow... the es spec thing to dynamically keep the header at the top is really buggy in FF nightly
19:41
<wanderview>
wonder if it could just use position:sticky
19:41
<wanderview>
or maybe it already is
19:44
<TabAtkins>
zcorpan: Will check on it. Are you referring to an argument via autolinking?
19:45
<zcorpan>
TabAtkins: i don't know what part it's complaining about. i have a <dfn> that mentions the argument, but other than that dunno
19:45
<Domenic>
wanderview: yeah I am pretty sure it does use position: sticky
19:50
<wanderview>
Domenic: hmm... now I can't duplicate the glitching
19:50
<wanderview>
oh well
19:50
<Domenic>
nightly ¯\_(ツ)_/¯
19:51
<wanderview>
aha! caught it https://www.dropbox.com/s/oizffofxdfgoypb/Screenshot%202015-08-24%2015.51.42.png?dl=0