01:41
<MikeSmith>
Domenic_: yeah got it figured out
09:05
<zcorpan>
MikeSmith: are your changes online?
09:48
<annevk>
jgraham: final paragraph of http://en.wikipedia.org/wiki/Quantum_computer#Developments
09:56
<jgraham>
annevk: I note that is all in the future tense, and slightly before that it says "In November 2011, researchers factorised 143"
10:01
<Ms2ger>
jgraham, r? https://critic.hoppipolla.co.uk/r/31 :)
10:06
<jgraham>
r+ :)
10:07
<Ms2ger>
Woo :)
10:08
<Ms2ger>
Almost managed to get it done in six months :)
10:12
<annevk>
jgraham: you said 15, so... but yeah
10:13
<Ms2ger>
(I have to admit that I found the sessions at the summit more interesting than this class)
10:18
<jgraham>
Ms2ger: UML? :)
10:18
<Ms2ger>
I managed to avoid that :)
10:18
<Ms2ger>
Machine learning
15:14
<rtc>
is it ok if I put div inside h2?
15:30
<annevk>
rtc: no
15:31
<rtc>
annevk, does it matter css properties of the elements with their position on html
15:31
<annevk>
I can't parse that question
15:31
<rtc>
so let's say if I make div inline element with css, can I put it in another inlin element then? is this ok?
15:32
<rtc>
sorry about my english, it's little bad :)
15:33
<annevk>
rtc: CSS doesn't affect semantics
15:33
<annevk>
rtc: so no
15:34
<rtc>
ok
15:34
<rtc>
it is strange
15:34
<rtc>
you guys need to work
15:34
<rtc>
on some thins, honestly
15:34
<annevk>
it's not strange at all, CSS is optional, HTML should make sense without CSS
15:35
<rtc>
annevk, this is me speaking because I have to change about 30 elements structure now -_-
15:35
<rtc>
coz I have put divs inside h2 :)
15:35
<rtc>
hehe good work so far
15:35
<rtc>
keep up the good work! and respect hixie
15:36
<rtc>
annevk, I have put 30 divs inside h2 why you made html so divs can't go in h2 :S
15:36
<rtc>
:D
15:50
<rtc>
annevk, I truly admire Timothy and his team
15:50
<annevk>
rtc: not sure who that is
15:50
<rtc>
his mission/vision and all who work on the project keep up the good work guys!
15:51
<rtc>
he will go where nikola tesla einstein newton platon aristotle pitagora are
15:53
<rtc>
annevk, can I ask you question about your personal info?
15:54
<rtc>
mor exactly where you work besides whatwg
15:55
<annevk>
rtc: http://annevankesteren.nl/about
15:57
<rtc>
thanks!
15:58
<rtc>
annevk, lets start a company
15:59
<rtc>
annevk, you look like a nice guy from the image :) hehe
15:59
<rtc>
look
15:59
<rtc>
seriouslly please decrease the size of the fonts!
15:59
<rtc>
they are too big
15:59
<rtc>
and dcrease everything and finally!
15:59
<rtc>
please remove top bad please
16:00
<rtc>
so I don't think internet explorer is better than firefox :S
16:00
<rtc>
they finally starting to work on the things with ie11 adopting webgl
16:00
<rtc>
on my total surprise
16:02
<rtc>
annevk, sorry but im honest :|
16:02
<rtc>
lately I feel firefox is left behind
16:02
<rtc>
please work on this
16:02
<rtc>
3d preview is awesome
16:02
<rtc>
I always show my students that :)
16:03
<rtc>
they are simply amazed asking me how I made it, well I should give credits to you hehe
16:03
<rtc>
mdn site is awesome too thanks for making that, just remove the top bar from firefox and decrease fonts pls
16:04
<rtc>
and do something with google guys to make browsers simialr
16:05
<rtc>
annevk, yo udo 3d visualization?
16:16
<rtc>
annevk, should we change our html code in 2020 to html5?
16:17
<rtc>
because how things are going, people stil lsupporting ie6 it looks like 2020 will be target for html5 because people still will support ie 8
17:27
<dglazkov>
good morning, Whatwg!
18:28
<rtc>
can I put block element inside inline-block element?
18:29
<Ms2ger>
Sure
18:35
<rtc>
Ms2ger, thanks
20:00
<annevk>
Does anyone happen to know if iOS carrier setting updates overwrite existing iOS carrier settings or whether it stores them all side by side?
21:41
<Domenic_>
Is ServiceWorker still the current name?
21:44
<annevk>
yws
21:50
<zcorpan>
maybe rename it at LC?
21:51
<Domenic_>
i too thought it meant prostitute but google says it just means waiter or similar. *shrug*
22:32
<TabAtkins>
What sort of verbage would be appropriate to refer to a trusted event which is appropriate for "activating"? Things like clicks and keyboard presses, but not mousemove events.
22:33
<TabAtkins>
Is there already a term for that?
22:35
<Hixie_>
TabAtkins: 'click'? :-)
22:35
<Hixie_>
TabAtkins: keyboard presses fire a click event before they trigger activation behaviours
22:36
<zewt>
keyboard events can trigger only-during-click stuff, even if there's no associated click, right?
22:36
<zewt>
(seems like they should, at least)
22:36
<TabAtkins>
Hm, maybe. Context is fullscreen and stuff - asking for Vincent. He's currently referring to something wk specific called "user gesture" which means "the subset of events that represent the user actually doing something".
22:36
<TabAtkins>
It might just be "click".
22:37
<zewt>
eg. you should be able to listen for key events to fullscreen if the user presses alt-enter, even if there's nothing to activate (or if you cancel the keypress event so you don't activate something unintentionally)
22:38
<TabAtkins>
zewt: Exactly.
22:38
<scheib>
Thanks for asking TabAtkins, I'm back at desk.
22:38
<rektide>
q: is there a specification where i can ask a webserver for a non-minified version of a page, a human readable please version?
22:38
<scheib>
Yes, and for pointer lock. Other events could be voice actions, or taps on touch screens. So.... these are all 'click'?
22:40
<zewt>
right: click is not what you want, and I'm not sure if there's any spec for this stuff
22:43
<rektide>
for some reason i thought there was some incipent view-source movement that had proposed a hook asking for "human friendly" assets, but i haven't found any links to anything except the view-source:// uri, http://tools.ietf.org/html/draft-yevstifeyev-view-source-uri-01#page-2
22:44
<rektide>
which will open up the unspeakable compiled horrors no human will be able to read
22:45
<TabAtkins>
rektide: To the best of my knowledge, no. You may be thinking of humans.txt, which is unrelated.
22:45
<Hixie_>
rektide: http, but you have to know the URL of the non-minified version :-)
22:45
<Hixie_>
TabAtkins: sounds like you want something consistent with what is considered a gesture for the purposes of popup blocking
22:45
<TabAtkins>
Hixie_: Yes, exactly that.
22:45
<rektide>
righto, yeah. perhaps a misuse of Nottingham's alternative service might be permissible here
22:46
<rektide>
spdy-human
22:46
<rektide>
quick-human
22:46
<barnabywalters>
rektide: http://daneden.me/max-css/ comes to mind
22:46
<rektide>
quik-human even. alterantive transports, i need you
22:46
<rektide>
yes, your asset compiler is part of your transport
22:46
<rektide>
don't dare disagree with me, you mangling serializing toolchain
22:47
<rektide>
barnabywalters: yup, that's perfect.
22:47
<rektide>
i'm alas not well versed on source maps, what role they might play.
22:51
<Hixie_>
TabAtkins: http://www.whatwg.org/specs/web-apps/current-work/#allowed-to-show-a-popup may be helpful
22:53
<TabAtkins>
Hixie_: I'd have to chase definitions, so I'll just ask you instead - would that work to, say, allow fullscreening when the user presses alt+Enter?
23:03
<Hixie_>
TabAtkins: probably not, i don't see key events in that list
23:03
<Hixie_>
TabAtkins: (maybe it's not exactly the same as popup blocking)
23:03
<Hixie_>
TabAtkins: but it may give you a starting point for a list of events
23:04
<TabAtkins>
Hixie_: Okay, I was wondering if those were subsumed under that "click" entry.
23:04
<Hixie_>
i don't think so
23:04
<Hixie_>
that only happens when you e.g. click space on a button
23:04
<TabAtkins>
That's what I thought.
23:04
<TabAtkins>
scheib: ^^^ You can just copy that list and add the additional events you need.
23:05
<scheib>
Hixie_ Tab is asking on my behalf. I'm particularly asking about pointer lock -- but it should match fullscreen. My reading of allowed-to-show-a-popup shows it to be mostly right. I can see adding to a white list of events. I do notice that http://fullscreen.spec.whatwg.org/ seems to only refer to allow a popup.
23:05
<scheib>
Thanks, for looking, by the way.
23:07
<scheib>
A whitelist is unfortunate, it precludes future unknown but equivalently intended events. I'll try to capture that somehow.
23:11
<zewt>
doesn't prevent it, you just add to the list