| 06:21 | <annevk> | JakeA: wanderview: I'd be okay with landing the tests early |
| 06:21 | <annevk> | JakeA: wanderview: just make sure the commit points to the relevant Fetch PR |
| 06:22 | <annevk> | JakeA: wanderview: and maybe start filing bugs against all the browsers too? Tests first doesn't seem too bad, since we all agree on the specifics |
| 20:27 | <timwis> | Hey folks, we've been thinking about using custom elements for our component library (standards.phila.gov), and are thinking about possible issues.. one that came to mind that's hopefully simple is how to provide the benefit of encapsulated css but not have to import our CSS framework repeatedly -- ie. once foundation.css is imported, reuse it next time it's imported rather than load it to memory twice. is that |
| 20:27 | <timwis> | possible? |
| 22:08 | <MikeSmith> | timwis: TabAtkins would be one of the best people to get insight from on that I think |
| 22:08 | <MikeSmith> | if/when he’s around |
| 22:12 | <MikeSmith> | timwis: nice site by the way |
| 22:13 | <MikeSmith> | design and all the docs too |
| 22:57 | <Domenic> | timwis: have you done measurements? My understanding is that browsers don't duplicate <link rel=stylesheet>s in memory if they go to the same URL. |