- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 04 Oct 2017 23:40:19 +0000
- To: public-css-archive@w3.org
The Working Group just discussed `Styling the ::spelling-error marker`, and agreed to the following resolutions: * `RESOLVED: Specify that custom styling of the underline overrides the UA-rendered underline (not just adds to it). Details to be determined in a separate issue.` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> Topic: Styling the ::spelling-error marker<br> <TabAtkins> GitHub: https://github.com/w3c/csswg-drafts/issues/1828<br> <TabAtkins> florian: In Pseudo4 we have ::spelling-error and ::grammar-error. The spec doesn't say that the browser is supposed to use these to put their own markers.<br> <TabAtkins> florian: So technically it's valid for your outlines to *add* to the browser UI, not replace.<br> <TabAtkins> florian: So the spec needs to state that...<br> <fantasai> +1 to Florian's proposal<br> <fantasai> to require that UA styles are expressed in this manner<br> <TabAtkins> florian: Maybe do UA stylesheet to mandate what they look like by default, or just say that the UA one has to use ::spelling-error<br> <TabAtkins> TabAtkins: Don't mandate the UA style, let it do whatever. But definitely mandate that it replaces.<br> <TabAtkins> myles: The existing markers don't necessarily map to something in CSS, so we can't do it precisely in the UA stylesheet.<br> <TabAtkins> myles: For example, the MacOS style is under-dots with a gradient inside, and we try hard to make sure there's never a partial dot.<br> <tantek> q+<br> <TabAtkins> florian: Okay, so how to specify it?<br> <fantasai> I don't think making sure there's never a partial dot is incompatible with CSS<br> <TabAtkins> florian: Any property specified, it shuts down the native one?<br> <fantasai> CSS doesn't mandate dot spacing, leaves it up to the UA so that it can do exactly these things<br> <TabAtkins> florian: That seems too much, they might just want to do the color.<br> <TabAtkins> myles: Adjusting the color of our dots isn't possible. It should be just like 'outline'.<br> <TabAtkins> TabAtkins: Agreed.<br> <astearns> ack tantek<br> <TabAtkins> fremy: Yes, it should also have a value that means "native", just like outline.<br> <TabAtkins> tantek: Agreed as well, it's also like borders - the natives might look more special than you can get with built-in stuff.<br> <TabAtkins> tantek: The key aspect here is normative text that says "if you draw it normally, don't draw it when CSS specifies one".<br> <TabAtkins> astearns: And we can agree on that text regardless of whether UAs can specify something today.<br> <dbaron> Tantek was also pointing out to me that what myles described with the dots sounds like a new underline style<br> <TabAtkins> florian: So is that sufficient? If you set color, does that count as "CSS-drawn"?<br> <fantasai> "Any styling provided by the author must override, not duplicate, any particular aspect of the UA's default styling, even if the exact characteristics of that styling are not expressable in CSS."<br> <TabAtkins> myles: That seems like a clear intent that they want a pink error, should switch to the CSS one.<br> <TabAtkins> florian: So what happens then? What style?<br> <TabAtkins> TabAtkins: The default one.<br> <TabAtkins> florian: The default is "none".<br> <tantek> "text-decoration-style:system-spelling-error"<br> <TabAtkins> fantasai: Cant' change the default value - it's 'text-decoration', used more widely than just ::spelling-error.<br> <TabAtkins> fremy: We can say that the default pixel is "1px wavy red" in the UA stylesheet, and the browser is free to render whatever way it wants...<br> <TabAtkins> fremy: Say that if you don't override anything you get the UA rendering, but if you override something you get the other values defined in the spec.<br> <TabAtkins> florian: Model after outline-style:auto which lets UA do whatever, or is the same as solid. We could do somethign similar here, with t-d-s: auto, which can do what it wants, or fall back to wavy.<br> <tantek> or even just text-decoration: system-spelling-error<br> <tantek> since it may affect color/style/etc.<br> <TabAtkins> florian: Only problem is that then you can use the spelling-error style on any element.<br> <TabAtkins> TabAtkins: Is taht a problem?<br> <gregwhitworth> this sounds like possibly an option for env()<br> <tantek> and there may be no way to decompose the system-spelling-error "look" into components<br> <TabAtkins> florian: No, I think it's useful, so you can do your own spelling marking in JS or something and have it match with native.<br> <gregwhitworth> env(spelling-error)<br> <tantek> same with text-decoration: system-grammar-error<br> <TabAtkins> astearns: So it sounds like we want to add a system-spelling-error style for text-decoration.<br> <tantek> just thinking off the top of my head<br> <TabAtkins> myles: We have a new concern, and have the WK person implementing this.<br> <tantek> please consider these proposals with a grain of salt. or is that sand. I forget.<br> <TabAtkins> Daniel: So are you proposing these for each of the error types?<br> <tantek> haven't through through the connotations for the cascade, but similar to outline right?<br> <TabAtkins> florian: Just the two.<br> <TabAtkins> TabAtkins: We only recognzie two with pseudo-elements so far.<br> <TabAtkins> Daniel: Sounds great to opt into the system-spelling one.<br> <TabAtkins> Daniel: What if they want to style the errors and achieve the look of the system one.<br> <TabAtkins> Daniel: So on Mac the spelling errors are always drawn beneath existing text decorations, so if you have underlines, the spelling markers are put below them.<br> <TabAtkins> Daniel: How do you achieve the same effect?<br> <TabAtkins> florian: No problem here, I think. The underline isn't set on the spelling error, it's set on some parent element. The spelling error decoration is set on ::spelling-error.<br> <dbaron> maybe somebody should write up what the proposal is and we should come back to it once people had a chance to read and ask questions?<br> <astearns> +1<br> <TabAtkins> Daniel: I specifically mean if you just want, say, a black wavy underline, but definitely underneath the existing underline.<br> <TabAtkins> fantasai: We have a control for that in Text level 4.<br> <TabAtkins> florian: text-underline-offset.<br> <florian> https://drafts.csswg.org/css-text-decor-4/#underline-offset<br> <TabAtkins> Daniel: Okay, so that would allow offsetting.<br> <TabAtkins> fantasai: Yeah. The "auto" value is different tho - "auto" just means "UA decides on the offset appropriately", and can use text information or something.<br> <TabAtkins> fantasai: Currently can't pay attention to other decorations to avoid overlapping, we would need another value for that.<br> <TabAtkins> astearns: So we're going to resolve that if the ::spelling-error has t-d styles, we'll use CSS drawing for that, and override the system-level decoration.<br> <tantek> q+ dbaron<br> <TabAtkins> dbaron: I think that might need to be specific to certain properties.<br> <tantek> ack dbaron<br> <TabAtkins> dbaron: Dont' want it to happen just if the selector exists, want specific properties to be specified.<br> <TabAtkins> florian: The proposal was to have a t-d value of "system-spelling-error" that gives magic rendering, and if that gets overridden, it uses CSS rendering instead.<br> <tantek> btw feel free to bikeshed the value. e.g. env-spelling-error and env-grammar-error<br> <tantek> etc.<br> <TabAtkins> TabAtkins: So back to what dbaron said in the chat, can we get the actual new proposal in the issue, and reoslve on it next week?<br> <tantek> I have no attachmen to any particular name, presented straw-name only to illustrate concept<br> <gregwhitworth> I must have missed this - but who is asking for this?<br> <gregwhitworth> ^ the feature as a whole<br> <TabAtkins> astearns: Yeah, can we resolve to just do the UA overriding?<br> <tantek> ok with that<br> <TabAtkins> RESOLVED: Specify that custom styling of the underline overrides the UA-rendered underline (not just adds to it). Details to be determined in a separate issue.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1828#issuecomment-334319887 using your GitHub account
Received on Wednesday, 4 October 2017 23:40:09 UTC