00:25
<jpwhiting>
MikeSmith: have you ever seen an error log like this: http://pastebin.com/EmmgBUjS
00:25
<jpwhiting>
it builds fine on my debian wheezy machine, not sure what kind of distro is on the obs worker, but I can find out
00:25
<jpwhiting>
this is what I'm getting
00:26
<jpwhiting>
the end result is that nu.valudator.client.Main isn't compiled, so the validator.jar has the Main.java. but not Main.class
00:26
<jpwhiting>
so --local run fails
00:26
<rillian>
TextTrack's addCue and removeCue methods have "If the given cue is/is not in a text track list of cues" conditionals
00:26
<rillian>
does it define what comparison of cues is?
00:26
<rillian>
same object? object with the same properties and values?
01:09
<jpwhiting>
ugh, copyright symbols are messing up the java compiler on the build machine
01:10
<MikeSmith>
jpwhiting: the build for ./util/src/nu/validator/xml/dataattributes/DataAttributeDroppingContentHandlerWrapper.java is failing
01:10
<jpwhiting>
yep, just noticed that
01:10
<jpwhiting>
can I tell the javac that the file encoding is utf-8 rather than ascii somehow?
01:10
<MikeSmith>
because "package nu.validator.htmlparser.impl does not exist"
01:11
<jpwhiting>
or do I just need to set the encoding in the build machine env somehow
01:11
<jpwhiting>
like locale en_US.UTF-8 or something
01:11
<MikeSmith>
so the parser is not built
01:11
<jpwhiting>
yep, because it fails on a copyright symbol in the .java files
01:11
<MikeSmith>
this may be due to some circular dependencies
01:12
<MikeSmith>
and if so the only way to resolve it is to re-run the build
01:12
<jpwhiting>
no, it's because javac is interpreting the .java files as ascii, but they have unicode copyright symbols in them
01:12
<jpwhiting>
yep, I'm running --local build twice
01:13
<jpwhiting>
maybe I need to patch the build system to call javac -encoding utf8 ?
01:13
<MikeSmith>
also, "./syntax/non-schema/java/src/org/whattf/checker/XmlPiChecker.java:1055: error: unmappable character for encoding ASCII" is weird
01:13
<jpwhiting>
see these lines : /htmlparser/src/nu/validator/htmlparser/impl/Tokenizer.java:31: error: unmappable character for encoding ASCII
01:13
<jpwhiting>
yep
01:13
<MikeSmith>
I have never seen that before
01:14
<MikeSmith>
jpwhiting: ah yeah
01:14
<MikeSmith>
I thought I had already done that "-encoding utf8" thing
01:15
<jpwhiting>
do I just add that to the ant file where it calls javac?
01:16
<MikeSmith>
dunno but I think we have an opne bug for it, with a patch. lemme check
01:16
<jpwhiting>
ah, maybe build/build.py runJavac can be patched to pass -encoding utf8
01:17
<jpwhiting>
what bug tracker do you use btw?
01:17
<jpwhiting>
i.e. which url, I didn't notice anything about it on the about.validator.nu site
01:17
<MikeSmith>
http://bugzilla.validator.nu/
01:18
<jpwhiting>
thx
01:19
<MikeSmith>
that server is really really slow sometimes
01:19
<MikeSmith>
like, now
01:19
<jpwhiting>
:) yep, seems to be
01:19
<jpwhiting>
probably because us is still awake, maybe some of europe, and asia is getting up too
01:21
<MikeSmith>
http://bugzilla.validator.nu/show_bug.cgi?id=941
01:21
<jpwhiting>
searching encoding on there doesn't give any obvious bug entries, but you can probably find it easier than I can
01:21
<jpwhiting>
ah, there it is
01:23
<MikeSmith>
- runCmd('"%s" -g -nowarn -classpath "%s" -sourcepath "%s" -d "%s" %s'\
01:23
<MikeSmith>
+ runCmd('"%s" -encoding UTF-8 -g -nowarn -classpath "%s" -sourcepath "%s" -d "%s" %s'\
01:24
<MikeSmith>
I'll commit that change right now and push it upstream
01:24
<MikeSmith>
I don't know why it causes no problem in my local environment
01:24
<MikeSmith>
maybe java looks at $LANG or something
01:31
<jpwhiting>
yeah, I think so, ok cool, I'll update my tarball with that change
01:31
<jpwhiting>
thanks for looking into it :)
01:33
<MikeSmith>
thanks for catching it :)
01:33
<jpwhiting>
yep, np
02:52
<smaug____>
rafaelw: sorry, I'm late with that event loop spinning + microtask thing. I'll try to remember think about it tomorrow (or annevk will kick me)
02:56
<annevk>
:evilsmile:
03:32
<jpwhiting>
MikeSmith: what does "Exception in thread "main" java.lang.UnsupportedClassVersionError: nu/validator/servlet/Main : Unsupported major.minor version 51.0" mean when I try to run in my simulator vm
03:32
<jpwhiting>
the simulator's jdk or jvm is too old?
03:32
<MikeSmith>
no clue
03:32
<MikeSmith>
can't recall seeing that one before
03:33
<jpwhiting>
it's running openjdk-7-jdk u3-2.1.1 wheras I've been building on a machine with u3-2.1.7
03:33
<jpwhiting>
k, /me googles
03:34
<MikeSmith>
ah
03:34
<MikeSmith>
oh wait
03:34
<MikeSmith>
so both are Java7 environments?
03:34
<jpwhiting>
yep
03:35
<jpwhiting>
one is newer than the other though
03:35
<jpwhiting>
2.1.1 vs 2.1.7
03:35
<MikeSmith>
hmm
03:35
<jpwhiting>
I'll try backporting 2.1.7 to this ubuntu version I'm using on the simulator in the morning and see if that does it
03:35
<jpwhiting>
google results are suggesting the same
03:36
<MikeSmith>
if you can make your compiler compile it as Java6 that would be fine. We don't have any Java7isms in there afaik
03:36
<MikeSmith>
ok
03:36
<jpwhiting>
ah, ok, I'll give that a shot too, yeah, I can just change the build dep to make it use openjdk-6 rather than 7 when building
10:33
<Ms2ger>
r? https://github.com/w3c/web-platform-tests/pull/246 https://critic.hoppipolla.co.uk/r/216
14:23
<matjas>
is it okay to use <data> to embed JSON-formatted data in a document, like this? <data value='{"foo":"bar"}'></data>
14:23
<matjas>
note that it has no content in this case
14:24
<matjas>
basically, i want an alternative to <script>window.data = <% server-generated JSON goes here %>;</script>
14:24
<matjas>
…without using inline scripts, so that I can still enable CSP
14:25
<matjas>
option 1: load the data through Ajax after page load = bad for performance
14:25
<matjas>
option 2: use <script src=server-side-script-that-outputs-the-data-as-a-js-file></script> → additional HTTP request = bad for performance
14:26
<matjas>
option 3: hide the data somewhere in the DOM (in a hidden element, or in an attribute value) and use JS to read it out and `JSON.parse()` it
14:26
<matjas>
none of those solutions are as performant as a simple inline <script>, though
14:27
<matjas>
thoughts?
14:27
<zewt>
on a quick look at the spec, it looks like <data> is valid for this, but since there's no human-readable data associated with it, dataset might be preferable
14:28
<annevk>
matjas: how is that different from <body data-json=...> ?
14:28
<matjas>
zewt: that would be option 3, right? something like <div data-foo="<% json goes here %>"></div>
14:28
<zewt>
is it actually faster? i'd think there'd be a chance that parsing the data as json might be faster than parsing it as javascript, since it's a much tighter format
14:29
<matjas>
annevk: not different… you’re right, just an attribute value would be better since there is no useful non-machine content
14:29
<zewt>
(if there's any measurable difference at all)
14:29
<matjas>
zewt: ah, i hadn’t considered that
14:31
<matjas>
thanks! I’ll go with `data-json='…'` and `JSON.parse()` then
14:33
<matjas>
note to self: don’t forget to escape ' in the serialized JSON data as &#x27;
14:34
<zewt>
reminds me, i need to check my foo = <?= jsonencode(foo) ?>'s for </script> escaping
14:48
<matjas>
zewt: don’t forget about <!-- either
14:49
<matjas>
hsivonen_ suggest simply escaping any occurences of `<`: http://mathiasbynens.be/notes/etago#comment-8
14:49
<matjas>
suggests*
16:22
<gsnedders>
Is there any point in releasing tests which are going to be handled by idlharness.js?
16:26
<annevk>
maybe if you annotate them as such so they can be deleted later on?
16:30
<galant>
how can I put inside border in some element
16:31
<galant>
inside shadow sry not border
16:31
<dglazkov>
good morning, Whatwg!
16:32
<TabAtkins>
galant: Use the "inset" keyword.
16:34
<galant>
thanks
17:04
<Hixie_>
annevk: are we up to date with respect to fullscreen event attributes?
17:04
<Hixie_>
annevk: c.f. http://www.w3.org/mid/CADnb78jr+rBRYR_iFuB3WwY-U=XxfQJokqO0CWCx3ob=jSSysA⊙mgc
17:08
<Hixie_>
i'm going to assume that e-mail is out of date.
17:15
<annevk>
Hixie_: looks like we're all good
17:16
<Hixie_>
k
17:17
<annevk>
yeah, seems we revised our thinking of how to organize things since then
17:18
<Hixie_>
annevk: what's the story with HTMLElement.dataset? Do you want that on Element?
17:18
<annevk>
I've been thinking about it, to satisfy the SVG (and Math?) crowd
17:18
<TabAtkins>
Hixie_: Yes, please. SVG wants data.
17:19
<Hixie_>
annevk: you gonna reply on the relevant whatwg thread?
17:19
<Hixie_>
from february?
17:19
<Hixie_>
or should i?
17:19
<Hixie_>
i don't really care either way
17:19
<Hixie_>
i guess i'll reply saying it's your problem
17:19
<Hixie_>
:-)
17:19
<annevk>
Hixie_: I already replied there
17:20
<Hixie_>
yeah but your reply wasn't a "yes" or a "no" it was "let's make this bikeshed bigger"
17:20
<Hixie_>
:-P
17:20
<annevk>
Hixie_: one reason I haven't done it yet is because I haven't seen adoption yet of the Element.id/Element.className stuff, but maybe I haven't been paying sufficient attention
17:20
<Hixie_>
k
17:26
<annevk>
Belated :-)
17:36
<TabAtkins>
Hixie_: Why does <style scoped> have to be the first child of the element. >_<
17:37
<Hixie_>
so it doesn't style things before it, same reason <style> has to be in <head> and not randomly in <body>
17:38
<TabAtkins>
But now I have to add code to my preprocessor to move <style> blocks around just to satisfy the validator.
17:38
<Hixie_>
not just to satisfy the validator
17:39
<Hixie_>
also to avoid restyling in incremental rendering
17:42
<TabAtkins>
In this case, the only thing above it is an <h1>. ;_;
17:43
<Hixie_>
yeah but what if the parser stalled between the <h1> and the <style>?
17:43
<Hixie_>
then it'd render the h1 one way, then suddenly rerender it
17:43
<Hixie_>
that's bad for performance
17:43
<Hixie_>
and ugly
17:43
<TabAtkins>
Well, assuming I was styling the <h1>, which I'm not. But whatever.
17:43
<TabAtkins>
Still, I guess I can fix this. Just annoying.
17:44
<Hixie_>
you could just wrap the rest in a <div> then
17:44
<SimonSapin>
<style> has to be in <head>? Really?
17:44
<Hixie_>
or <main>, if that's applicable
17:44
<Hixie_>
<style> has had to be in <head> since like 1996
17:45
<SimonSapin>
Hixie_: that’s an author requirement, right? UAs should still apply <style> that are not in <head>
17:45
<Hixie_>
yes
17:47
<annevk>
can <input type=hidden> precede <style>? :-p
17:47
<Hixie_>
no
17:49
<TabAtkins>
Okay, that was an easier fix than I thought. Anyway, I now produce valid HTML documents (at least for this spec - we'll see as I publish more things under my preprocessor).
17:49
<GPHemsley>
annevk, Hixie_: Thoughts? https://www.w3.org/Bugs/Public/show_bug.cgi?id=22641
17:50
<Hixie_>
that entire section is non-normative.
18:09
<galant>
I am not sure how textAlign and textBaseline work on the canvas when I shoul type x y coordinates for the starting text?
18:10
<galant>
also in which place browser draws the text in that x y coordinates?
18:10
<galant>
I place 0 0 but top left of the text is not in the top left corner of the canvas why?
18:11
<galant>
hm
18:12
<galant>
so if I use textAlign cwenter and textBaseline middle then x,y coordinate is the middle of the text
18:31
<annevk>
http://html5.org/r/8051 sorting is hard :)
18:31
<annevk>
galant: you want something like #html5 for such questions I think
18:39
<annevk>
smaug____: https://dvcs.w3.org/hg/IndieUI/raw-file/default/src/indie-ui-events.html very much has a uiactions attribute
18:40
<annevk>
Hixie_: ^^ uncoordinated extensions to HTML
18:41
<smaug____>
annevk: yes, that is a "new" thing
18:42
<smaug____>
there was something else before
18:42
<smaug____>
annevk: something effectively like mutation event
18:42
<smaug____>
for some attributes
18:42
<annevk>
o_O
18:42
<smaug____>
or something like that
18:43
<annevk>
smaug____: so the idea is that these events only dispatch if this attribute is used?
18:44
<smaug____>
that mutation event -like thing isn't there anymore
18:44
<smaug____>
I have to re-read the spec
18:50
<annevk>
That specification is terrible :/
18:55
<galant>
thanks
18:56
<galant>
ok annevk sry
18:57
<annevk>
galant: you're free to ask here, it's just that most people here are focused on documenting the web
18:57
<annevk>
/ understanding it
19:08
<reyre_>
when comparing TextTrackCue's like in TextTrack::AddCue() should we be doing by value or by ref compare? http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html#dom-texttrack-addcue
19:08
<Hixie_>
galant: i don't understand your question, can you ask again?
19:08
<Hixie_>
reyre_: by identity (ref)
19:08
<Hixie_>
annevk: ?
19:09
<annevk>
Hixie_: that draft, which is being implemented by at least Apple as I understand it, is adding an attribute to HTML; I thought I'd let you know
19:09
<Hixie_>
aah
19:10
<Hixie_>
seems not unreasaonable
19:12
<reyre_>
Hixie_: awesome, thanks
19:31
<galant>
Hixie_, sry I wasn't arround
19:31
<galant>
Hixie_, I solved my problem, thanks guys for trying to help me
19:37
<smaug____>
aha, there I said it. nanotasks. That will be the next lower level task handling. Don't know what they will be for or how they are defined, but obviously we need them.
19:46
<annevk>
Taskception. WE NEED TO GO DEEPER!
19:46
<galant>
I write text with canvas then I am writing over that text same text but with white color and then again I am rewriting the text over with old color however I get some white dots appearing still from the white letters
19:47
<Hixie_>
galant: yeah, antialiasing will do that
19:47
<galant>
hm
19:47
<Hixie_>
galant: you're better off clearing the whole canvas each frame, in my experience
19:47
<galant>
:S
19:47
<galant>
ok thanks
19:53
<galant>
man its working like a charm now ^^ :)
19:53
<galant>
omg im so happy
19:56
<galant>
is light webgl performing good in pcs without graphic cards? please invest time in webgl improe it i has so much potential
20:27
<jpwhiting>
MikeSmith: up by chance?
20:27
jpwhiting
guesses not since it's not even 6am there
20:36
<TabAtkins>
Hixie_: Your mail client messes up unicode?
20:36
<TabAtkins>
See Björn's name in your most recent response to Anne.
20:36
<Hixie_>
yeah i just updated to a more recent version of pine and i haven't spent the time to work out what settings i need to tweak
20:37
<Hixie_>
theoretically it's better than the previous version, which was encoding ignorant
20:37
<Hixie_>
but i may have broken it through whatever hacks i had in before
20:39
<Hixie_>
GPHemsley: another example of something that is needed from a mouse event spec is defining when form controls get focused in response to clicks
20:48
<ap>
Hixie_: just noticed that all browsers fail Acid3 on my machine - pixel results don't match because reference image gets upscaled for Retina
20:48
<Hixie_>
yeah, acid tests are only valid on 96dpi displays
20:52
<Domenic_>
+1 nanotasks
20:59
<Hixie_>
how the hell does my .bashrc containing just:
20:59
<Hixie_>
export LC_ALL=en_US.UTF-8
20:59
<Hixie_>
...result in my Mac OS X environment containing:
20:59
<Hixie_>
LANG=en_US.UTF-8
20:59
<Hixie_>
...and no LC_ALL ???
21:00
<Hixie_>
not that setting LC_ALL is doing what i want either
21:06
<jsbell>
Hixie: MacOS uses .bash_profile not .bashrc
21:06
<Hixie_>
uh
21:06
<Hixie_>
it doesn't use both?
21:06
<jsbell>
apparently not
21:07
<Hixie_>
fun
21:07
<Hixie_>
thanks
21:08
<Hixie_>
locale -a outputs, amongst many others, "en_US.utf8"
21:09
<Hixie_>
when i set LC_ALL to "en_US.utf8", i get: locale: Cannot set LC_CTYPE to default locale: No such file or directory
21:09
<Hixie_>
wtf
21:26
<Hixie_>
annevk: is the thread "Proposal: Adding methods like getElementById and getElementsByTagName to DocumentFragments" on your radar?
21:28
<Hixie_>
TabAtkins: right, in theory my encoding woes are fixed...
21:33
<Hixie_>
"I think it more common for people to interact mainly with people in their
21:33
<Hixie_>
own timezone. I.e. most time when talking about dates and times people
21:33
<Hixie_>
don't me nation what timezone is involved and rely on contest to provide
21:33
<Hixie_>
that information.
21:33
<Hixie_>
"
21:33
<Hixie_>
i'm assuming sicking means "context", not "contest", though the latter is funnier
21:34
<Hixie_>
(also i assume "me nation" is "mention")
21:56
<annevk>
Hixie_: yes
21:57
<Hixie_>
excellent
21:57
Hixie_
deletes it from his
22:15
<annevk>
file URLs :/
22:41
<annevk>
smaug____: hmm, addedNodes should have been insertedNodes
22:41
<annevk>
smaug____: kinda of a naming failure
22:42
<smaug____>
hmm, probably yes
22:57
<GPHemsley>
Hixie_, annevk: http://wiki.whatwg.org/wiki/Mouse_interaction
23:13
<jpwhiting>
MikeSmith: around?
23:14
<jpwhiting>
I've hit a couple issues with packaging, one is that dependencies/jetty-6.1.26/lib/ext/libsetuid.so is a 64 bit library, is validator.nu only supposed to work on a 64 bit system?
23:14
<jpwhiting>
or is that library not even used maybe?
23:15
<jpwhiting>
the other issue is when I run it's still trying to load schema http://s.validator.nu/html5.rnc but I thought I removed that from w3c-presets.txt so it shouldn't show up when I run
23:16
<jpwhiting>
and I'm getting a java.lang.StackOverflowError with com.thaiopensource.relaxng.impl.ChoicePattern.checkRestrictions over and over in a huge stack
23:17
<jpwhiting>
ah, it's saturday morning there, you're probably gone :)