| 01:14 | <smaug____> | rbyers: ping |
| 02:12 | <rbyers> | smaug____: yes? |
| 02:32 | <smaug____> | rbyers: it was about fullscreen API |
| 02:33 | <smaug____> | I guess xidorn will send some information about the issues in unprefixing |
| 02:33 | <smaug____> | rbyers: are you perhaps aware of the situation at all? and do you know if blink was willing to try to unprefix? |
| 02:33 | <smaug____> | (it would help a ton if most of the browser vendors unprefixed around the same time) |
| 02:34 | <rbyers> | We want to yes, but there are some nasty problems to fix first. It's on our layout team's list but may not happen anytime soon unfortunately. |
| 02:35 | <rbyers> | I'm trying to see if I can get it funded from just the interoperability perspective too, so I'm hopeful. |
| 02:35 | <rbyers> | Edge also wants us to do it... |
| 02:39 | <smaug____> | rbyers: yes, this is related to the Edge stuff |
| 02:43 | <smaug____> | annevk: has there been more talk about hiding APIs in certain contexts |
| 05:52 | <annevk> | smaug____: only secure contexts |
| 05:52 | <annevk> | smaug____: seems like that is still the plan |
| 05:55 | <smaug____> | annevk: this came up in a discussion about Presentation API which should be somehow disabled (not defined how in the spec) in sandboxed iframes by default |
| 05:56 | <smaug____> | and the question was whether to hide the API or make getters to return null and some ctors to throw |
| 05:56 | <smaug____> | (restarting) |
| 06:03 | <annevk> | smaug____: hmm |
| 06:03 | <annevk> | smaug____: typically we use sandboxing for that |
| 06:04 | <smaug____> | for what? |
| 06:04 | <annevk> | smaug____: or what fullscreen uses |
| 06:04 | <annevk> | smaug____: disabling things in certain browsing contexts |
| 06:04 | <smaug____> | annevk: sure, that is what Presentation API does |
| 06:05 | <smaug____> | the question is how to disable features |
| 06:05 | <annevk> | smaug____: throw I suppose |
| 06:05 | <smaug____> | like, hiding the API in the sandboxed iframe or making the getters return null or throwing or making methods no-ops or what |
| 06:05 | <smaug____> | so, no hiding in this case I guess |
| 06:06 | <smaug____> | yeah, for now the plan is to make the getter return null and a ctor to throw |
| 06:06 | <annevk> | smaug____: yeah, seems like something we might provide optin for too |
| 08:13 | <MikeSmith> | the editors of the Payment Request API have been recently getting issues resolved that were blocking implementors |
| 08:13 | <MikeSmith> | so the spec is moving along well and I encourage anybody and everybody here to please scrutinize it |
| 08:13 | <MikeSmith> | https://w3c.github.io/browser-payment-api/specs/paymentrequest.html |
| 08:14 | <MikeSmith> | and if you find problems, please file issues https://github.com/w3c/browser-payment-api/issues |
| 08:18 | <annevk> | Anyone have 5min to review a blog post for me? |
| 08:19 | <MikeSmith> | annevk: I can |
| 08:19 | <MikeSmith> | as long as it’s not something too esoteric |
| 08:20 | <annevk> | maybe a little bit esoteric |
| 08:20 | <annevk> | definitely considering the entire world population |
| 08:25 | <MikeSmith> | heh, well by the definition everything we do here is very esoteric |
| 12:16 | <annevk> | So components for HTML has been dabbled around for nearly two decades |
| 12:18 | <MikeSmith> | annevk: yeah? |
| 12:18 | <annevk> | MikeSmith: https://www.w3.org/TR/NOTE-HTMLComponents is from 98 |
| 12:19 | <annevk> | MikeSmith: I'm feeling inspired to write another short blog post, since I can't quite concentrate on editing standards today |
| 12:24 | <MikeSmith> | if you write it I will be happy to review it |
| 12:29 | <MikeSmith> | annevk: I wonder if https://www.w3.org/TR/NOTE-HTMLComponents was based on the IE “Behaviors” thing, or whether it predates that |
| 12:31 | MikeSmith | finds https://msdn.microsoft.com/en-us/library/ms532146(v=vs.85).aspx |
| 12:32 | <MikeSmith> | “Using HTML Components to Implement DHTML Behaviors in Script” |
| 13:41 | <MikeSmith> | .win 33 |
| 13:41 | <MikeSmith> | oofs |
| 13:44 | <annevk> | So if I want a better mobile experience for my site, I need to use <meta content="width=device-width, initial-scale=1, shrink-to-fit=no" name=viewport> to this day? |
| 13:44 | <annevk> | This is so sad |
| 13:45 | <Ms2ger> | Very |
| 13:49 | <MikeSmith> | I think it is not just “to this day” but instead we are now stuck with it forever |
| 13:50 | <caitp> | surely there's a betterw ay |
| 13:53 | <MikeSmith> | there was before Apple unilaterally minted that |
| 13:53 | <MikeSmith> | but too late now |
| 13:56 | <annevk> | Also, designing for mobile is hard, I kinda want the <h1> to become part of the <nav> but ... |
| 13:56 | <annevk> | I guess this is what you deserve when you've been neglecting CSS for a while |
| 14:17 | <zcorpan> | MikeSmith: https://github.com/validator/validator/pull/286 |
| 14:17 | <MikeSmith> | zcorpan: yup, thanks, will try to get that changed this weekend |
| 14:18 | <zcorpan> | MikeSmith: cool, no rush, just thought i'd drop it here in case you were flooded with github notifications :-) |
| 14:21 | <MikeSmith> | well I am always flooded with github notifications so yeah I appreciate it |
| 14:54 | <wanderview> | Domenic: would you be ok if I changed some "let" variables in for of loops to "var"s in the stream tests? its not actually something that works well in firefox now and prevents me from really running the tests to work on streams |
| 14:54 | <wanderview> | https://bugzilla.mozilla.org/show_bug.cgi?id=1268812 |
| 14:54 | <wanderview> | obviously we need to fix that, but it seems its not the focus of these tests |
| 15:03 | <Ms2ger> | wanderview, since they're in wpt now, I'm going to claim I can r+ that, so go for it :) |
| 15:03 | <wanderview> | Ms2ger: I'm going to wait a bit since its not blocking me quite yet... but will probably do it in next couple weeks |
| 15:03 | <wanderview> | just wanted to get Domenic's opinion since its not a pressing issue yet |
| 15:04 | <wanderview> | thats assuming people don't bring me more service worker bustage :-( |
| 16:05 | <Domenic> | wanderview: sure, I guess. Sad that even in nightly you guys are behind on fairly basic ES6 stuff... Just be sure it doesn't change the semantics, as changing let to var often does, especially in loops with closures. |
| 16:06 | <Ms2ger> | Turns out `let` is hard |
| 16:06 | <Ms2ger> | Even harder if you had it before it was cool, and then it changed |
| 16:10 | <annevk> | So I tried to use this name=viewport thing and added a stylesheet, but it still looks bogus in Safari |
| 16:11 | <Domenic> | annevk: cross origin objects blog post! |
| 16:11 | <annevk> | yeah should do that |
| 16:12 | <Domenic> | let's keep a good cadence on blog.whatwg.org |
| 16:12 | <annevk> | Desktop Safari is fine though meeh |
| 16:22 | <caitp> | in your view, 10 years from now, is web development going to be more streamlined than it is now |
| 16:22 | <caitp> | or is it going to be even more of a mess |
| 16:25 | <annevk> | Firefox for iOS renders something I expect, Safari for iOS does not... |
| 16:27 | <MikeSmith> | botie, inform zcorpan label[form] change pushed to https://checker.html5.org/ with some additional fixups https://github.com/validator/validator/commit/4bdaa25fb95ed23b2fbcf97b79207db7afbc6303 |
| 16:28 | <nox> | annevk: That sounds wonderful. |
| 16:28 | <annevk> | nox: you'd think that after 9 years of iPhone this would be easy |
| 16:29 | <nox> | Especially with them using the same engine, right? |
| 16:30 | <annevk> | nox: I guess WebView is a bit different from Safari here |
| 16:30 | <annevk> | UIWebView? |
| 16:31 | <annevk> | Also, there's a weird horizontal scrollbar |
| 16:33 | <caitp> | you know if you asked about it on twitter someone would tell you in a short timespan exactly how to fix it |
| 16:33 | <caitp> | ...maybe |
| 16:35 | <annevk> | Yeah, last resort |
| 16:38 | <annevk> | Okay, so Safari is affected by overflow somehow |
| 16:38 | <annevk> | If you have overflow, it'll rescale the page |
| 16:38 | <annevk> | UIWebView does not do this |
| 16:39 | <MikeSmith> | botie, inform zcorpan label[form] change pushed to https://checker.html5.org/ with some additional fixups https://github.com/validator/validator/commit/4bdaa25fb95ed23b2fbcf97b79207db7afbc6303 |
| 16:39 | <botie> | will do |
| 16:43 | <annevk> | caitp: https://twitter.com/annevk/status/726089939725766656 answer away 😃 |
| 16:43 | <caitp> | I said someone would, I didn't say I had a clue about it :x |
| 16:44 | <annevk> | caitp: as for your question earlier, I have no idea |
| 16:44 | <annevk> | caitp: I tend to think it gets better over time, but the transitional period of new technology is always painful |
| 16:46 | <Domenic> | annevk: there's some flag for this, hold on... |
| 16:46 | <Domenic> | annevk: <meta content="width=device-width, initial-scale=1, shrink-to-fit=no" name="viewport"> |
| 16:46 | <Domenic> | shrink-to-fit=no being the key I think |
| 16:46 | <annevk> | Domenic: my site uses that |
| 16:49 | <annevk> | Oooh maybe something got incorrectly cached, it seems to work now |
| 16:53 | <caitp> | it seems like the transitional period for new tech never really ends, though |
| 16:54 | <annevk> | Maybe, but there's lots of features that are more than usable without requiring hacks |
| 17:07 | <Domenic> | let's see how it looks on Firefox Android |
| 17:08 | <Domenic> | Isn't it time to update the "URLs suck" though |
| 17:08 | <Domenic> | hmm ok kind of works on mobile |
| 17:08 | <Domenic> | the sidebar should really be hidden ideally |
| 17:08 | <Domenic> | or turned into a footer |
| 17:08 | <Domenic> | but, write a cross origin objects blog post instead of tweaking your CSS :P |
| 17:10 | <Domenic> | https://usercontent.irccloud-cdn.com/file/hsMjGda9/Screenshot_20160429-131111.png |
| 17:11 | <Domenic> | woah it looks great on chrome mobile |
| 17:11 | <Domenic> | except if you scroll left there's a lot of purple for no clear reason |
| 17:25 | <annevk> | Domenic: isn't the sidebar hidden on mobile? |
| 17:25 | <Domenic> | annevk: not in Firefox, yes in Chrome |
| 17:26 | <Domenic> | probably worth filing a bug on Firefox |
| 17:26 | <annevk> | Domenic: I wonder why all these browsers work differently |
| 17:26 | <annevk> | Domenic: the lots of purple is because of an overflowing <pre> |
| 17:27 | <annevk> | Maybe Firefox has the CSS cached? |
| 17:27 | <wanderview> | Domenic: the sidebar on anne's site is hidden on my firefox for android... |
| 17:27 | <Domenic> | Hmmmm |
| 17:27 | <Domenic> | Is there a force reload on mobile FF? |
| 17:27 | <Domenic> | Ah yep! |
| 17:27 | <Domenic> | Good now |
| 17:28 | <Domenic> | You just have to actually reload instead of just pressing enter on the URL bar again |
| 17:29 | <annevk> | Thanks for checking on Android 😃 |
| 17:33 | <botie> | zcorpan, at 2016-04-29 16:41 UTC, MikeSmith said: label[form] change pushed to https://checker.html5.org/ with some additional fixups https://github.com/validator/validator/commit/4bdaa25fb95ed23b2fbcf97b79207db7afbc6303 |
| 17:34 | <MikeSmith> | zcorpan: thanks for the PR! |
| 22:27 | <rniwa> | annevk: yt? |
