00:55
<Hixie_>
me: "waah, editing HTML in the HTMLWG is too hard, i quit"
00:55
<Hixie_>
w3c: "ok, we'll hire 9 people to replace you"
00:56
<Hixie_>
time passes
00:56
<Hixie_>
the nine people: "waah, editing HTML in the HTMLWG is too hard"
00:56
<Hixie_>
...
01:59
<zewt>
when did browsers decide loading mouse cursors were "uncool"?
01:59
<zewt>
very sick of clicking links in chrome on macbook, sitting around for 20 seconds, then realizing the click didn't take and it's wasting my time but I couldn't tell because it's failing at UI 101
01:59
<zewt>
firefox does the same crap
03:51
<suman>
hi anyone there?
03:54
<sumankumardey>
i have a problem with html5lib ruby gem its taking very long time in production to respond. where as in development environment it work fines.
03:57
<sumankumardey>
hi baku
03:57
<baku>
hi sumankumardey
03:58
<sumankumardey>
can you help me out in solving an issue i have some problem with html5lib in production environment
03:58
<sumankumardey>
the execution halts as if it is infinite loop
03:59
<baku>
sumankumardey, sorry, I can't help you
04:00
<sumankumardey>
okay but the there is some problem with html5lib
04:00
<sumankumardey>
html5-0.10.0/lib/html5/treebuilders/rexml.rb:21:in `value='
04:01
<sumankumardey>
the execution halts after this
04:12
<sumankumardey>
sumankumardey: okay but the there is some problem with html5lib
04:12
<sumankumardey>
[09:32am] sumankumardey: html5-0.10.0/lib/html5/treebuilders/rexml.rb:21:in `value='
04:12
<sumankumardey>
[09:33am] sumankumardey: the execution halts after this
04:49
<roc>
TabAtkins: hey, now that you've forked Webkit, Chrome can implement the same-origin restriction for fonts
05:11
<krit>
roc: I think for the next couple of weeks, Blink has enough to do on clean up and restructuring
05:11
<krit>
roc: Don't expect that much "visible" change in the next weeks or months
06:13
<sumankumardey>
html5lib issue anyone can help me here?
06:20
<MikeSmith>
sumankumardey: I don't think anybody around here is actually using the ruby version of html5lib
06:20
<MikeSmith>
and nobody has touched that code for a long time
06:20
<MikeSmith>
maybe Sam Ruby came up that code?
06:20
<MikeSmith>
I can't remember now who wrote it
06:21
<sumankumardey>
okay..
06:21
<sumankumardey>
np
06:21
<sumankumardey>
thanks anyways..
06:23
<MikeSmith>
sumankumardey: but it sounds to me like whatever problem you are seeing is not caused by the source but was introduced by the packager of the ruby gem
06:23
<MikeSmith>
so that person -- whoever it is -- is probably the one you want to contact
06:24
<sumankumardey>
sure thank you
06:24
<MikeSmith>
sumankumardey: but even under ideal conditions I think the performance of that port of html5lib is really poor
06:24
<MikeSmith>
it was not designed to be fast
06:25
<sumankumardey>
but xss_terminate uses this gem as its dependency
06:26
<MikeSmith>
ah
06:42
<SteveF>
hixie: only 1 person was 'hired' to my knowledge, nobody 'quit' and I am happily editing HTML can't speak for the others
06:57
<a-ja>
SteveF: anywhere in particular to discuss Using ARIA in HTML draft? or PM?
06:58
<SteveF>
a-ja: html wg best place
06:58
<a-ja>
meant on irc. just a minor typo, i think
06:59
<SteveF>
a-ja: you can tell me now an i will capture it
07:00
<SteveF>
a-ja:so here or #html-wg is fine
07:00
<a-ja>
the recommendation on summary
07:01
<a-ja>
if summary element is being used in a scripted polyfill - Use role=button with aria-expanded="true" if the element's open attribute is present, aria-expanded="false" otherwise.
07:02
<a-ja>
should'nt that say on parent details element's open attribute?
07:04
<SteveF>
a-ja:yes, good catch will fix thanks!
07:05
<a-ja>
wasn't sure whether open attr got inherited somehow i'd missed
07:05
<SteveF>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21615
07:09
<a-ja>
Stevef: now to find a non-jq polyfill that handles kb input
07:10
<SteveF>
a-ja:can't help you there unfortunately, if you find one give me a yell
07:11
<a-ja>
will get around to forking one and doing it myself some day
07:13
<SteveF>
hixie: so trying to read between the lines of http://krijnhoetmer.nl/irc-logs/whatwg/20130408#l-50 does it mean its yes its OK to assign bugs to you or no its not? I am leaning towards the latter
07:17
<SteveF>
hixie: it would be useful to have sensible communications on such matters how can we make that happen?
07:18
<jgraham>
sumankumardey: The ruby version has been unmaintained for a *long* time
07:18
<jgraham>
I don't think anyone here knows anything about it
07:19
<jgraham>
Oh MikeSmith already said all that
07:19
<Ms2ger>
SteveF, you can assume that Hixie_ will take care of all bugs that exist in the WHATWG HTML specification
07:19
<jgraham>
gsnedders: Sure
07:19
<Ms2ger>
SteveF, does that answer your question?
07:19
<sumankumardey>
thanks jgraham
07:23
<SteveF>
Ms2ger: sort of
07:27
<SteveF>
Ms2ger: should bugs that are not taken care of in the W3C HTML specification have their product changed to WHATWG? I am trying to work out a reasonable work flow for managing bugs
07:28
<Ms2ger>
It's probably better to discuss that directly with Hixie_, I don't know if he tracks your bugs already
07:29
<SteveF>
Ms2ger: thats what I am trying to do...
07:34
<SteveF>
Ms2ger: most changes from WHATWG HTML flow back into W3C HTML once hixie has processed bugs, some don't after review and some bugs get dealt with by direct changes to W3C HTML
07:36
<SteveF>
Ms2ger: would be good if WHATWG and W3C could acknowledge that reality and work out an understanding on it
08:01
<SteveF>
Ms2ger: in a nutshell: all people involved can continue to play turf wars in the HTML web standards playground or we can try to work out a way to work together I prefer the latter but am accepting the former is more likely given the history
08:11
<jgraham>
Ms2ger: Why is resize:none needed?
08:17
<Ms2ger>
jgraham, because the handles are in different corners
08:18
<jgraham>
Oh, right reftests
08:18
<Ms2ger>
Yeah
08:18
<jgraham>
OK, merged
08:19
<Ms2ger>
Thanks
08:58
Ms2ger
finds some tests he forgot to submit
08:58
<annevk>
SteveF: well Hixie_ was replaced as editor by the W3C, so asking him to work on bugs for a product he's not the editor for is kind of weird given that dynamic
08:59
<annevk>
SteveF: and I don't think it's fair to expect Hixie_ to make good here
09:00
<annevk>
SteveF: that W3C is still taking his work while listing him as "Previous Editor" for instance seems like more than enough reason for him to be very upset
09:03
<mitemitreski>
annevk: the comunity knows him and respects him so I don't think that W3C can do much harm there
09:06
<annevk>
mitemitreski: sure, that seems a bit besides the point though
09:35
<zcorpan>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16757#c10 is interesting
09:51
<SteveF>
annevk: so the answer is to change the product?
09:51
<SteveF>
mitemitreski: don't think that its that simple
09:53
<annevk>
SteveF: Why don't you ask W3C management?
09:53
<SteveF>
annevk: I am not asking hixie to 'make good' I am asking how to make it work
09:53
<annevk>
SteveF: If you think Hixie_ should be editing (part of) the specification because none of the HTML editors are capable of addressing the bug, they might have some insight.
09:54
<annevk>
SteveF: I would not expect much more than blank stares though
09:55
<SteveF>
annevk: well thats why I am asking
09:55
<annevk>
SteveF: Are you asking them?
09:56
<annevk>
SteveF: To some extent it seems bugs have been cloned and then whenever Hixie_ gets around to it the original bug is closed with the same resolution. That still seems like working around the actual problem though.
10:02
<SteveF>
annevk: OK then thats fine what I have been doing is providing as much trail in bugs i resolve as possible, so that if anyone is interested they can see the diff. I make very few changes that effect browser implementation and when i do its because browsers are implementing some acc related stuff not specced, or there is something acc related missing in a proposed implementation
10:03
<SteveF>
annevk: I am not up to tackling the disfunctional relationship between whatwg and w3c at an organisational level though
10:05
<annevk>
I understood http://krijnhoetmer.nl/irc-logs/whatwg/20130408#l-230 differently, but that seems fine.
10:07
<annevk>
That the W3C is still plagiarising is bad though.
10:12
<SteveF>
annevk: talk to darobin or MikeSmith about the subject of plagiarising they both work for the W3C, I don;t I don't even work for a member company, I just do my best to improve the spec where I can
10:13
<smaug____>
is DAP still active?
10:13
<annevk>
smaug____: at until July per charter
10:14
<annevk>
at least*
10:14
darobin
was raised?
10:14
<darobin>
smaug____: DAP is still active, yes
10:15
<darobin>
smaug____: any specific question? I can probably point you in the right direction, or to people
10:15
<marcosc>
darobin, Annevk is calling you a dirty plagiarist :)
10:15
<smaug____>
just wondering whether filing bugs makes sense
10:16
<marcosc>
You and your co-plagiarist-conspirator, "Evil MikeSmith"
10:16
Ms2ger
throws darobin instead
10:19
jgraham
catches darobin
10:20
<SteveF>
note, anything I do as an editor of the html spec is in response to a direct (and secret) command from either MikeSmith or darobin
10:20
<jgraham>
Well we have established that darobin is Exceptional
10:21
<SteveF>
they call it 'operation deplagiarisation'
10:21
Ms2ger
frowns
10:22
<Ms2ger>
How did I just jump from 5025 tests to 14143 tests?
10:26
<darobin>
smaug____: depends on on which spec, some of them are abandoned
10:27
<darobin>
but if it's on one that's alive, then filing a bug definitely makes sense
10:27
<smaug____>
the latest one was the which has proximityevent
10:27
<darobin>
marcosc: hey, don't blame me, I'm just carrying out the programme of the Pirate Party :)
10:27
<smaug____>
it is just that someone should go through webidl usage
10:28
<darobin>
smaug____: as far as I know Proximity is alive and well, so bugs are good
10:28
<darobin>
I thing DougT was working on that, recently at least
10:29
<smaug____>
editors: Anssi Kostiainen, Nokia , Dzung D Tran, Intel
10:29
<smaug____>
and Anssi is now at Intel too
10:30
smaug____
could ask dougt, who is kind of his manager
10:31
<darobin>
smaug____: if you just have a problem with the IDL, I'd recommend simply emailing Anssi — he'll probably fix it in the time it takes to read your email
10:32
<smaug____>
yeah, could work
10:33
<smaug____>
oh, Intel's office in Helsinki isn't faraway
10:34
<darobin>
go have a beer with Anssi then, he's cool :)
10:34
<Ms2ger>
Walk into his office and make him fix it on the spot? :)
10:35
<darobin>
btw, if you know anyone who's into Rust/Servo and looking for a job, talk to me as I have someone looking for just that
10:35
<smaug____>
Ms2ger: exactly
10:36
<Ms2ger>
SimonSapin? :)
10:37
<jgraham>
darobin: Small target audience for that job :)
10:37
<darobin>
jgraham: yeah, I'm having trouble coming up with a name without poaching someone from Mozilla :)
10:38
<darobin>
Ms2ger: trying not to poach :)
10:38
<annevk>
darobin: haha, yeah, why don't just name them directly?
10:38
<jgraham>
Taking someone from Mozilla to work on Servo would be ironic
10:38
<jgraham>
Unless you mean non-Servo-rust
10:38
<darobin>
no, this is definitely Servo
10:38
<annevk>
darobin: reminds me of http://ln.hixie.ch/?start=1052961695&count=1
10:39
<jgraham>
darobin: I suggets you look for kickass developers and ignore the Rust part, because that's easy to learn
10:39
<darobin>
annevk: hahaha, yeah, pretty much
10:39
<darobin>
jgraham: that's what I was thinking too — if I were doing the hiring it's what I'd do
10:40
<darobin>
maybe grab some former Opera...
10:40
<darobin>
or soon-to-be former
10:42
<SimonSapin>
darobin: what is it about Servo?
10:43
<darobin>
SimonSapin: I have someone with a job opening for Servo/Rust work, I was just asking about recommendations
10:44
<SimonSapin>
I’m curious :)
10:49
<Ms2ger>
SimonSapin, you're wondering if they'd pay better? ;)
10:50
<jgraham>
heh
10:50
<SimonSapin>
Ms2ger: I’m gonna work on Servo, so I might work with them too
10:52
<Ms2ger>
In any case, I hope you're good at dealing with crappy syntax ;)
10:52
<SimonSapin>
I already got email from them about rust-cssparser, a while ago
10:52
<SimonSapin>
do you mean Rust?
10:52
<jgraham>
SimonSapin: Are we supposed to know the antecendent of "them"?
10:53
<Ms2ger>
Yeah
10:53
<SimonSapin>
https://blog.mozilla.org/blog/2013/04/03/mozilla-and-samsung-collaborate-on-next-generation-web-browser-engine/
10:53
<Ms2ger>
I mean, what I've seen so far makes my eyes bleed
10:53
<smaug____>
Rust syntax is indeed... interesting
10:53
<smaug____>
almost as horrible as python
10:54
<jgraham>
SimonSapin: So "them" == Samsung?
10:54
<SimonSapin>
yes
10:54
<jgraham>
Makes sense
10:54
<Ms2ger>
And was darobin talking about Samsung too?
10:54
<jgraham>
Curiously it's the rubyish parts of Rust syntax I don't like
10:54
<jgraham>
Although generally it doesn't seem too bad
10:54
<SimonSapin>
Ms2ger: ideas on how to improve it?
10:54
<SimonSapin>
smaug____: why is Python horrible?
10:55
<smaug____>
why isn't python horrible ;)
10:55
<Ms2ger>
SimonSapin, smaug____ has a Stockholm Syndrome with perl ;)
10:55
<smaug____>
python is like: do things differently for the sake of doing it differently
10:56
<gsnedders>
jgraham: Speaking of html5lib, the repo should probably have the old Py2 deleted.
10:56
<gsnedders>
jgraham: Given I never finished moving stuff to github.
10:57
<gsnedders>
jgraham: (Though it didn't work that great, too many early commits by none@none)
10:57
<jgraham>
Well I think it's better to just move stuff to GH
10:57
<jgraham>
I can look at that
10:57
<SimonSapin>
is html5lib dropping python 2 support?
10:57
<jgraham>
No
10:58
<gsnedders>
SimonSapin: No, moving to single codebase for Py2 and Py3.
10:58
<SimonSapin>
awesome
10:58
<Ms2ger>
\o/
10:58
<gsnedders>
SimonSapin: It's currently in the Py3 folder, though. The old Py2 folder is dead.
10:58
<gsnedders>
jgraham: You need to rewrite history multiple times, though, if you split it up, to ensure branches go all the way back and stuff like this. It's quite a mess.
10:59
<gsnedders>
jgraham: I'm happy to do it in a month or so after exams.
10:59
<gsnedders>
jgraham: I guess it'll take a day or so to do the split nicely
11:00
<jgraham>
Which branches?
11:00
<jgraham>
I don't actually care about anything other than master
11:00
<gsnedders>
I still care about csswg-testsuite or whatever it's called.
11:01
<gsnedders>
Also merging the Python3 folder into being a branch and ultimately being master was something I did before.
11:02
<gsnedders>
csswg-testsuite
11:02
<gsnedders>
* master
11:02
<gsnedders>
python3
11:02
<gsnedders>
Those are the branches I have.
11:04
<zcorpan>
annevk: in the Future introduction, i think function() { showFailcat } should be either function() { showFailcat() } or just showFailcat
11:06
<gsnedders>
jgraham: Nothing has happened since I merged everything into one Python tree, let me push this somewhere.
11:07
<annevk>
zcorpan: not confident? ;)
11:08
<zcorpan>
annevk: just humble :-P
11:08
<annevk>
heh
11:09
<marcosc>
function() { showFailcat() } is redundant, no?
11:09
<zcorpan>
annevk: domintro for any is missing a word "accepted rejected"
11:10
<annevk>
marcosc: yes
11:11
<zcorpan>
annevk: should the domintros end with "respectively"?
11:12
<annevk>
hmm yeah, maybe
11:12
<annevk>
I guess that's not implied
11:14
<jgraham>
gsnedders: I don't see a python3 head
11:15
<gsnedders>
Where?
11:15
<Ms2ger>
In the mirror
11:15
<jgraham>
In the html5lib repo
11:16
<gsnedders>
The mirror I pushed two seconds ago?
11:16
<jgraham>
Perhaps?
11:17
<gsnedders>
jgraham: in hg, there is no py3 head because it's just a folder.
11:17
<jgraham>
Right
11:17
<gsnedders>
jgraham: In https://github.com/gsnedders/html5lib-python it's not there because it hasn't been pushed because it's an obsolete branch
11:18
<jgraham>
IS there anything in your github repo that isn't in the main repo?
11:18
<gsnedders>
A merge of python3 into python.
11:18
<gsnedders>
Otherwise, no.
11:18
<gsnedders>
But I'm suddenly suspicious history is badly broken in places.
11:18
<jgraham>
OK, I will start from the main repo
11:19
<gsnedders>
A lot of files seem to be missing all Py2 history.
11:19
<gsnedders>
Probably some missing parent commit of something.
11:21
<gsnedders>
jgraham: Overwritten master so it's back to the earlier master-is-python and python3-is-python3 state, in case you want to try merging again.
11:22
<gsnedders>
jgraham: f77aa82ce9ec1b08586d92dc84e9cfcf5e6e8548 doesn't seem to have the correct parent
11:27
<gsnedders>
jgraham: Basically, that repo is *close* to what you want, but not quite it.
11:28
<jgraham>
gsnedders: Which repo? That isn't a commit in the repo I have (from google code)
11:29
<gsnedders>
jgraham: https://github.com/gsnedders/html5lib-python/commits/python3 — note the huge jump in commits of three years
11:29
<gsnedders>
jgraham: in the git one
11:29
<gsnedders>
jgraham: Looking at that it may be a couple away from where it is wrong, but you get the idea.
11:41
<zcorpan>
annevk: is the abstract still accurate?
11:44
<annevk>
zcorpan: how about "<p>DOM defines a platform-neutral model for events, futures, and document nodes."
11:45
<zcorpan>
annevk: works for me
12:01
<gsnedders>
jgraham: Will try and sort out the one big bit of history fuck-up later.
12:01
<gsnedders>
jgraham: Then hopefully we have something working
12:04
<gsnedders>
jgraham: The history appears fucked in hg, a parent in the future
12:05
<SimonSapin>
gsnedders: that can happen with rebase
12:08
<gsnedders>
SimonSapin: Right, yes, that's true. Then that makes sense.
12:42
<gsnedders>
jgraham: At some stage in the move I seem to have lost all tags. Whoops.
12:48
<gsnedders>
jgraham: I think history is now right on html5lib-python, and py-merge just needs merged into master (it's ff, so it should be fine)
12:51
<gsnedders>
jgraham: Now pushed the merge to master as everything looks fine.
12:52
<jgraham>
Are you talking the git repo you made?
12:52
<gsnedders>
Yes.
12:53
<gsnedders>
jgraham: Apart from the fact that all the early commits GitHub thinks are by invalid-email-address (i.e., "none@none", from the SVN -> hg move), it's done.
12:54
<gsnedders>
But we probably want to fix them before we do anything more, given it means rewriting history
13:06
darobin_
wonders how long it will be before he takes flak for https://github.com/w3c/html/commit/03823ce134a06b3ed84a409f584ed035ba55bc31
13:06
<daoribn>
fuck me
13:06
<Ms2ger>
Da Orbin?
13:06
<darobin>
yeah, that's how they called me in ancient Mesopotamia
13:51
<karlcow>
<!--END darobin-html--> <!--START darobin-html-->
13:54
<darobin>
karlcow: :)
14:05
<zcorpan>
Hixie_: some bugs appear to come from people who c/p error messages from v.nu (or maybe validator.w3.org). since the messages contain links to the spec, we could identify such bugs by looking at Referer
14:35
<darobin>
does anyone know why the <data> element isn't in the W3C spec?
14:36
<SteveF>
annevk: https://github.com/w3c/html/commit/261a168584e59785789604b191034cd3730b746b
14:36
<zcorpan>
probably it was invented when the w3c spec was in LC or something and Hixie wasn't supposed to add new features
14:37
<zcorpan>
about https://www.w3.org/Bugs/Public/show_bug.cgi?id=21572 how do people feel about "cooked text elements"?
14:38
<zcorpan>
or maybe "normal text elements"?
14:38
<zcorpan>
not that they're particularly normal
14:39
<Ms2ger>
Abnormal text elements?
14:41
<darobin>
zcorpan: ok, ta
14:41
<darobin>
that means I can add it
14:41
<zcorpan>
darobin: i bet there are more cases like that
14:41
<Ms2ger>
By the way
14:42
<darobin>
zcorpan: I've decided to hunt down leftover forks to kill them
14:43
<Ms2ger>
I'd like someone to create a tool to track if spec commits still need tests
14:44
<Ms2ger>
darobin, do you still have free time? :)
14:44
<sangwhan>
Ms2ger: TE is like that orphaned project which needs to be kicked out of the door as soon as possible. Hacks are expected.
14:44
<sangwhan>
Ms2ger: ...at least that's what I see from it.
14:44
<darobin>
Ms2ger: there's a f2f coming up, I'll have plenty of free time that week ;)
14:44
<Ms2ger>
sangwhan, that's what I said, no?
14:45
<Ms2ger>
sangwhan, I expected the response I got
14:45
<zcorpan>
Ms2ger: with metadata in the test saying it's testing a certain spec change?
14:45
<Ms2ger>
zcorpan, rather not
14:46
<Ms2ger>
Just a webapp where you can add URLs, say
14:47
<Ms2ger>
And notes about things that still need testing
14:47
<sangwhan>
Ms2ger: Yep, unfortunate but what can you do - the group had a bumpy start from the beginning..
14:48
<darobin>
Ms2ger: we're thinking about stuff like that, I could possibly hack on it soon in fact
14:49
<Ms2ger>
darobin, excellent :)
14:49
<Ms2ger>
darobin, hoping it'll track WHATWG commits ;)
14:50
<darobin>
Ms2ger: I haven't thought it out at this point, but I was thinking that a spec is just a URL
14:50
<darobin>
and any change tracking is just a GH stream
14:50
<darobin>
so I see no reason why not :)
14:50
<Ms2ger>
You know I'm no fan of gh ;)
14:50
<annevk>
sangwhan: TE?
14:50
<Ms2ger>
Touch Events
14:50
<sangwhan>
annevk: Touch Events
14:50
<darobin>
I operate under the assumption that WHAT/W3C is just a bicameral system
14:51
<annevk>
ohh
14:51
<darobin>
I serve the Web Republic
14:52
<annevk>
except the knowledge and speedy process is in the same chamber? :p
14:54
<darobin>
annevk: that reminds me of a joke someone tells in the West Wing
14:54
<annevk>
oh please do tell
14:54
<annevk>
I love that show
14:55
<darobin>
it's about a junior Republican senator who's talking with other Republican senators about a meeting they're about to have with Democrats
14:55
<sangwhan>
Does Firefox ship with statically linked OpenSSL? (possibly wrong channel, but I don't have IDA installed on this machine)
14:55
<SteveF>
+2 to "I serve the Web Republic"
14:55
<darobin>
and he says "Oooh, I can't wait to meet the enemy!"
14:55
<Ms2ger>
sangwhan, we use nss
14:56
<darobin>
to which the others reply "The Democrats aren't the enemy. The House of Representatives is."
14:57
<Ms2ger>
Must've been the way he told it
14:58
<darobin>
ow
14:58
<Ms2ger>
<3
14:59
<sangwhan>
Ms2ger: Oh, that I did not know. Thanks
15:06
<annevk>
darobin: hehe
15:17
<sangwhan>
Hmm, so not many low level optimizations in NSS it seems. There is some redundant compiler specific bootstrap code that seems to have gone a bit out of sync and does some strange things from a quick look, but I guess it's minor.
15:37
<jgraham>
Ms2ger: So, is it cheating the system if you mark the files in r/5 as reviewed as you update them, and someone else reviews your updates?
15:37
<jgraham>
(the answer is no: it is not)
15:38
<jgraham>
Otherwise we will ~never finish that review
15:38
<Ms2ger>
Mm
15:38
Ms2ger
wonders how to do that
15:40
<jgraham>
http://critic.hoppipolla.co.uk/6dda8721?review=5
15:40
<jgraham>
Put a tick by the files you have updated
15:40
<jgraham>
Press submit
15:41
<Ms2ger>
All I have under "Reviewed" is "pending"
15:44
<jgraham>
Hmm
15:44
<jgraham>
So
15:44
<jgraham>
For some reason it wasn't making you a reviewer of all the files
15:45
<jgraham>
But now I adjusted it it won't make you a reviewer of the files that you subsequently touched
15:45
<jgraham>
Which seems like a bug
15:46
<jgraham>
Give me a list of files and I will mark them as reviewed
15:49
<Ms2ger>
jgornick, elements-{embedded/forms/grouping}.js, so far
15:50
<jgraham>
OK, marked
15:50
<Ms2ger>
Ta
17:32
<gsnedders>
sangwhan: Opera/Presto is the only browser using OpenSSL.
17:33
<gsnedders>
sangwhan: Though perhaps Safari does via NSURL and OpenSSL at a system level?
18:07
<sangwhan>
gsnedders: Chromium does have a "use system SSL" feature which probably turns out using OpenSSL (although no idea how it works on Windows) - and yes, NSURL probably hits OpenSSL at some point.
18:09
<gsnedders>
sangwhan: Chrome uses NSS by default on Windows/Linux, definitely.
18:10
<gsnedders>
sangwhan: I believe it does on OS X as well.
18:10
<gsnedders>
sangwhan: But yes, I'm aware it has an option. :)
20:02
<gsnedders>
How many interfaces have (catch-all) named property setters?
20:04
<Ms2ger>
Setters, hmm...
20:04
<Ms2ger>
DOMStringMap?
20:07
<Hixie_>
ok, back to work!
20:07
<Hixie_>
18854
20:08
<gsnedders>
Ms2ger: only has setter creator void (DOMString name, DOMString value);
20:08
<gsnedders>
Ms2ger: So no.
20:08
<Ms2ger>
What do you mean, then?
20:09
<Hixie_>
(if there were any questions in the last few days, please ping me again or e-mail me, i was mostly afk and only occasionally popped my head in)
20:09
<gsnedders>
Ms2ger: setter void (DOMString name, DOMString value) is a catch-all. That setter only defines one for creator.
20:10
<Ms2ger>
'setter creator'
20:10
<gsnedders>
Am I misunderstanding the WebIDL spec?
20:11
<gsnedders>
(Entirely plausible.)
20:11
<Ms2ger>
I'm confused about what you're asking :)
20:11
<gsnedders>
Catch-all setters. Where do they exist in the platform?
20:11
<gsnedders>
DOMStringMap AIUI only defines a setter for the 'creator' property, not a catch-all.
20:12
<gsnedders>
I could simply be misunderstanding.
20:12
<Ms2ger>
setter creator void (DOMString name, DOMString value); is equivalent to
20:12
<Ms2ger>
setter void (DOMString name, DOMString value);
20:12
<Ms2ger>
creator void (DOMString name, DOMString value);
20:13
<gsnedders>
Oh, okay!
20:14
<Ms2ger>
Not exactly the most obvious syntax :)
20:17
<gsnedders>
No, not quite. :)
20:19
<Hixie_>
anyone have a suggestion for variable name for a variable that represents an <a> or <area> element?
20:19
<Hixie_>
so far i've considered element, a, anchor, link, source, victim
20:19
<Hixie_>
they all suck for various reasons
20:19
<Hixie_>
(i'm using /subject/ unless someone has a better idea)
20:51
<annevk>
Hixie_: <link href=/ target=_blank><style> head,link {display:block} link::before { content:"link" } </style>
20:51
<annevk>
Hixie_: works in Gecko
20:51
<annevk>
(as in creates a new browsing context)
21:12
<zcorpan>
annevk: but it doesn't work anywhere else and nobody does that kind of thing (i.e. show <link>s and expect users to click them)
21:16
<zcorpan>
though the spec maintains the <link> is a link story in other places
21:18
<Hixie_>
annevk: yes (i'm the one who filed the bug to make that work)
21:22
<zcorpan>
annevk: would you be opposed to removing <link> being clickable, matching :link, etc?
21:23
<annevk>
zcorpan: I don't care I think, but I think bz might
21:24
<annevk>
Hixie_: target="" is not valid in HTML at the moment for <link> though
21:28
<Hixie_>
annevk: so?
21:32
<blooberry>
/msg Hixie_ hey bachelorman 8-}