01:38
<MikeSmith>
w3c bugzilla has been updated to v5.0
01:38
<MikeSmith>
if anybody notices problems with it please lemme know
01:39
<MikeSmith>
biggest new feature appears to be ability to tag comments https://www.bugzilla.org/releases/5.0/release-notes.html#feat_comment_tags
01:42
<MikeSmith>
plus the "never email me about this bug" option
02:36
<jakesyl>
Hello, I'm working on a website and would like to make a login like this: https://accounts.google.com/ServiceLogin?hl=en&continue=https://www.google.com/#identifier (with the box) any idea how to do this?
02:47
<Yay295>
jakesyl: Do you mean you want to use a Google log-in, or do you want to log-in with your own accounts, but make it look like Google's?
02:51
<jakesyl>
make it look like googles
02:52
<Yay295>
What do you need help with? It's pretty much just a white box.
02:53
<jakesyl>
here's what I have so far: https://gist.github.com/jakesyl/7c81dc31640068068775 I'm working on this right now: https://jsfiddle.net/f780xcs3/ but nothings showing up
02:53
<jakesyl>
The canvas face thing
02:55
<Yay295>
Why are you using a canvas?
02:55
<jakesyl>
to make that face thing
02:57
<Yay295>
You don't need a canvas for that.
02:57
<jakesyl>
hmm, how do i do it then
02:57
<Yay295>
Try doing what Google did. "border-radius: 50%;"
02:59
<jakesyl>
for the....
03:00
<jakesyl>
oh cool!
03:01
<jakesyl>
so how do I make one overlay the other
03:02
<Yay295>
HTML is read top to bottom. Things declared after other things get put on top.
03:03
<Yay295>
You could also use the CSS 'z-index' property.
03:05
<jakesyl>
wait so on googles page what is this for: <canvas id="canvas" class="circle" width="96" height="96"></canvas>
03:07
<Yay295>
I don't see a canvas element when I visit that page. Google must be sending us slightly different pages for some reason.
03:09
<jakesyl>
hmm
04:26
<MikeSmith>
astearns: FYI https://twitter.com/sideshowbarker/status/623347810457358336
04:27
<MikeSmith>
astearns: I realize this isn't your department at all but any guidance or suggestions for who to talk with would be appreciated.
04:28
<astearns>
MikeSmith: I have a couple DW contacts, I'll see who I can send your way
04:28
<MikeSmith>
astearns: thanks, much appreciated
04:29
<MikeSmith>
astearns: Dunno if you know this feature but apparently Dreamweaver (CS6 at least; I don't user Dreamweaver and don't know about versions) has some feature where it will send a document to the (legacy) W3C Validator and some UI for displaying the results
04:30
<astearns>
ah, I didn't know. I've never been a DW user :)
04:30
<MikeSmith>
heh
04:31
<MikeSmith>
well what happened is, since last week, basically I'm taking all requests for HTML5 documents sent to the legacy validator and auto-redirecting them to the Nu HTML Checker https://validator.w3.org/nu/
04:31
<MikeSmith>
if DW is expecting the results in some format that's different from what I'm sending back now, I can try to have the Nu checker send it in that expected format
04:32
<astearns>
or we could update to the new address and format
04:32
<MikeSmith>
yeah I would prefer that
04:34
<astearns>
the 'creative cloud' aspect is supposed to make it easy to update things like this, but I expect there will be a legacy tail where we'd like the old format :)
04:37
<MikeSmith>
yeah
04:37
<MikeSmith>
I don't like breaking things that people depend on
04:38
<MikeSmith>
but on the other hand sometimes you can't know what will break until you break it
04:45
<astearns>
MikeSmith: I've blasted everyone I know on the DW team with your contact info and summary of the issue above
04:46
<MikeSmith>
astearns: coolマthanks much
05:21
<jakesyl>
is this a common error: http://imgur.com/G8THmEG and how do i fix it?
05:36
<Domenic>
Anyone have the email where Boris and annevk work out the custom elements callbacks attached/detached thing?
05:37
<Domenic>
Found it https://lists.w3.org/Archives/Public/public-webapps/2015AprJun/0517.html
08:19
<howdoi_>
gsnedders: Fixed it, so it lists out only the companies for now https://github.com/hemanth/tc39-members
08:19
<howdoi_>
thanks.
09:09
<Ms2ger>
bring back to life:
09:09
<Ms2ger>
XForms Working Group
09:19
<MikeSmith>
Ms2ger: yeah I encourage y'all to comment on that please
09:20
<MikeSmith>
as in, say No
09:21
<MikeSmith>
there was an XForms WG in plh's domain for years that was doing nothing and he tried to shut it down for a long time and finally succeeded
09:22
<Ms2ger>
I would suggest that, but it'll happen anyway, and most likely people will start wasting dbaron's time trying to get him to change his vote
09:22
<MikeSmith>
ok
09:23
<Ms2ger>
I have basically zero confidence in feedback like that being paid attention to
09:23
<MikeSmith>
oh it's paid attention to
09:23
<MikeSmith>
especially when I amplify it
09:24
<MikeSmith>
but if no AC reps speak up I have nothing to amplify
09:24
<MikeSmith>
I already stalled those charters from going out to the AC to begin with because I insisted that none of those groups be rechartered as Member-only
09:24
<jgraham>
Ms2ger: Oh, you mean outside people?
09:25
<MikeSmith>
originally at least
09:25
<jgraham>
MikeSmith: What is this, 1998?
09:25
<MikeSmith>
yeah, seriously
09:25
<Ms2ger>
jgraham, XML people
09:26
<MikeSmith>
at least make I do think it's worth making the comment "none of this should be going into
09:27
<MikeSmith>
* "none of this work should be getting done under any assumption that it will get implemented in browsers"
09:27
<jgraham>
I'm struggling to imagine anyone who works on Gecko arguing with "we have no intention of implementing XForms, and feel it's a distraction from the real and urgent needs of the web"
09:27
<MikeSmith>
which kinda should make anybody then ask why it's being done at the W3C at all, and that would be a very good question
09:27
<Ms2ger>
Yeah, dbaron already said that
09:28
<jgraham>
Ms2ger: Pointer?
09:28
<Ms2ger>
MikeSmith, last I checked, there was an oil industry group at w3c, so I doubt that says much :)
09:28
<Ms2ger>
"(My inclination is at minimum to explicitly abstain, with comments
09:28
<Ms2ger>
that they shouldn't expect browser implementation.)"
09:28
<Ms2ger>
On m.d.platform
09:28
<jgraham>
Oh, I ignored that because it said "XML Group activity", it seems
09:31
<MikeSmith>
these groups are basically just a kind of pollution at this point
09:32
<MikeSmith>
I wish more AC reps would say stuff like that rather than just not commenting at all or abstaining
09:32
<smaug____>
what is the reason to try to bring XForms back to life?
09:32
<MikeSmith>
smaug____: beacuse there are some diehards that want to keep working on it
09:33
<MikeSmith>
I think it's fine if they do, but that's what we have Community Groups for
09:33
<smaug____>
Pemberton + insurance companies ?
09:33
<Ms2ger>
Why not ECMA?
09:33
<MikeSmith>
I would love to gift the XForms stuff to ECMA
09:33
<MikeSmith>
or Oasis or somewhere
09:33
<Ms2ger>
How about xml core? :)
09:34
<MikeSmith>
zcorpan still gets some productive stuff done in xml core or somewhere
09:34
<MikeSmith>
but I don't know if he plans to keep doing that
09:34
<Ms2ger>
Really?
09:35
<MikeSmith>
he worked on the spec for the XML stylesheet processing instruction at least
09:35
<Ms2ger>
Yeah, but that was years ago, and they made him cut out half the spec, no?
09:36
<smaug____>
MikeSmith: does having a WG use more W3C's resources than a CG?
09:37
<jgraham>
smaug____: Seems like it must since they get f2f meetings including TPAC and so on
09:37
<jgraham>
and a contact?
09:37
<Ms2ger>
The proposed charters are requesting 85% fte altogether
09:38
<jgraham>
I guess if you're going to argue it like that though; it's possible that there are people that only join W3C to participate in XForms (I don't know if that's true)
09:40
<jgraham>
So I am going to suggest the problem is one of focus; the W3C should dedicate it's resources to leading the web to its full potential, and not work on things that are unrelated to that
09:40
<jgraham>
s/'//
09:40
<Ms2ger>
"The Working Group may, if needed, update XML Events 2 if needed"
09:40
<jgraham>
Ms2ger: Best to hedge your bets
09:40
<Ms2ger>
"the primary risk factor will be external attention and increased adoption leading to a longer review cycle than expected."
09:43
<Ms2ger>
The Working Group has current plans to:
09:43
<Ms2ger>
Publish a sixth edition of XML 1.0 as an Edited Recommendation, to include the changes for the LEIRI specification, at such time as IRI-bis is final.
09:48
<smaug____>
hmm, XML Events implementation was IIRC my first larger contribution to Gecko :p (I then removed it couple of years later)
09:50
<smaug____>
"couple" == 8
09:51
<MikeSmith>
smaug____: having a WG definitely consumes more of W3C resources than having a CG
09:52
<MikeSmith>
in theory if all of our staff were capable of moving into work in other areas, then shutting down work in non-priority WGs would free up staff to help with WGs that actually matter
09:53
<MikeSmith>
Ms2ger: "to include the changes for the LEIRI specification, at such time as IRI-bis is final" pretty much says it all
09:53
<MikeSmith>
writing their own parody there
09:54
<Ms2ger>
This is almost as bad as Obama implementing an article from the Onion
09:58
<MikeSmith>
it's not quite as bad as the "Golden Key for Governments to Unlock Any Encryption" WG charter we'll sending out for AC review soon
10:00
<Ms2ger>
What's next, the "solve the halting problem" CG?
10:03
<MikeSmith>
that's the spirit
10:03
<MikeSmith>
optimism
10:10
jgraham
notes that gold is a soft metal that's therefore entirely unsuitable for making keys
12:35
<gsnedders>
jgraham: https://github.com/html5lib/html5lib-python/pull/198 would be nice to land sooner rather than later, FWIW
12:36
<gsnedders>
jgraham: as it allows us to keep up-to-date with tests without having unexpected failures
12:37
<gsnedders>
except it looks increasingly like there's more needed to get it to work, bah
12:52
<jgraham>
gsnedders: No critic review?
13:07
<gsnedders>
jgraham: no, doesn't appear to have picked it up
13:11
<gsnedders>
(FWIW, the remaining Travis failures are bugs in pytest-expect)
13:22
<gsnedders>
Basically need some way to serialise a set of a mixture of bytes and unicode, across both Py2 and Py3
13:25
<gsnedders>
(pickle on Py2 doesn't support the more recent protocols which sanely cope)
13:32
<webzen>
hi
14:28
<webzen>
Should my imports also end up in document ready ? http://laravel.io/bin/9v6rM