| 06:44 | <hsivonen> | dbaron: thanks. I wanted to make sure the scrolling attribute on iframes didn't have a CSS mapping |
| 07:18 | <annevk> | hsivonen: it does not do more than overflow:none, no? |
| 07:36 | <hsivonen> | annevk: does overflow:none applied to the iframe element itself prevent it from scrolling? |
| 07:43 | <annevk> | hsivonen: I'd expect not |
| 07:43 | <annevk> | hsivonen: nope |
| 07:43 | <annevk> | data:text/html,<iframe style=overflow:none srcdoc="<br>t<br>g<br>t<br>t<br>t<br>g<br>t<br>t<br>t<br>g<br>t<br>t<br>t<br>g<br>t<br>t<br>t<br>g<br>t<br>t"></iframe> |
| 07:52 | <hsivonen> | good. thanks |
| 15:30 | <annevk> | domfarolino: you probably wanna read through https://github.com/whatwg/html/issues/3840#issuecomment-481034206 |
| 15:31 | <domfarolino> | annevk: will do thank you |
| 15:38 | <smaug____> | annevk: so all the lazyload elements get auto per default, and wouldn't block page load by default |
| 15:39 | <smaug____> | so UA wouldn't need to block top level page load ever for iframes? |
| 15:39 | <smaug____> | I must be missing something |
| 15:39 | <annevk> | smaug____: oh sorry, after posting I realized the "auto" thing might be significant |
| 15:39 | <annevk> | smaug____: per the PR it doesn't interact with the load event at all |
| 15:40 | <annevk> | smaug____: that's the problem I was seeing |
| 15:40 | <smaug____> | ok |
| 15:40 | <smaug____> | yeah, that is major issue |
| 17:53 | <bkardell> | was doing some stuff with analyzing tag names and attributes and noticed that the single page html spec contains like 54k <c- elements with boolean single letter attributes... is there somewhere I can read about what that's about? |
| 17:54 | <bkardell> | just curious |
| 18:09 | <astearns> | TabAtkins: ^ I think I remember the <c- b> stuff was something you were doing, but I forget what it was about |
| 18:15 | <astearns> | ah, bkardell they're for highlighting |
| 18:16 | <bkardell> | yeah I am just curious if anyone wrote about that choice, it seems unusual if legal |
| 18:16 | <astearns> | https://freenode.logbot.info/whatwg/20180605#c1575174 |
| 18:19 | <Mek> | https://github.com/tabatkins/highlighter/commit/75e91017fa33302a9a02876c8a2e4e8d138bf975 |
| 19:05 | <bkardell> | yeah, I wondered if that was all there is to it :-p |
| 21:23 | <bkardell> | so... we have a lot of issues about custom attributes and a long history of mentions in webplatform about 'some kind of way to mixin behaviors' and 'kind of like custom elements' - but... do we actually have anything resembling a proposal or something that lays out use cases and enough details of boundaries that would help it avoid the sorts of problems that hosed is="" and decorators and xbl and .htc-like solutions? |
| 21:23 | <bkardell> | I spent some time searching and I can't find one |
| 21:24 | <bkardell> | s/one/something helpful about this |