| 13:06 | <pwf> | TabAtkins: how can i make the red/green divs fill the rest of the window when scrolling because the blue divs make the container scrollable |
| 13:06 | <pwf> | https://codepen.io/anon/pen/GEQmGx |
| 15:13 | <plexigras> | why should i use whatwg fetch instead of something like axios? |
| 15:59 | <TabAtkins> | pwf: You're getting bit by <https://bugs.chromium.org/p/chromium/issues/detail?id=599828>;, which is forcing the .inner's sole flex line to be .inner's size, and so .a and .b stretch to that height only. |
| 15:59 | <TabAtkins> | Feel free to comment on that bug and request prioritizing a fix - Safari and Edge act correctly. |
| 16:00 | <ahn0st> | hello |
| 16:00 | <TabAtkins> | (The Flexbox spec did, for a while, define "single-line" to be "has one line worth of content", but that ended up being very bad for reasons like this.) |
| 16:00 | <pwf> | thank you TabAtkins, good to know it's actually a bug! we're working around it by giving up on making the header fixed |
| 16:01 | <TabAtkins> | plexigras: fetch() is the low-level primitive. axios is sugar built on top of it. Use axios if you feel like it makes things sufficiently better to be worth its weight on the page. |
| 16:01 | <TabAtkins> | pwf: Using Grid for page layout will work even better. ^_^ |
| 16:01 | <pwf> | what we ended up with (closer to our actual layout anyways) https://codepen.io/jlee42/pen/owEmXj |
| 16:03 | <pwf> | how's browser support for grid |
| 16:03 | <pwf> | this is the first i've heard of it |
| 16:03 | <pwf> | this is also the first job i've been forced into frontend :< |
| 16:04 | <pwf> | oof, no mobile at all |
| 16:04 | <TabAtkins> | pwf: https://codepen.io/TabAtkins/pen/owEOmN |
| 16:04 | <TabAtkins> | Grid is widely supported! |
| 16:04 | <TabAtkins> | But yeah, mobile might still be lagging a little for Safari. |
| 16:05 | <TabAtkins> | Ah, no, it should be fine: https://caniuse.com/#search=grid |
| 16:05 | <pwf> | awesome |
| 16:06 | <pwf> | thank you so much |
| 16:06 | <TabAtkins> | Flexbox *should* work fine for this case except for the bug. Sorry about that. :( |
| 16:06 | <TabAtkins> | np! |
| 16:06 | <pwf> | we're redoing a lot of the layout right now, so grid might be a good option |
| 17:33 | <annevk> | rbyers: https://bugs.chromium.org/p/chromium/issues/detail?id=123004 is becoming a problem |
| 17:33 | <annevk> | rbyers: https://bugzilla.mozilla.org/show_bug.cgi?id=1377282 |
| 17:51 | <Domenic> | annevk: I don't understand https://github.com/whatwg/dom/issues/76#issuecomment-311805043 ; specs use create or fire an event, whereas author code uses the constructor or createEvent. |
| 17:53 | <annevk> | Domenic: hmm I had forgotten that was the setup |
| 17:54 | <annevk> | Domenic: the PR still has all kinds of issues though it seems |
| 17:54 | <annevk> | Domenic: the high resolution PR |
| 17:55 | <Domenic> | Hmm, dang, would be nice to get that landed |
| 17:55 | <annevk> | Domenic: like it still says that timeStamp is set when the event is created |
| 17:55 | <Domenic> | I'd imagine majidvp_ views the EventInit issue as blocking though since that would change how he solves all the rest |
| 17:55 | <annevk> | Domenic: although maybe that's okay |
| 17:56 | <annevk> | Domenic: btw, smaug is not in the US so I haven't really been able to poll him on the addition of new DOM features |
| 17:56 | <Domenic> | ah ok |
| 17:59 | <Domenic> | annevk: maybe comment on issue 76 then indicating that distinguishing based on create/fire vs. constructor/createEvent is a good path forward? |
| 18:02 | <annevk> | Domenic: done |
| 18:02 | <Domenic> | \o/ |
| 18:03 | <annevk> | Domenic: I did think that eventually we wanted all construction of objects to go through the constructor |
| 18:03 | <annevk> | Domenic: potentially with hidden flag |
| 18:03 | <Domenic> | Maybe... that seems pretty long-term |
| 18:10 | <majidvp_> | annevk: "it still says that timeStamp is set when the event is created", only for synthetic events though. The PR uses occurrence time for non-synthetic events. |
| 18:11 | <majidvp_> | The PR is not blocked on having EventInitDic issue resolved. But you raised the same concerned there but I don't see it given that we have different wording for the two paths that exists. |
| 18:16 | <virmaha> | Hello. When I check http://callmenick.com/_development/html5-video/index.html in network tab, why does the 1st request have content-length 40 MB(approx) but 'size' column shows value in KB? And if the browser has got entire video in first request, why are there multiple requests? |
| 18:23 | <annevk> | majidvp_: yeah, maybe it's okay, I have to review again given what Domenic said |
| 18:23 | <annevk> | majidvp_: the origin time stuff is a little confusing to me |
| 21:32 | <rbyers> | annevk: Thanks, that case helps argue for priority. Updated: https://bugs.chromium.org/p/chromium/issues/detail?id=123004#c43 |