- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 17 May 2017 18:42:49 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-overflow] FPWD for level 4`, and agreed to the following resolutions:
* `RESOLVED: FPWD of Overflow 4`
<details><summary>The full IRC log of that discussion</summary>
<dael> Topic: [css-overflow] FPWD for level 4<br>
<dael> github topic: https://github.com/w3c/csswg-drafts/issues/1374<br>
<dael> astearns: Is it correct that everything in 4 way already in 3?<br>
<dael> Florian: Correct. No new features.<br>
<dael> astearns: Any objections to FPWD of Overflow 4?<br>
<dael> RESOLVED: FPWD of Overflow 4<br>
<dael> Florian: I'll also make sure any L3 edits are reflected in L4.<br>
<dael> fantasai: I'd recommend just dropping those sections.<br>
<dael> Florian: That's better.<br>
<dael> astearns: We don't have time for the last item, so we'll end a minute early.<br>
<dael> astearns: Thanks everybody.<br>
<Florian> fantasai: Can you comment on https://github.com/w3c/csswg-drafts/issues/174#issuecomment-224735914 to say if you accept the decision?<br>
<Florian> TabAtkins: echidna is rejecting MQ4 because of <a href=""> elements in the railroad diagrams. https://labs.w3.org/echidna/api/status?id=89b4647f-7a36-45e4-87d7-47b30f3245ec<br>
<Florian> (if I understand the error message correctly)<br>
<Florian> what gives?<br>
<TabAtkins> Tell them it's broken and SVG allows those just fine.<br>
<TabAtkins> Yay for more validation-that-is-out-of-date-and-prevents-things-from-working!<br>
<Florian> "Tell them"? who's them?<br>
<TabAtkins> Sorry, #pub<br>
<Florian> on irc?<br>
<TabAtkins> Example: <!DOCTYPE html><svg><text y=20><a href="http://example.com">foo</a></text><br>
<TabAtkins> Yeah<br>
<tantek> aside: Florian, thanks very much for the issues you've opened on WPWG rechartering. Keep up the pressure.<br>
<Florian> tantek: My pleasure :) I suppose I am somewhat masochist<br>
<Florian> TabAtkins: it's getting late here, can you deal with the folks on #pub, and publish MQ4 if they fix echinda fast enough, or report back with if they don't?<br>
<TabAtkins> yup<br>
<Florian> TabAtkins: Other than changing the status to WD and pushing the draft, everything should be ready<br>
<Florian> TabAtkins: thanks<br>
<TabAtkins> got me a bug in my bonnet about this validation stuff anyway<br>
<TabAtkins> i'm def in and out today - sick - but we'll see what i can do<br>
<Florian> Well, I am definitely just out today, it's 2:45am, so you're still more active. Take good care of yourself, and if you get the chance to run bikeshed echinda, do it, and if not, I'll pick up from there<br>
<AmeliaBR> TabAtkins: You should *probably* still be using xlink:href so that the links work in Safari. But, yes, the validator needs to be updated to allow href without xlink on SVG links. But that's probably a pull request on the Nu validator, not something specific for W3C publications team.<br>
<Florian> Woohoo, it's so good to have someone how knows SVG inside out. Good to have you on board AmeliaBR.<br>
<Florian> TabAtkins: can you fix bikeshed to generate that instead? with a bit of luck, that will pass the validator<br>
<gsnedders> are table cells by default indefinitely sized?<br>
<AmeliaBR> Also, the Nu Validator really needs to work on their error messaging: Error 1 is "href not allowed here". Error 2 is "href is required" (on the same element). Doh.<br>
<TabAtkins> Heh, I wonder how that happens? Probably: namespaces.<br>
<gsnedders> I'm sure I saw MikeSmith talking about this a while ago, and it was something about requiring a non-empty value<br>
<gsnedders> https://codepen.io/gsnedders/pen/ybxbZN — how do I make that div the full height of its parent?<br>
<gsnedders> I presume the table cell is considered indefinite hence why that isn't working<br>
<AmeliaBR> TabAtkins: Yup. When people write a validator for HTML, and then someone goes and sneaks in some pesky XML namespaces in there. I went to file an error, but someone had beat me to it https://github.com/validator/validator/issues/511<br>
<gsnedders> and I think this is just generally getting into the mess that is table layout :)<br>
<AmeliaBR> @gsnedders It seems to be only looking at whether the parent has `height: auto`, regardless of the actual height. If you set `td {height: 1em;}, then then div changes height. Oh. except not in a cross-browser compatible way: Firefox adjusts it for a 1em height, Chrome and Edge adjust it to fit the actual 2-row <td> height.<br>
<AmeliaBR> So, yes: "I think this is just generally getting into the mess that is table layout :)"<br>
<gsnedders> :)<br>
<gsnedders> even with table-layout: fixed spans are pretty undefined, afaict<br>
<astearns> trackbot, end meeting<br>
</details>
--
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1374#issuecomment-302191423 using your GitHub account
Received on Wednesday, 17 May 2017 18:42:55 UTC