03:51
<MikeSmith>
Yeah I guess we should just make it always by credit default print out that file
03:54
<MikeSmith>
But if the "quiet" option is set, only print the file out if there are errors
08:29
<zcorpan>
can FrozenArray<DOMString> be used for a live array?
08:41
<MikeSmith>
> zcorpan: MikeSmith: ok. but can it print the content of that file even on success?
08:41
<MikeSmith>
Yeah I guess we should just make it always by credit default print out that file
08:41
<MikeSmith>
But if the "quiet" option is set, only print the file out if there are errors
08:42
<MikeSmith>
zcorpan: also a question for you: do you care much whether wattsi emits its messages to stdout or stderr
08:43
<MikeSmith>
it seems to me that it rightly should be emitting all its messages to stderr
08:43
<MikeSmith>
it seems like you were initially surprised to see that it was sending them to stdout
08:43
<zcorpan>
MikeSmith: sounds good. i tried implementing that this morning but didn't get the logic right :-)
08:43
<MikeSmith>
ok I'll try it today
08:43
<zcorpan>
MikeSmith: i don't really care about stderr vs stdout
08:43
<MikeSmith>
ah ok
08:44
<MikeSmith>
I guess I won't bother changing it then
08:44
<MikeSmith>
zcorpan: but do you think it's important that wattsi exit non-zero if there are errors?
08:45
<zcorpan>
MikeSmith: i only care about seeing the errors :-)
08:45
<MikeSmith>
ok fair enough
08:46
<MikeSmith>
but the if it doesn't exit non-zero for the error case it makes it pretty hard to do any sane CI automation for it
08:47
<zcorpan>
true
08:47
<MikeSmith>
ok
08:47
<MikeSmith>
anyway right now I'll deal with getting the error emitted reliably by the html-build build script
08:48
<zcorpan>
thx
08:51
<MikeSmith>
and sorry for the headaches you've had needing to deal with the build hassles. I had wanted to get this stuff working reliably back in September (which would have been before you were back full-time I think) but life got in the way I and I really haven't touched any of this for more than 2 months until I got to your PRs yesterday along with the PR I'd had left hanging open since the end of September
08:51
<MikeSmith>
anyway, will get it all righted
08:56
<zcorpan>
no worries, html-build has worked fine for me, really
08:57
<zcorpan>
my wattsi build problems were apple's fault
09:08
<zcorpan>
Domenic: can we adopt the "snapshot as of this commit" thing in streams for all our specs? (then we can also make "file an issue" link use the snapshot URL, and maybe clicking a <dfn> can include a stable link)
09:35
<zcorpan>
nice https://drafts.csswg.org/indexes/#properties
10:04
<MikeSmith>
very cool
10:24
<annevk>
zcorpan: an Array is not live
10:28
<MikeSmith>
FYI for folks who care about e-mail archives
10:28
<MikeSmith>
https://github.com/w3c/mailing-list-archives
10:28
<MikeSmith>
https://lists.w3.org/Archives/Public/spec-prod/2015OctDec/0089.html
10:28
<Ms2ger>
Hey, anyone who knows things about canvas2d around?
10:28
<MikeSmith>
"We are planning to modernize the markup and style of our mailinglist archives, to improve readability and usability and todisplay better on a wider variety of devices."
10:29
<MikeSmith>
Ms2ger: Philip` maybe
10:29
<Ms2ger>
Ha
10:54
<annevk>
Can anyone just host files in your repository? https://github.com/whatwg/notifications/issues/57#issuecomment-165652739
11:19
<annevk>
(reported to GitHub)
14:55
<smaug____>
hayato: dglazkov: does blink already have deprecation warnings for the old shadow dom API?
15:09
<rits>
i am compiling watttsi, but during the build getting this error http://pastebin.com/fFKKAqdb
15:12
<gsnedders>
rits: what version of fps do you have?
15:12
<gsnedders>
*fpc
15:13
<gsnedders>
because that looks like it's confused between 3.0.0 and 2.6.2 for some reason?
15:13
<rits>
gsnedders: 3.0.0
15:14
<rits>
gsnedders: yes, the error seems relate to that but i have installed 3.0.0
15:19
<gsnedders>
rits: can you try pastebinning bash -x ./build.sh (or whatver shell)
15:20
<rits>
gsnedders: yes
15:20
gsnedders
doesn't really know /that/ much about fpc
15:21
<rits>
gsnedders: this one is a ./build.sh result only http://pastebin.com/fFKKAqdb
15:22
<rits>
me too, there is not much resource on the internet about fpc errors too
15:24
<gsnedders>
As far as I can see, there's nothing passing in any -FM anywhere, so it's coming from within fpc… :\
15:24
<gsnedders>
I presume there's some FreePascal IRC channel, maybe it'd be worthwhile asking there?
15:25
<gsnedders>
Unless MikeSmith can help? (He runs the AWS instance hosting it I think?)
15:27
<rits>
gsnedders: yes, i will try to asking on any FreePascal channel, otherwise will comment there on the issue, might be whenever they are around, will solve it then
15:31
<ondras>
hmh
15:31
<ondras>
flexbox + overflow
15:31
<ondras>
http://stackoverflow.com/questions/14962468/flexbox-and-vertical-scroll-in-a-full-height-app-using-newer-flexbox-api
15:31
<ondras>
can someone please explain *why* this works?
15:32
<ondras>
(i.e. setting arbitrary height on a "flex:1 1 auto" element)
15:32
<Domenic>
Fascinating, bfcache in blink? https://code.google.com/p/chromium/issues/detail?id=511340
15:33
<Domenic>
botie: tell zcorpan that generalizing stream's snapshot system has been a TODO of mine for a while, and I would welcome some help...
15:33
<botie>
will do
15:37
<gsnedders>
rits: let us know what the solution is!
16:20
<rits>
gsnedders: was afk, surely will tell the solution, tried two three but didn't worked, asking on their irc now :)
17:50
<dglazkov>
smaug____: not yet
18:00
<smaug____>
dglazkov: would be perhaps good, so that web devs don't start to rely more and more on deprecated API
18:03
<botie>
zcorpan, at 2015-12-18 15:33 UTC, Domenic said: generalizing stream's snapshot system has been a TODO of mine for a while, and I would welcome some help...
19:13
<TabAtkins>
annevk: I... guess? I'd just delete the thread.
19:29
<smaug____>
hmm, 491 tabs. time to close some of them
19:32
<TabAtkins>
ondras: That's an intentional and encouraged use of flexbox. The flex container is set to the full height of the page, and the article is the only part that can grow or shrink.
23:11
<MikeSmith>
rits: to compile wattsi, one thing is you need to make sure you're using the development version, not any of the release versions
23:12
<MikeSmith>
it must be the version from ftp://freepascal.stack.nl/pub/fpc/beta/3.0.0-rc1/
23:13
<MikeSmith>
I mean the fpc version
23:13
<MikeSmith>
and you need to make sure you don't have any other existing version of fpc already installed on your system
23:15
<gsnedders>
MikeSmith: like, fpc 3.0.0 (the released version) doesn't work? :(
23:17
<MikeSmith>
gsnedders: I don't know; have never tested it but Hixie has told me as recently as September that it needs to be the version from ftp://freepascal.stack.nl/pub/fpc/beta/3.0.0-rc1/
23:17
<MikeSmith>
it may be that 3.0.0 got released in the mean time works, I dunno
23:18
<MikeSmith>
but ftp://freepascal.stack.nl/pub/fpc/beta/3.0.0-rc1/ is what we're all using
23:24
<MikeSmith>
rits: http://www.lazarusforum.de/viewtopic.php?f=4&t=8344 has discussion of the same error
23:24
<MikeSmith>
(in German)
23:25
<MikeSmith>
but no resolution
23:26
<MikeSmith>
http://lists.lazarus.freepascal.org/pipermail/lazarus/2015-February/090281.html seems to suggest it's caused by the build picking up the wrong ppcx64 binary
23:27
<MikeSmith>
the fpc source distribution has its own ppcx64 binary that must be used instead, and the http://pastebin.com/fFKKAqdb error message indicates it's not using it
23:27
<MikeSmith>
Error: /usr/bin/ppcx64 returned an error exitcode