W3C home > Mailing lists > Public > public-css-archive@w3.org > September 2017

Re: [csswg-drafts] [css-backgrounds] 'border: 1px inset' is not interoperable

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 27 Sep 2017 16:15:13 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-332574966-1506528900-sysbot+gh@w3.org>
The Working Group just discussed `'border: 1px inset' is not interoperable`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: 'border: 1px inset' is not interoperable<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/1489<br>
&lt;dael> Rossen_: Is zcorpan on?<br>
&lt;dael> [silence]<br>
&lt;dael> fantasai: I can prob take this<br>
&lt;dael> fantasai: basically the inset and outset borders we don't define what color they should be. This is resulting in non-interop, esp. on 1px. Do we want to work on aligning and, if yes, do we try and do this in L3 or L4?<br>
&lt;tantek> L4 please<br>
&lt;dael> fantasai: I don't think we can resolve on the result, but figuring out where to put this work would help me agenda set.<br>
&lt;dael> Rossen_: Fair.<br>
&lt;tantek> unless someone has citations of real world sites where people are complaining<br>
&lt;tantek> and in which case, seriously, 1px inset/outside/ridge etc. border?!? why?!?<br>
&lt;dael> Rossen_: For the impl would this besomething high on your list of things to fix if we were to agree? Or will this be low priority?<br>
&lt;tantek> silence = low<br>
&lt;dael> Rossen_: I'mgoing to take silence as it being low priority.<br>
&lt;tantek> hah<br>
&lt;dael> Rossen_: As an impl I would say this is low priority for us. We have no had any reports of issues b/c of this. I don't see us rushing this.<br>
&lt;dael> Rossen_: One more call.<br>
&lt;dael> Rossen_: If no one raises urgency I propose L4.<br>
&lt;dael> Rossen_: So this is the call. If you're an impl and want to rush an interop fix, now is the time.<br>
&lt;tantek> if Edge is still using the Trident border style rendering code which was ported from Tasman, then I'd say that's a good default if you want to specify something in L4 :)<br>
&lt;bradk> Wait for L4<br>
&lt;dael> Rossen_: Okay, let's take this to L4. fantasai Is this specific to 1px or inset in general?<br>
&lt;dael> fantasai: I'm not sure.<br>
&lt;dael> florian: From bug it looks like there's a general problem and it's worse at 1px. We need to dig into details.<br>
&lt;tantek> I want to know what is the use-case for these odd 1px border-styles<br>
&lt;dael> Rossen_: Okay. Again, I don't htink we can push inset to L4.<br>
&lt;tantek> seriously why are people doing them? what effect do they expect?<br>
&lt;dael> fantasai: The spec has a not-specific statement as to what the color should be, but no formula. All impl are spec complient.<br>
&lt;tantek> yes that's deliberately vague to capture what implementations did in the late 1990s / early 2000s<br>
&lt;dael> Rossen_: Okay. Let's close saying if there are any more restrictive spec changes that have to be made in terms of inset and color computation, they would go in L4. Obj?<br>
&lt;dael> tantek: I'd want a use case. Why are you doing this? for what effect.<br>
&lt;dael> fantasai: THe default rendering of hr to be consistant?<br>
&lt;bradk> Inset borders are not in vogue anyway<br>
&lt;dael> tantek: Why?<br>
&lt;dael> fantasai: Don't know.<br>
&lt;dael> tantek: That's why I want it documented. I'd prefer an explicit statement saying we don't know why to do this. Most things we do with a use case for what's trying to be achieved. You're just making work without a use case<br>
&lt;astearns> the effect we're looking to achieve is interoperability in an existing feature<br>
&lt;dael> Rossen_: Fair point.<br>
&lt;dael> Rossen_: Your point will me in github. If we ever come back to this we'll have to call for use cases and then revisit. Fair to you?<br>
&lt;dael> tantek: Yeah.<br>
&lt;dael> Rossen_: Anything else?<br>
&lt;dael> fantasai: That's it.<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1489#issuecomment-332574966 using your GitHub account
Received on Wednesday, 27 September 2017 16:15:05 UTC

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