- From: Alan Gresley <alan@css-class.com>
- Date: Thu, 03 Oct 2013 19:49:41 +1000
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- CC: www-style list <www-style@w3.org>
On 3/10/2013 5:53 AM, Tab Atkins Jr. wrote: > Yesterday, I finished up the first draft of the overflow:clip spec: > <http://dev.w3.org/csswg/css-overflow-clipping/> > > It passed a quick review from Blink implementors, so I'd appreciate more review! > > ~TJ How can a new value of clip be used for the property of overflow when clip is a property itself [1] (e.g. CSS2.1)? Why is a new value of overflow being introduced into a new spec and not just (CSS3/CSS4) css-overflow [2]? How can a new spec 'css-overflow-clipping' be introduced when the spec where is being dragged from, being 'css-overflow' is incomplete and unclear? How can such differing behavior between Firefox/Chrome vs IE10/Opera be overlooked in this test case [3] or Firefox/IE10/Opera vs Chrome be overlooked in this test case [4] when this will impact on the behavior that is partly defined in 'css-overflow-clipping'? Alan 1. http://www.w3.org/TR/CSS21/visufx.html 2. http://dev.w3.org/csswg/css-overflow/ 3. <http://css-class.com/test/css/overflow/block-inside-auto-width-float-overflow.htm> 4. <http://css-class.com/test/css/visformatting/float-computed-used.htm> -- Alan Gresley http://css-3d.org/ http://css-class.com/
Received on Thursday, 3 October 2013 09:50:12 UTC