| 02:10 | <ericandrewlewis> | I notice the example on the WHATWG for asides uses h1's in nearly every structural element - http://www.whatwg.org/specs/web-apps/current-work/multipage/sections.html#the-aside-element |
| 02:11 | <ericandrewlewis> | if that blogroll had 15 articles shown per page, that would make about 20 h1 elements on a page |
| 02:11 | <ericandrewlewis> | is that "fine"? |
| 02:13 | <ericandrewlewis> | that kinda goes against what is said here - https://www.youtube.com/watch?v=GIn5qJKU8VM |
| 03:58 | <Hixie_> | ericandrewlewis: matt's response is talking about pages that don't use sectioning elements |
| 03:58 | <ericandrewlewis> | ah, that makes more sense. |
| 03:58 | <Hixie_> | (his post is from 2009, when those elements were still very new) |
| 03:59 | <ericandrewlewis> | so we're officially over the "one h1 on a page" thang |
| 04:09 | <Hixie_> | "officialy"? |
| 04:09 | <Hixie_> | "officially" even |
| 05:54 | <annevk_> | FWIW: http://wiki.ecmascript.org/doku.php?id=strawman:structured_clone |
| 20:06 | <sedovsek> | Hey. What's the W3C state on CSS Reflection? Are there any standardized ways to achieve it? |
| 20:07 | <sedovsek> | I'm only aware of webkit-box-reflect - which is unofficial… |
| 20:49 | <TabAtkins> | -webkit-box-reflect is terribad, and it'll never be standardized. It shows up with anomolously high usage stats in Blink's use tracker, but once we figure out what's wrong with that, we plan to kill it. |
| 20:50 | <TabAtkins> | sedovsek: If you want to achieve that effect, combine ::before/::after with element() and 'mask'. |