| 00:10 | <JakeA> | Fetch can return opaque responses. You get detailed cors options, and soon you'll get streams. You'll be able to explain XHR in terms of fetch. |
| 00:10 | <JakeA> | But fetch does more, better |
| 00:17 | <TabAtkins> | Domenic: Okay, just landed the ability to replace boilerplate sections. Should we come up with some decent default text, or should I just make an empty status-whatwg.include file and let you fill it in only when desired? |
| 01:58 | <JonathanNeal> | gsnedders: Fetch? |
| 03:01 | <zewt> | gsnedders: sit |
| 03:02 | <SamB> | gsnedders: rollover |
| 04:52 | <JonathanNeal> | I see that I can’t load SVGs from different domains. Is there any way to get them to load? Like updating the host’s origin policy? |
| 05:10 | <SamB> | JonathanNeal: how are you trying to use them? |
| 05:10 | <SamB> | I think you can use them for <img> just fine |
| 05:10 | <JonathanNeal> | <svg><use xlink:href=""/></svg> |
| 05:14 | <SamB> | ah, yeah, that would leak info |
| 05:44 | <JonathanNeal> | SamB: is there something like Access-Control-Allow-Origin I can set to allow it? |
| 05:51 | <TabAtkins> | JonathanNeal: No, but theoretically it would be find to allow that. |
| 05:51 | <TabAtkins> | JonathanNeal: But can you use just <image>? |
| 05:51 | <TabAtkins> | Or do you really need the behavior of <use>? |
| 06:12 | <JonathanNeal> | TabAtkins: I have an SVG with many <symbol> elements. I use it as a spritemap. I am hosting the spritemap on another domain. |
| 06:14 | <JonathanNeal> | My use case is that our university hosts our branding on one domain. Among the assets are stylesheets and images, some of which I have updated to use SVG instead of PNG and glyphfont. |
| 06:38 | <JonathanNeal> | TabAtkins: These sprites’ fills are colorized by the current color, so I’m not sure I can use <image>. |
| 06:40 | <caitp> | don't you just yearn for the good old days of 1x1 pixel transparent gifs and recycled jpegs full of artifacts |
| 13:05 | <GPHemsley> | If a line is made up spans with various (proportional) font-size values, is it conforming for the text to overlap across lines? |
| 13:07 | <GPHemsley> | https://imgur.com/RBsyMR1 |
| 13:16 | <SimonSapin> | GPHemsley: I believe not |
| 13:27 | <SimonSapin> | GPHemsley: with `position: static` and `transform: none`, the line box should be high enough to include everything, and line boxes should not overlap each other |
| 13:30 | <GPHemsley> | ah, hmm, it seems there is a line-height of 25px in the cascade |
| 13:31 | <GPHemsley> | data:text/html,<div style="width: 25em; line-height: 25px"><span style="font-size: 1.5em;">act</span> <span style="font-size: 1.5em;">action</span> <span style="font-size: 1.5em;">american</span> <span style="font-size: 1.1em;">bill</span> <span style="font-size: 0.9em;">congress</span> <span style="font-size: 0.9em;">continue</span> <span style="font-size: 1.8em;">dream</span> <span style="font-size: 0.9em;">forwardlooking</span> < |
| 13:31 | <GPHemsley> | span style="font-size: 1.5em;">government</span> <span style="font-size: 1.1em;">john</span> <span style="font-size: 0.9em;">kennedy</span> <span style="font-size: 0.9em;">long</span> <span style="font-size: 1.1em;">meet</span> <span style="font-size: 0.7em;">moment</span> <span style="font-size: 1.1em;">must</span> <span style="font-size: 1.5em;">nation</span> <span style="font-size: 1.3em;">national</span> <span style="font-size: |
| 13:31 | <GPHemsley> | 1.3em;">need</span> <span style="font-size: 1.3em;">now</span> <span style="font-size: 4em;">our</span> <span style="font-size: 1.3em;">peace</span> <span style="font-size: 0.9em;">program</span> <span style="font-size: 0.9em;">rights</span> <span style="font-size: 1.1em;">seek</span> <span style="font-size: 1.5em;">strength</span> <span style="font-size: 1.5em;">strong</span> <span style="font-size: 1.5em;">time</span> <span style= |
| 13:31 | <GPHemsley> | "font-size: 1.3em;">united</span> <span style="font-size: 4em;">will</span> <span style="font-size: 0.7em;">years</span> |
| 13:31 | <GPHemsley> | ah, hm |
| 14:52 | <matijs> | Is there a machine readable value for x that we can use in a <time datetime=x>present</time> to represent the present/now/today? |
| 21:47 | <JonathanNeal> | GPHemsley: that’s some nice HTML you got there. |
| 22:05 | <JonathanNeal> | TabAtkins: When you say “that model is crazytown” is that referring to <use xlink:href>? Do you think the future of using SVGs is strictly <img> or something else? |
| 23:06 | <caitp> | as sad as it is, xml doesn't work very well in HTML or the DOM, so SVG has some issues --- they aren't necessarily related to the issue you're talking about WRT cross-domain <use> tags, but there are a number of hard problems to solve, and it could be that SVG's future in html is just as broken as html has been, historically, if not moreso |
| 23:07 | <caitp> | no need to get into the specifics about the various broken things, but if you've looked at it, you've probably noticed some of the issues |
| 23:09 | <caitp> | of course that doesn't mean that the future of SVG won't be successful, it's a common theme around here about broken things being highly successful |
| 23:11 | <SamB> | caitp: :-( |
| 23:14 | <caitp> | well I'm not saying I'm right, it could be a pessimistic view =) |
| 23:15 | <caitp> | but the way it looks to me, it's a bit like trying to fit a square peg into a round hole, it doesn't quite squeeze in |
| 23:17 | <SamB> | well, I mean, I don't really expect SVG embedded in the HTML syntax to work the best ... |
| 23:17 | <caitp> | the network requirements may not line up with those of the web platform, xml complicates things for CSS resulting in weird and unfortunate hacks, which are still not actually working in some mainstream browsers, and are certainly not working with DOM apis using query selectors, beyond selectors, the createElementNS thing is really just a hack to support xml, there are all these corners that don't quite fit |
| 23:18 | <caitp> | the CSS issue particularly being @namespaces |
| 23:19 | <caitp> | yeah it's not really limited to SVG, most of that stuff is just XML not really fitting well into HTML to begin with |
| 23:19 | <SamB> | where you really need something more like what RNG has, eh? |
| 23:19 | <SamB> | and CSS not really being this generic thing it's presented as |
| 23:19 | <SamB> | I guess it works about as well as DTDs though ... |
| 23:44 | <TabAtkins> | JonathanNeal: I'm referring to cross-document <use>. |
| 23:44 | <TabAtkins> | Though now that the instance tree is gone, it might be slightly saner. |
| 23:45 | <TabAtkins> | caitp: Namespaces don't really cause problems for CSS unless you're missing vocabs with the same element names. |
| 23:46 | <caitp> | it's not necessarily a problem implementing them, but lets face it, it's a hack |
| 23:47 | <TabAtkins> | And even then it's not a "problem" so much as an inconvenience. |
| 23:47 | <caitp> | inconveniences are problems =) but I concede that css is the smallest problem |
| 23:48 | <caitp> | although DOM selector APIs having to deal with case-sensitive names is kind of sucky |
| 23:48 | <caitp> | because that is just totally different from HTML |
| 23:48 | <caitp> | which is what this stuff was built for |
| 23:49 | <caitp> | there are all kinds of problems with it, and I'm not saying that as an attack on XML, because XML is great. but the pieces never really fit together very well |
| 23:49 | <caitp> | from my perspective |