04:17
<tantek>
has anyone blogged about the latest longdesc fiasco, or is the "consensus" just to ignore it and move on?
04:22
<caitp->
consensus doesn't exist on the web
04:22
<caitp->
or anywhere else
04:24
<tantek>
caitp: any posts about it you know of? like pointing out all the crazy?
04:24
<caitp->
haven't seen any mention of it today
05:24
<roc>
?
05:30
<tantek>
hey roc
06:44
<tantek>
caitp: I posted https://twitter.com/t/status/571184745008095233
06:58
<annevk_>
I wonder whether it's time that CSSOM starts properly defining the side effects of accessing clientHeight et al: https://bugzilla.mozilla.org/show_bug.cgi?id=1135960
08:20
<annevk>
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/2LXKVWYkOus this is so great
08:21
<jochen__>
\o/
08:23
<annevk>
before you get too excited, overall peers at Mozilla didn't seem super compelled when I proposed something similar a while back
08:23
<annevk>
but hopefully eventually
08:33
<jochen__>
yeah, I guess we'll have to look at it on a case by case basis
08:33
<jochen__>
e.g. for geolocation, numbers on HTTP are surprisingly low, and the numbers of granted geolocation are even lower
08:33
<jochen__>
so it might not be a big deal for users anyway
08:34
<jochen__>
i'm kinda sad that there's still the argument that experimentation on http should work
08:34
<jochen__>
web developers should experiment on https
08:37
<annevk>
Yeah, with GitHub and localhost exception I don't really think that's an argument
08:38
<annevk>
I think for Web Crypto the argument has been that it can be polyfilled and that therefore there's no additional functionality, but that discounts that Web Crypto cannot be safe without TLS...
08:39
<annevk>
For geolocation and WebRTC it's been a combination of "too late now" and some more spurious arguments
08:39
<jochen__>
well
08:40
<jochen__>
numbers say it's not too late
08:40
<annevk>
Some of the others I had not considered though Joel's rationale makes sense
08:40
<annevk>
jochen__: that's certainly encouraging
08:43
<annevk>
jochen__: WebRTC WG was quite hostile to the idea, but forcing their hand works for me
08:43
<annevk>
jochen__: see e.g. https://www.w3.org/Bugs/Public/show_bug.cgi?id=26937#c3
08:44
<annevk>
Anyway, looking forward to updates :-)
08:45
<jochen__>
yeah
08:45
<jochen__>
currently, we're in the process of collecting usage numbers
08:45
<jochen__>
and based on these, we'll propose concrete steps to move forward on a per feature basis
09:08
<JakeA>
wanderview: yeah, I like the simplicity of that model. It means you can't use a sharedworker offline from a SW unless a document initiates it. Buuuuuuuut I don't think that's a problem
09:31
<zcorpan>
good news everyone, http://www.w3.org/TR/2015/REC-html-longdesc-20150226/
09:34
<Ms2ger>
You're late :)
09:48
<zcorpan>
if (i.longdesc)
10:03
<Ms2ger>
Why not have .longdesc and .longDesc both?
10:06
<gsnedders>
Anyone got a link to the IR for advancement to PR?
10:10
gsnedders
wonders what implementations they used
10:21
<zcorpan>
Ms2ger: thank you! i've never tried 99% before, will report back whether i like it :-)
10:28
<jgraham>
"Just a spoon full of cocoa poweder helps…" actually I don't know why you would want a spoon full of cocoa powder. Except for baking, I suppose.
10:29
<gsnedders>
jgraham: because everything should be chocolatey. EVERYTHING.
10:34
<zcorpan>
i usually put a teaspoon of cocoa powder in my protein shake
10:40
<Ms2ger>
zcorpan, I thought you'd like to try it :)
10:42
<MikeSmith>
fyi for people who love uri schemes https://mailarchive.ietf.org/arch/msg/ietf-announce/VGP7bgN8BN1kv2TDdE5d7-3w2Ug
10:42
<MikeSmith>
BCP request fo 'Guidelines and Registration Procedures for URI Schemes'
10:44
<MikeSmith>
> The file can be obtained via [URL that isn't a hyperlink because IETF's online-mail-archive software doesn't even turn URLs in messages into hyperlinks...]
10:44
<MikeSmith>
http://tools.ietf.org/html/draft-ietf-appsawg-uri-scheme-reg-04
10:45
<MikeSmith>
the registration procedures are at http://tools.ietf.org/html/draft-ietf-appsawg-uri-scheme-reg-04#section-7
10:49
<MikeSmith>
anyway, here's an idea for a better procedure: move all the registries into github repos and you just submit a PR for any new uri-scheme or media-type or whatever registrations
10:51
<MikeSmith>
that way the registries are all under publicly accessible version control, so you can see the history, etc., and changes are tied to referencable issues/PRs, etc
10:51
<Ms2ger>
Hehehehehe
12:38
<MikeSmith>
hsivonen: given the Codehaus news and the fact Jetty moved to Eclipse some time ago but the current validator dependency is still an outdated version that's only available from Codehaus, seems like it's probably time to update the dependency to a new version of JettyーI guess the latest version
12:47
<GPHemsley>
https://bugzilla.mozilla.org/show_bug.cgi?id=1060767
12:49
<GPHemsley>
https://bugzilla.mozilla.org/show_bug.cgi?id=1133409
15:28
<beverloo>
annevk, which version of anolis do you use?
15:28
<annevk>
beverloo: I'm not sure
15:28
<beverloo>
when I run it on the notifications spec I get a ton of changes in Overview.html unassociated with my changes
15:28
<Ms2ger>
Port to bikeshed first? :)
15:28
<annevk>
beverloo: I might have updated Anolis meanwhile and not regenerated that specification...
15:31
<beverloo>
I like the irony in the bikeshed project's name
15:31
<beverloo>
the notifications spec isn't too big, I'm happy to volunteer to do the conversion if that's desired?
15:31
<annevk>
beverloo: so... only comment I have on that PR is that I avoid newlines within <span> and such so I can more easily search and replace
15:32
<annevk>
beverloo: yeah that would be welcome
15:32
<Ms2ger>
It'll be a good day when I can finally retire anolis
15:33
<hsivonen>
MikeSmith: I've missed the codehaus news, but updating to latest makes sense
15:36
<beverloo>
annevk, ok, I'll change that. do you want me to include a regenerated overview.html?
15:36
<annevk>
beverloo: yeah I think that's fine
15:36
<beverloo>
annevk, I hereby sign up then. I'll regret this, won't I? :)
15:36
<annevk>
beverloo: dunno, we'll find out :-)
15:47
<beverloo>
annevk, amended
15:47
<annevk>
JakeA: so the alternative for use*URL is to just require a redirect, or would that be too cumbersome on authors?
15:57
<annevk>
beverloo: seems you forgot to add your name
15:59
<annevk>
Hmm it does seems like my copy of Anolis sorts attributes differently
15:59
<annevk>
Maybe I'll wait for the bikeshed conversion then to add that name
15:59
<beverloo>
sure
15:59
<annevk>
Well, I guess it doesn't matter, Overview.src.html can be used for sane diffs
16:00
<MikeSmith>
hsivonen: ok, will update
16:00
<beverloo>
annevk, I pulled anolis from ms2ger's hg repo just now
16:00
<beverloo>
1.3pre
16:02
<annevk>
1.2pre :-)
16:31
<wanderview>
annevk++
16:31
<wanderview>
for switzerland :-)
16:31
<annevk>
hehe
16:38
<wanderview>
JakeA: do you know what blink does when an https response is stored in the Cache? does it save certificate and trust info as well?
16:38
<wanderview>
as far as I can tell, that type of information is not represented in the fetch Response object
19:24
<TabAtkins>
beverloo: Or I can help with the conversion; converting Anolis specs to Bikeshed well is a little tricky.