W3C home > Mailing lists > Public > public-css-archive@w3.org > October 2018

Re: [csswg-drafts] [css-ui-4][css-tables-3] should table outlines surround captions too?

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Mon, 22 Oct 2018 19:27:37 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-431876489-1540223607-sysbot+gh@w3.org>
The CSS Working Group just discussed `Defining Outline`.

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: Defining Outline<br>
&lt;astearns> github: https://github.com/w3c/csswg-drafts/issues/3184<br>
&lt;fantasai> florian: Outline property is quite loosely defined, and to a certain degree intentionally so<br>
&lt;fantasai> florian: Ther'es a design reason and a process reason<br>
&lt;fantasai> florian: Design reason is because outline is used for focus, and we didn't wnat to constrain too much how UAs draw their focus rings<br>
&lt;fantasai> florian: On the other hand, outlines are used for decorative purposes all the time, and not having inteorp there is an issue<br>
&lt;fantasai> florian: Process reason was that for L3, we were trying to wrap up and didn't have a clear proposal or interop<br>
&lt;fantasai> florian: So question is, now in L4, do we want to define this more precisely?<br>
&lt;fantasai> florian: Should we pick a behavior and have everyon conform to it?<br>
&lt;fantasai> florian: Or are we still thinking we don't want to constrain the outline.<br>
&lt;fantasai> florian: Wanted to see where the WG stands on these types of issues<br>
&lt;fantasai> florian: Should we try to constrain and find inteorp, or leave open to experimentation by UAs?<br>
&lt;fantasai> smfr: Special behavior in webkit only happens on auto style<br>
&lt;fantasai> florian: That could be a reasonable compromise<br>
&lt;fantasai> florian: let auto do whatever, then gradually narrow down behavior of the rest<br>
&lt;fantasai> florian: Specific issue triggering this discussion was raised by heycam<br>
&lt;fantasai> florian: Seems like you have some interest in increased interop?<br>
&lt;fantasai> heycam: Even if we didn't get to a world with mandated behavior, would be helpful to have more guidelines on which boxes contribute to the outline rectangle<br>
&lt;fantasai> florian: Was contacted by person from Google who works on this<br>
&lt;fantasai> Aleks: I'm implementing this, so that's my interest. My take on outline, I talked to fantasai about them<br>
&lt;fantasai> Aleks: There was a difference for us between focus outline and css outline, and that was annoying<br>
&lt;fantasai> Aleks: Would be nice to define whether focus and css outlines are the same or different, and if different then define css outline strictly for interop<br>
&lt;fantasai> ...<br>
&lt;fantasai> Aleks: When you're tabbing through, you get the "tabbing outline"<br>
&lt;fantasai> florian: If you put 'outline: auto', do you get the same outline as the focus outline or something else?<br>
&lt;fantasai> Aleks: that's a weird edge case in my opinion<br>
&lt;fantasai> florian: current suggestion is to allow UA to do whatever for 'auto' style outline, and otherwise tighten up what the outline is<br>
&lt;tantek> outline was always intended to represent the focus outline, period. and if there's been a divergence it's because implementations were lacking, likely unintentionally.<br>
&lt;fantasai> florian: So I think that's a direction we can look into<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3184#issuecomment-431876489 using your GitHub account
Received on Monday, 22 October 2018 19:27:39 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:38 UTC