| 00:01 | <rniwa> | kochi: yt? |
| 00:01 | <rniwa> | hayato: ping |
| 00:14 | <MikeSmith> | https://github.com/w3c/browser-payment-api/issues/307#issuecomment-265511874 |
| 00:14 | <MikeSmith> | “I'd like to think that the implementation follows the spirit of the spec.” |
| 01:06 | <rniwa> | annevk: yt? |
| 01:07 | <rniwa> | Domenic: yt? |
| 01:11 | <annevk> | rniwa: sorta |
| 01:11 | <rniwa> | annevk: do you recall know why fullscreenElement: https://fullscreen.spec.whatwg.org/#dom-document-fullscreenelement |
| 01:11 | <rniwa> | annevk: needs to check whether candidate & context object are in the same tree after retargeting the lement? |
| 01:11 | <rniwa> | that seems odd because retargeting should guarantee that |
| 01:12 | <rniwa> | oh I guess it's not necessary true if the retargeted node is in another shadow tree... |
| 01:12 | <rniwa> | wait, retargeting should fix that |
| 01:13 | <rniwa> | oh, i guess if we called fullscreenElement on a shadow tree and fullscreenElement is in the document, we'd hit this... |
| 01:14 | <annevk> | rniwa: sounds plausible, foolip and kochi might know more |
| 01:32 | <Domenic> | rniwa: annevk: does sound like worth adding an example to the spec for |
| 01:39 | <annevk> | Yeah, makes sense |
| 01:40 | <annevk> | Is there a combined term for the GET and HEAD methods? |
| 02:34 | <rniwa> | Domenic, annevk: an example for what? |
| 02:34 | <annevk> | rniwa: the fullscreenElement thing you mentioned |
| 02:34 | <rniwa> | ah, I see |
| 02:56 | <Ms2ger> | slightlyoff, here? |
| 02:59 | <slightlyoff> | Ish. Whaddup? |
| 03:00 | <Ms2ger> | slightlyoff, I'm failing to make sense of the definition of origin in https://w3c.github.io/ServiceWorker/#run-service-worker |
| 03:02 | <slightlyoff> | Send mail? On Indian 2G, won't be able to answer quickly |
| 03:03 | <Ms2ger> | Oh, okay |
| 03:03 | <Ms2ger> | Thanks anyway :) |
| 06:22 | <rniwa> | annevk, hayato : should fullscreenchange be composed? |
| 06:22 | <rniwa> | oh, I guess this fires on document so no need |
| 06:40 | <rniwa> | annevk, hayato: on the other hand, that seems to indicate that we should be firing these events on shadow root as well... |
| 06:40 | <rniwa> | otherwise we get into a weird situation where in order to listen to a fullscreen state change, you need to attach your event listener to document |
| 06:49 | rniwa | filed https://github.com/w3c/webcomponents/issues/614 |
| 07:55 | <salty-horse> | how can I compile the "source" file into HTML? is the post-processor proprietary and therefore not provided? |
| 08:01 | <JakeA> | Ms2ger: we could probably replace that with the script's origin. Is that what you mean? |
| 08:07 | <MikeSmith> | salty-horse: https://github.com/whatwg/html-build/ |
| 08:08 | <salty-horse> | MikeSmith, thanks. I looked in README instead of CONTRIBUTING. |
| 08:08 | <MikeSmith> | ah |
| 08:09 | <MikeSmith> | hmm yeah we used to have that info in teh README but we moved it to CONTRIBUTING a few months ago |
| 08:09 | <MikeSmith> | because of the fact CONTRIBUTING is what the GH issue tracker auto-links to |
| 08:10 | <MikeSmith> | but it seems we should maybe mention it in the README still as well |
| 08:10 | <salty-horse> | is it ok if my fix breaks the 100 column width rule? (I have to, to prevent any newlines from appearing in the output) |
| 08:10 | <MikeSmith> | yeah it is OK |
| 08:10 | <MikeSmith> | if there is a reason for it |
| 08:11 | <MikeSmith> | that 100 column width rule is not a hard requirement for the processor or anything |
| 08:11 | <MikeSmith> | it is just a policy, style rule |
| 08:12 | <MikeSmith> | salty-horse: if you have any problems with the build please report them |
| 08:12 | <salty-horse> | trying.. |
| 08:12 | <MikeSmith> | even if they are just frustrations and not show stoppers |
| 08:12 | <MikeSmith> | we have tried hard to make the build as easy to use as possible |
| 08:13 | <MikeSmith> | but I think it probably still has a lot of room for improvement |
| 08:17 | <salty-horse> | MikeSmith, have you considered making "html-build" a git submodule of "html"? I don't see a reason why I would want one and not the other |
| 08:41 | <MikeSmith> | We have but decided intentionally to not make it a submodule |
| 08:42 | <MikeSmith> | because submodules are one of those "now you have two problems" things |
| 08:50 | <MikeSmith> | salty-horse: https://github.com/whatwg/html/pull/2151 |
| 08:52 | <salty-horse> | MikeSmith, looks good! |
| 08:54 | <kochi> | rniwa: sorry for being late, I was busy for other things today. As you may have understood, the "retargeting" algorithm does not guarantee that the context object and the retargeted node is in the same node tree. The "retargeting" algorithm was originally for event retargeting, but as most part can be reused, the algorithm is used for fullscreenElement. |
| 08:55 | <MikeSmith> | salty-horse: so actually waht we normally do for cases like that line is wrap the “ data-x="dom-context-2d-imageSmoothingQuality-low">low</code>".</p>” part to the next line |
| 08:55 | <kochi> | rniwa: also pointerLockElement uses the retargeting algorithm. https://w3c.github.io/pointerlock/#dom-documentorshadowroot-pointerlockelement |
| 08:55 | <MikeSmith> | salty-horse: that is, break it before the attribute name |
| 08:55 | <kochi> | Looks like Safari TP supports PointerLock!! http://caniuse.com/#search=pointerlock |
| 08:56 | <salty-horse> | hmm ok. yes the docs mentioned it, but I thought this was more readable. |
| 08:57 | <MikeSmith> | yeah we do it even if it is less reabable |
| 08:57 | <rniwa> | kochi: it looks like fullscreenchange event is still broken: https://github.com/w3c/webcomponents/issues/614 |
| 08:57 | <rniwa> | kochi: as things stand, you have to listen to the event on document level if one of the elements in a shadow tree is full screen'ed |
| 08:57 | <MikeSmith> | salty-horse: actually it is more that we go with whatever our text editors do when given a 100-column limite |
| 08:59 | <salty-horse> | fixing nw |
| 09:00 | rniwa | sigh... one of these days, i'd go home before midnight |
| 11:29 | <ondras> | so, is there an "official" way of making html/css tables with a fixed header and a scrollable body? |
| 11:30 | <boogyman> | This isn't really a support channel, but what do you mean by "official" |
| 11:31 | <zcorpan> | where does webidl say to "perform a security check" for constructors? or does it not? heycam|away tobie annevk Domenic - context https://github.com/w3c/browser-payment-api/issues/361#issuecomment-265719019 |
| 11:41 | <ondras> | boogyman: such as "there is a dedicated attribute for this" or "the <tbody> cannot really overflow, so you need to use display:block or wrap it" ... something more worthy than a random crappy SO search |
| 11:42 | <ondras> | no looking for a solution to be copypasted. looking for a right direction (or a statement about no direction being available at all) |
| 11:46 | <boogyman> | position: fixed is the most likely, but I have not tried to use it in the context of <table><thead>...<tbody> |
| 11:46 | <ondras> | okay, thanks |
| 12:19 | <tobie> | zcorpan: afaik it doesn't |
| 12:19 | <tobie> | zcorpan: see: https://heycam.github.io/webidl/#es-constructible-interfaces |
| 12:21 | <zcorpan> | tobie: shouldn't it, somewhere before step 6? |
| 12:21 | <tobie> | zcorpan: instantiation being neither done by an operation nor a getter/setter, we'd need to modify https://heycam.github.io/webidl/#dfn-perform-a-security-check |
| 12:23 | <tobie> | zcorpan: it seems like a reasonable thing to do, but I'm no authority in this topic. Can you file a ticket? |
| 12:25 | <zcorpan> | sure |
| 12:28 | <zcorpan> | filed https://github.com/heycam/webidl/issues/249 |
| 12:38 | <tobie> | zcorpan: ty |
| 12:40 | <zcorpan> | ondras: afaik, that is still an unsolved issue in css, but display:block "works" |
| 12:40 | <ondras> | zcorpan: I would say that display:block totally f*cks up the width computation of the tbody cells, so having absolutely positioned <thead> might work better. gave it only a rough try though. |
| 12:41 | <ondras> | zcorpan: https://jsfiddle.net/zo1tg7L7/1/ |
| 12:41 | <zcorpan> | ondras: yeah maybe positioning the thead is less painful |
| 12:41 | <ondras> | (but still painful) |
| 12:42 | <zcorpan> | you'd need to display:block the thead as well, and then specify widths for the cells so they hopefully line up |
| 12:43 | <ondras> | zcorpan: I would like to retain the automatic column width computation algorithm |
| 12:44 | ondras | thinking about the css grid for this particular case... |
| 13:01 | <tobie> | zcorpan: isn't the security check done by step 9 (Assert: O.[[Realm]] is equal to F.[[Realm]])? |
| 13:04 | <zcorpan> | tobie: no? that happens after the constructor's algorithm has run (step 6), and isn't "Assert" meant for things that should be impossible to be false if the spec is implemented correctly? |
| 13:05 | <zcorpan> | i.e. strictly non-normative |
| 13:05 | <tobie> | zcorpan: yeah, you're right on both counts. |
| 13:15 | <tobie> | MikeSmith, JakeA: sorry forgot to get back to you this morning. I unfortunately don't have a good answer to this. TabAtkins might have this data ("Is there a way to find all the specs that depend on fetch") from shepherd. |
| 13:15 | <MikeSmith> | tobie: OK |
| 13:16 | MikeSmith | watches hot potato get passed to TabAtkins |
| 13:17 | <tobie> | MikeSmith: I do have a bunch of code written specifically to get this data out, but the project was put on the back burner, unfortunately. |
| 13:18 | <MikeSmith> | ah yeah |
| 13:18 | <MikeSmith> | I thought you had done some work back some time ago |
| 13:18 | <MikeSmith> | so my memory is not as bad as I imagined |
| 13:20 | <zcorpan> | iirc shepherd doesn't know which specs reference which. i needed this when switching html to en-US but ended up greping various repos and googling |
| 13:22 | <zcorpan> | So... "secure context" cannot change during the lifetime of a document, correct? |
| 13:22 | <MikeSmith> | TabAtkins just needs to write a replacement for shepherd |
| 13:23 | <MikeSmith> | zcorpan: dunno the answer but you thinking about that in the context of future-proofing “allowed to use” for Feature Policy compat? |
| 13:24 | <zcorpan> | MikeSmith: that is related yeah. i'm trying to wrap my head around how these things work. |
| 13:25 | <zcorpan> | MikeSmith: i found [SecureContext] in webidl means the thing is not exposed at all in non-secure contexts, but that's not how it's implemented in chromium for PaymentRequest at least |
| 13:26 | <zcorpan> | instead it throws early in the constructor https://chromium.googlesource.com/chromium/src/+blame/master/third_party/WebKit/Source/modules/payments/PaymentRequest.cpp#682 |
| 13:32 | <MikeSmith> | zcorpan: I guess I have ceased being surprised by cases where blink+chromium+v8 doesn’t conform to webidl |
| 13:32 | <MikeSmith> | seems to be the rule rather than the exception |
| 13:33 | <MikeSmith> | well that’s overstating things but… it’s frustrating |
| 13:35 | <MikeSmith> | especially when I take time to report it and end up getting ’splained to, that well actually, the blink+chromium+v8 is right and wontfix |
| 14:17 | <felixjet> | Figure Content model: |
| 14:17 | <felixjet> | Either: One figcaption element followed by flow content. |
| 14:17 | <felixjet> | Or: Flow content followed by one figcaption element. |
| 14:17 | <felixjet> | flow content... but can be more than 1? |
| 14:17 | <felixjet> | like <figure><figcaption></figcaption><div></div><div></div><div></div><div></div></figure> |
| 14:17 | <felixjet> | is that valid? |
| 14:25 | <MikeSmith> | felixjet: yes |
| 14:26 | <felixjet> | and the example of figure + code shows this figcaption: <figcaption>Listing 4. The primary core interface API declaration.</figcaption> |
| 14:26 | <felixjet> | so, its a caption, and the flow content associated is <pre><code> |
| 14:27 | <felixjet> | thats ok, but what if the figcaption is used like <figcaption>javascript</figcaption> |
| 14:27 | <felixjet> | is that semantically still correct and good use? |
| 14:27 | <felixjet> | because thats not a caption at all, it's not describing the content of the code |
| 14:30 | <zcorpan> | felixjet: why is it not a caption? |
| 14:30 | <felixjet> | because it's not describing whats inside the <code> tag |
| 14:30 | <felixjet> | it's more like a label |
| 14:30 | <felixjet> | label != caption |
| 14:32 | <zcorpan> | "The figcaption element represents a caption or legend" |
| 14:38 | <zcorpan> | I guess "javascript" is arguably not correct use of figcaption, given dictionary definitions of the these words |
| 14:38 | <zcorpan> | maybe you want <pre class="language-javascript"><code> |
| 14:40 | <zcorpan> | https://html.spec.whatwg.org/#the-code-element |
| 14:40 | <zcorpan> | or class on the <code> |
| 15:07 | <felixjet> | the language-javascript is a class that specifies the language of the code |
| 15:08 | <felixjet> | i'm talking about showing that language label |
| 15:08 | <felixjet> | if it should be figcaption or not |
| 15:08 | <felixjet> | the class doesn't show, it just style the <code> |
| 19:04 | <igrigorik> | annevk: ping :) .. https://github.com/whatwg/fetch/pull/419 - anything I can do to help land that? |
| 19:04 | <botie> | will do |
| 19:05 | <annevk> | igrigorik: yeah I was looking for WPT |
| 19:05 | <annevk> | igrigorik: sorry for the delay in replying, some vacation plus now it's Mozilla week |
| 19:06 | <annevk> | igrigorik: we're slowly moving to a world where specification changes require corresponding WPT changes |
| 19:07 | <igrigorik> | annevk: np! re, WPT: as in, merge failing tests showing that update hasn't been implemented anywhere.. yet? =/ |
| 19:07 | <annevk> | igrigorik: heh, yeah, that would do |
| 19:07 | <annevk> | igrigorik: preferably with a pointer to the Fetch PR |
| 19:08 | <annevk> | igrigorik: and then when I land the Fetch PR I'll point to the tests |
| 20:11 | <annevk> | gsnedders: jgraham: the formatting in http://testthewebforward.org/docs/test-format-guidelines.html#tests-involving-multiple-origins seems wrong |
| 20:12 | <jgraham> | annevk: You mean there is text missing? |
| 20:12 | <annevk> | jgraham: yeah |
| 20:12 | <annevk> | jgraham: also, what can I assume location.host to return when a test is normally run? |
| 20:12 | <annevk> | jgraham: would that include a subdomain or not? |
| 20:12 | <annevk> | jgraham: that is, I'm wondering how to construct a request to a different domain given location.host as input |
| 20:13 | <jgraham> | annevk: https://github.com/w3c/web-platform-tests/blob/master/docs/test-format-guidelines.md has the unbroken documentation |
| 20:15 | <annevk> | jgraham: okay, but it doesn't really say much about how to do any of that from script |
| 20:16 | <jgraham> | It's a text substitution feature. Script doesn't really come into it |
| 20:17 | <jgraham> | I mean you can write `var host = "{{location[host]}}"` and put it in foo.sub.js for example |
| 20:19 | <annevk> | jgraham: I was trying to avoid substitution since I was just modifying an existing JS file used by several tests |
| 20:20 | <annevk> | jgraham: but I think I'm going to skip writing the test I was wanting to write since it's a little more involved than I want |
| 20:52 | <gsnedders> | annevk: oh, yeah, I noticed that a few days ago |
| 20:52 | <gsnedders> | annevk, jgraham: it's basically impossible to fix on ttwf without making it use non-standard Markdown stuff which breaks it on github :\ |
| 21:28 | <jgraham> | gsnedders: ttwf must die |
| 21:35 | <gsnedders> | jgraham: I agree. |
| 21:35 | <gsnedders> | jgraham: OTOH, Github Pages is still Jekyll so we hit the same issue |
| 21:36 | <gsnedders> | see <https://github.com/gsnedders/wpt-docs/commit/b778d04cfd3d476160b5f8ef7a87813029c91878>; which fixes that, if anyone wants to cherry-pick it and break the Github view :\ |
| 22:00 | <zcorpan> | Domenic: are you doing Starting Strength? |
| 22:05 | <Ms2ger> | Is that something people do? Why? |
| 22:34 | <zcorpan> | Ms2ger: to get stronger typically |
| 22:41 | <Domenic> | zcorpan: modified Stronglifts 5x5; clean and snatch scare me |
| 22:45 | <zcorpan> | Domenic: ok. but just 1 set for deadlift? |
| 22:45 | <Domenic> | zcorpan: ya |
| 22:47 | <zcorpan> | Domenic: i did that too for many years. this year i upped the volume for deadlift. 5x5 two times a week with linear progression, then a 5x5 "light" day and a heavier day with 2-3 sets of 3-5 reps. seems like it paid off |
| 22:48 | <Domenic> | oh wow, yeah |
| 22:49 | <zcorpan> | now time to sleep :-) nn |
| 22:54 | <caitp> | what does "paid off" entail though |
| 22:57 | <gsnedders> | can lift, bro |
| 23:02 | <jgraham> | Can probably also lift things that aren't bros |
| 23:04 | <caitp> | "it paid off so much that now the inlaws are calling me over whenever they need to move heavy furniture it's great" |
| 23:13 | <MikeSmith> | http://stackoverflow.com/questions/41047773/service-workers-fetch-event-never-fires |
| 23:29 | <MikeSmith> | http://stackoverflow.com/questions/16824661/cors-request-not-working-in-safari/22924272#22924272 seems to indicate that Safari adds “Origin” to Access-Control-Request-Headers |
| 23:29 | <MikeSmith> | which seems non-conforming |