00:32
<MikeSmith>
did something change recently with regard to styling of Wikipedia pages in Firefox?
00:33
<MikeSmith>
when I look at Wikipedia pages in Firefox recently, it seems like there's less white space around the content, maybe smaller line hight, smaller font
00:33
<MikeSmith>
it doesn't look good
00:34
<MikeSmith>
hmm, I see now there's a background image there too, which I don't see in other browsers
00:34
<MikeSmith>
at that top
00:34
<MikeSmith>
or some kind of funky gradient
00:49
<JonathanNeal>
Is there a clever combination of preserveAspectRatio, width, and height properties that can render me an SVG that would automatically cover any element it was made the background image of?
00:54
<terinjokes>
JonathanNeal: baby tears
00:55
<JonathanNeal>
lemme try that
01:03
<heycam>
JonathanNeal, does specifying a viewBox but no width/height attributes work?
01:11
<MikeSmith>
can anybody else connect to irc.w3.org right now?
01:11
<MikeSmith>
just lost my connection
01:17
<jgraham>
MikeSmith: I think I did too
01:18
<MikeSmith>
jgraham: yeah I'm checking with systems team now
01:18
<MikeSmith>
(harder to do when we're not on the same IRC channel...)
01:22
<TabAtkins>
JonathanNeal: If you just don't use a viewBox, widht, or height at all, it'll automatically fill the space it's used in (the entire background area).
03:07
<MikeSmith>
jgraham: w3c-test.org unreachable as well
03:07
<MikeSmith>
I can't even ssh to it from within the firewal
03:14
<JonathanNeal>
I’m also unable to connect to irc.w3c.org
03:19
<MikeSmith>
JonathanNeal: try now
03:20
<JonathanNeal>
I’m in. Thanks.
03:45
<zewt>
this 'outsmart the user and copy random crap out of the address bar" browser fad needs to end already
04:21
<JonathanNeal>
zewt: are you referring to copy hijack?
04:29
<zewt>
no, how I'll copy part of a url from the address bar and it's completely random whether i'll get the protocol at the start of the url or not
04:30
<zewt>
because some middle manager decided that showing "http://" in the address bar is somehow bad, so now there are obnoxious heuristics for browsers to decide what to copy
04:37
<JonathanNeal>
zewt: never experienced that, but I know if I copy a URL before it has been visited and the http isn’t present, then it doesn’t add it.
04:37
<JonathanNeal>
What browsers does this happen on?
04:38
<zewt>
firefox and chrome both try to be too clever
04:39
<zewt>
any browser that doesn't show the http protocol inherently has this problem (since then they have to play dumb games when you copy the url to figure out if they need to add it back in for the copy op)
04:40
<zewt>
so stupid things happen, like i'll copy just the hostname to ping a site and end up pasting a url instead of what i copied; or i'll edit a url in the address bar (eg. to simplify an amazon url), paste it and now the protocol is missing
12:16
<MikeSmith>
ISOC is holding a workshop today focusing on "DNSSEC Successes, Statistics and Innovation"
12:16
<MikeSmith>
meanwhile, only 0.43% of .COM domains are DNSSEC-signed...
12:18
<MikeSmith>
emperor's new clothes
12:35
<darobin>
MikeSmith: on the contrary, I think it makes perfect sense
12:35
<darobin>
given sufficient innovation in statistics, you can find success in DNSSEC
12:35
<MikeSmith>
hahah
12:36
<darobin>
you got it all, right there
12:36
<MikeSmith>
they should hire you to do their PR
12:36
<darobin>
shouldn't everyone?
12:37
<MikeSmith>
heh
12:39
<Ms2ger>
No.
14:22
<JakeA>
wanderview: So, range requests. Any idea how the browser defends against getting none-matching partials
14:22
<JakeA>
as in, the underlying resource has changed between range requests
14:23
<JakeA>
leading to the cached version being a frankenresource
14:24
<JoWie>
probably using Last-Modified
14:26
<JakeA>
JoWie: you are right https://tools.ietf.org/html/rfc2616#section-13.5.4
14:30
<JoWie>
ah but only if Date is more than 60 seconds after Last-Modified
14:30
<JoWie>
ETag also works
14:44
<annevk>
JakeA: we need to decide on that used flag thing for Request/Response
14:45
<JakeA>
annevk: ok, brain dumping on the restarting download issue, then will move onto that
14:45
<annevk>
JakeA: note that we need support for range in the cache API too
14:45
<JakeA>
annevk: I'm brain dumping on that too
14:46
<annevk>
JakeA: and we need to figure out how synthetic 206 behaves
14:46
<annevk>
excellent
14:46
<annevk>
ta
14:46
<JakeA>
annevk: I guess your thinking is similar to mine then. Cache never contains 206 responses but it may vend them depending on the request in .match(request)
14:47
<annevk>
I haven't really figured this out yet
14:47
<annevk>
Note that we do allow synthetic 304 at the moment
14:47
<annevk>
Which is the equivalent for a cached non-partial response
15:30
<JakeA>
wanderview: I WAS JUST WRITING THAT
15:30
<JakeA>
now I'm not going to seem as smart
15:30
<wanderview>
JakeA: the content-length thing? annevk and I were talking about it yesterday
15:31
<JakeA>
wanderview: nah, "I would prefer if just have getReader() set the flag"
15:31
<wanderview>
oh, yea... lets reduce the insanity
15:31
<wanderview>
JakeA: btw, does chrome implement the incumbent cache record and partial cache entries yet?
15:31
<JakeA>
wanderview: I doubt it, but I don't know for sure
15:50
<wanderview>
JakeA: thanks... just curious if I should be in a hurry to implement that
15:50
<wanderview>
I still have a hard time wrapping my head around what the spec says now
15:52
<wanderview>
JakeA: I guess the issue is, if the download of the Response is happening outside of Cache, then cache can't do any automatic restart... the fetch() needs to do the range request in order to avoid duplicating the initial download
15:52
<wanderview>
do we need to support restarting for both external-to-cache fetch() and internal-to-cache fetch()?
15:52
<wanderview>
I think solving for external-to-cache fetch() should be the higher priority
16:34
<wanderview>
annevk: where is null body distinguished/used in html spec?
16:35
<annevk>
wanderview: did I write HTML?
16:35
<annevk>
wanderview: oops
16:35
<wanderview>
oh, you wrote http
16:37
<wanderview>
annevk: I don't understand what the proposal is any more
16:38
<wanderview>
annevk: JakeA: Domenic: maybe we should sit down in SF in July to figure this out
16:38
<annevk>
The proposal is that Response/Request have an associated "used flag" that is set by fetch() / put() / getReader()
16:38
<annevk>
If the flag is set, fetch() / put() / getReader() throw
16:38
<annevk>
(also new Request())
16:39
<annevk>
Whether body is null or a stream is not important
16:39
<wanderview>
annevk: it just sucks that we have special case logic outside of fetch in put(), etc
16:40
<wanderview>
outside of fetch spec
16:40
<wanderview>
annevk: I would prefer to just do it getReader() and if body is null then don't mark used... its all consistent whoever uses the Response then
16:42
<annevk>
How does that work with new Request()?
16:42
<annevk>
Because that is what fetch() and put() use today
16:42
<annevk>
To normalize some other stuff
16:43
<wanderview>
annevk: ok... then put() doesn't do anything special... it uses new Request() which makes setting the flag internal to fetch
16:43
<wanderview>
annevk: I want setting the used flag to be done by the fetch spec and no one else... and Cache only uses public API calls from fetch to do it... the constructor works for that
16:44
<annevk>
Okay
16:44
<annevk>
I guess the only case that's not explained is the getReader() scenario
16:44
<annevk>
At least not through new Request()
16:44
<wanderview>
annevk: well, fetch spec needs to integrate with getReader() somehow... either through weasel-words or wrapping the stream or observing the stream somehow
16:45
<wanderview>
Domenic: is there a way to observe the getReader() call? ^^^
19:33
<WeirdAl>
hi folks - does either the HTML spec or the 6th edition of ECMAScript specify how to load a JS as 6th-ed ECMAScript (so that we get 6th-ed features such as the let statement)??
19:33
<Domenic>
wanderview: no, not without monkey-patching
19:33
<Domenic>
getReader() being observable is nonsensical
19:33
<Domenic>
you can just do .getReader().releaseLock() and you've done nothing
19:35
<Domenic>
> I want setting the used flag to be done by the fetch spec and no one else // if that's what you want, it's easy, just keep a side-table
19:35
<Domenic>
but I thought you also wanted to throw if someone else read using a reader
19:49
<Ms2ger>
WeirdAl, there are no versions. JS is JS
19:49
<WeirdAl>
Ms2ger: uh huh... then tell me how I can have the same script tag, and the same script, in a HTML document, and use let blocks, in both Google Chrome and Mozilla Firefox.
19:50
<Ms2ger>
let blocks? Those don't exist :)
19:50
<WeirdAl>
FF wants type="application/javascript;version=1.7" or a higher version - but GC won't recognize that MIME type.
19:50
<WeirdAl>
(in the script tag)
19:51
<WeirdAl>
if you put "use strict" in the script that seems to be enough for GC, except for the aforementioned type attribute problem
19:52
<WeirdAl>
ok, let statements, not let blocks :p
19:54
<WeirdAl>
basically, I want a common way to say "this JS should be loaded as if it were dependent on the 6th edition of ECMAScript."
19:57
<Ms2ger>
<script>
19:57
<Ms2ger>
Maybe not today, but soon enough
20:01
<WeirdAl>
:-| okay... and what if I want to use experimental "7th-edition" features? (Please, don't say polyfill.)
20:02
<WeirdAl>
(also, is there a FF bug to turn on 6th edition by default?)
20:05
<Ms2ger>
No, but there should be a bug to enable let bindings by default
20:12
<WeirdAl>
grumble grumble
20:23
<Ms2ger>
WeirdAl, I'm being pointed at https://bugzilla.mozilla.org/show_bug.cgi?id=950547
20:27
<WeirdAl>
https://bugzilla.mozilla.org/show_bug.cgi?id=932513#c5 is interesting
20:43
<Domenic>
there is no such thing as versions in browser, WeirdAl.
20:44
<Domenic>
versions are a fiction propagated by spec writers
20:44
<WeirdAl>
editions, then
20:44
<Domenic>
no such thing
20:44
<Domenic>
they are made up
20:44
<Domenic>
browsers just implement features, in some random order
20:45
<Domenic>
sometimes they implement features from edition 5, sometimes from 6, sometimes from 7
21:14
<wanderview>
Domenic: yes I do want normal stream readers to result in the used flag being set... I think annevk was suggesting we do the set flag as soon as getReader() is called the first time... I told him I thought you would dislike that since you want it on stream close
21:14
<wanderview>
Domenic: I just want us all to settle on something at this point
21:14
<Domenic>
wanderview: yes :(
21:15
<Domenic>
offset seemed like a big concession from me; I'm surprised it wasn't enough to get everyone on board.
21:15
<wanderview>
Domenic: if nothing else we can talk after the SW f2f if you are in SF that week
21:16
<wanderview>
Domenic: well, I think annevk is trying to do the breaking change so we don't need the offset all... I think we viewed that as a concession as well
21:16
<Domenic>
wanderview: when is the SW f2f? I will be at the custom elements f2f July 21...
21:17
<wanderview>
Domenic: its the day before the custom elements... annevk and I will be in town until Thursday I think
21:17
<wanderview>
he might leave on Thursday
21:17
<Domenic>
oh perfect, ok
21:17
<wanderview>
so maybe Wednesday
21:17
<wanderview>
?
21:17
<Domenic>
yeah sounds good
21:17
<wanderview>
cool