| 00:03 | <MikeSmith> | Hixie: help.whatwg.org is currently just the place where I run scripts that scrape the meta@name and link relation wikis to generate lists of registered keywords. I could move the scripts elsewhere if needed |
| 00:03 | <Hixie> | ah, cool |
| 00:03 | <Hixie> | no that's fine |
| 02:47 | <JonathanNeal> | Anyone here messed with the deviceorientation event and alpha/beta/gamma stuff? |
| 07:20 | <annevk> | zcorpan: did not review, did deploy |
| 07:20 | <annevk> | zcorpan: seems to look okay though |
| 07:20 | <zcorpan> | annevk: thx |
| 07:22 | <zcorpan> | i see Hixie already used background-size:cover so the spec's icons still have the right size |
| 07:23 | <annevk> | Oh is he hotlinking these now? |
| 07:23 | <annevk> | He is |
| 07:25 | <annevk> | zcorpan: they might need to be even bigger to cover these new x3 screens |
| 07:25 | <annevk> | zcorpan: also, can we do multiple images for background-image yet? I heard with icons you don't really want to downscale a high resolution icon, but provide your own low resolution |
| 07:26 | <annevk> | zcorpan: not sure if we should care for this use case though |
| 07:26 | <zcorpan> | annevk: i'm not convinced that it's ugly on 3x |
| 07:27 | <annevk> | Hmm, people are actually using my WebVTT validator: https://github.com/annevk/webvtt/issues/5 |
| 07:29 | <zcorpan> | annevk: are there browser icons that are 2x or 3x that are designed for 16x16 CSS pixels size? |
| 07:30 | <annevk> | zcorpan: no idea |
| 07:31 | <zcorpan> | https://github.com/alrra/browser-logos doesn't seem to have such a thing at least |
| 07:37 | <zcorpan> | i could have used the 16x16 icon in src and 32x32 in srcset but i don't really care about optimizing for 1x screens |
| 10:35 | <annevk> | Oh hey, the W3C imagined interoperability: http://www.w3.org/TR/2014/PR-html5-20140916/ |
| 10:36 | <annevk> | for jgraham: http://intertwingly.net/blog/2014/09/16/The-URL-Mess#c1410950300 |
| 10:37 | <smaug____> | PR requires interoperability |
| 10:37 | <smaug____> | ? |
| 10:38 | <annevk> | smaug____: exciting CR does |
| 10:38 | smaug____ | has so forgotten which *R requires what |
| 10:38 | <annevk> | oops, exiting |
| 10:41 | <jgraham> | "exciting" was better |
| 10:41 | <jgraham> | POssibly as it "it would be exciting if a spec in CR actually had interoperability" |
| 10:41 | <annevk> | heh |
| 10:42 | <caitp> | wouldn't it though? |
| 10:44 | <darobin> | I completely thought that "exciting" was on purpose :) |
| 11:04 | tantek | reads the blog post that annevk linked to |
| 11:05 | <tantek> | this: " It seems pretty clear at this point that IETF/IANA has a pretty poor track record when it comes to registries." |
| 11:15 | <annevk> | tantek: that's from the comments :p |
| 11:20 | <tantek> | annevke I know :) |
| 12:04 | <darobin> | don't get me started on IANA :) |
| 12:04 | darobin | just registered five media types with them |
| 13:58 | <annevk> | I don't understand why https://developer.mozilla.org/en-US/docs/Web/CSS/::selection was killed and ::first-line or ::first-letter was not |
| 14:01 | <annevk> | hsivonen: https://hsivonen.fi/extended-uncertainty/ example site went out of business |
| 14:03 | <zcorpan> | csswg decided to add back ::selection |
| 14:03 | <annevk> | can Gecko unprefix then? |
| 14:13 | <tantek> | darn I wanted to see a citation to re-adding ::selection |
| 14:14 | <tantek> | I remember some discussions about that... |
| 14:15 | <tantek> | annevk: current status of ::selection AFAIK is this issue: http://wiki.csswg.org/spec/css3-ui#issue-30 |
| 14:15 | <tantek> | which means it's yet another thing in my pile :/ |
| 15:42 | <Domenic> | spec.whatwg.org still dead? :( |
| 15:43 | <Hixie> | you can use https://whatwg.org/specs in the meantime |
| 15:43 | <Hixie> | it's the same file |
| 16:04 | <Domenic> | service worker without fetch? O_O |
| 16:18 | <annevk> | I feel sorry for slightlyoff_ if that happens |
| 16:19 | <annevk> | He was so adamant about offline being essential and a v0 feature |
| 16:20 | <annevk> | hsivonen: https://groups.google.com/d/msg/mozilla.dev.security.policy/RnAx-t-wOVU/dYjKJF4E7L8J |
| 16:22 | <jgraham> | Uh, what? |
| 16:23 | <jgraham> | I thought offline was the point of service worker and everything else was tacked on |
| 16:23 | <jgraham> | It certainly seems like the most pressing problem to solve |
| 16:29 | <annevk> | jgraham: see https://github.com/slightlyoff/ServiceWorker/issues/463 for context |
| 16:30 | <annevk> | Domenic: don't reply from your phone :p looks bad https://github.com/slightlyoff/ServiceWorker/issues/445#issuecomment-55918543 |
| 16:55 | <annevk> | That http://www.w3.org/TR/2014/CR-encoding-20140916/indexes/index-big5.txt does not have the correct encoding amuses me |
| 16:58 | <annevk> | Hixie: since pretty much all specs use dfn.js, perhaps it should move? Not sure I care strongly though |
| 17:18 | <Hixie> | annevk: i recommend copying dfn.js. i don't guarantee i won't change it arbitrarily to match what html needs. |
| 17:23 | <smaug____> | annevk: I was chatting with sicking yesterday, and sounds like we should have persistent and non-persistent notifications. And service worker should be supported too. Need to think about the API - it may end up being quite a bit different from what it is today. Luckily .get() is implemented in Gecko only |
| 17:59 | <annevk> | Hixie: okay |
| 18:00 | <annevk> | smaug____: okay, if you could do so within a couple of weeks that'd be great |
| 18:00 | <annevk> | smaug____: I'd like to update it to support service workers |
| 18:43 | <Domenic> | annevk: I or someone else can always edit out the cruft. |
| 19:35 | <Hixie> | so re our conversation yesterday about whether w3c's namespace redirect confuses people: |
| 19:35 | <Hixie> | http://www.hiphopcanada.com/tag/partynextdoor/ |
| 19:35 | <Hixie> | view-source:http://www.richbone.com/kansetsu/ill/ill.htm |
| 19:36 | <Hixie> | http://beheretowitness.com/seating-pricing/ |
| 19:36 | <Hixie> | there's lots of sites that have the wrong namespace |
| 19:36 | <Hixie> | and i wouldn't be surprised if it started from that redirect |
| 19:38 | <rubys> | annevk: ping? |
| 19:49 | <annevk> | rubys: if you leave a question I can get back to you within the next couple of hours most likely, only behind the laptop sporadically during the evening |
| 19:50 | <rubys> | I'll probably take it to the whatwg list. I'm looking to sketch out a "URL differences" document comparable to the "HTML differences" document; any pointers would be appreciated. |
| 19:50 | <rubys> | Meanwhile, I'm scanning the spec for likely candidates. |
| 19:51 | <rubys> | Will post a first draft when my scan is complete. |
| 19:54 | <annevk> | cool cool cool |
| 20:01 | <Domenic> | https://twitter.com/yaypie/status/512325679191322624 |
| 20:42 | <Hixie> | jamesr_: yt? |
| 20:42 | <Hixie> | jamesr_: does http://lists.w3.org/Archives/Public/www-dom/2014JulSep/0091.html still match your desires? |
| 20:43 | <Hixie> | jamesr_: and if so, should i assume that if i hook into https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/RequestAnimationFrame/Overview.html#processingmodel you'll update that spec to not longer involve a task but just to expose the algorithm? |
| 20:44 | <terinjokes> | Domenic: we resolved that problem by creating our own format and expecting everyone else to just use it |
| 21:08 | <annevk> | Interesting, per http://caniuse.com/#search=apng Safari on iOS 8 supports APNG |
| 21:26 | <jamesr_> | Hixie: that matches my desires, but i'm not sure that i've thought through all the consequences correctly |
| 21:29 | <Domenic> | annevk: yeah, I wonder if people will start using it on mobile and thus force Chrome to support it |
| 21:29 | <Domenic> | Then we would finally have a winner |
| 21:30 | <Domenic> | Although browsers have some catching up to do with http://geelen.github.io/x-gif/#/http://i.imgur.com/iKXH4E2.gif |
| 23:46 | <roc> | has anyone had a chat with L2L? |
