- From: Tantek Çelik <tantek@cs.stanford.edu>
- Date: Fri, 21 Jan 2011 22:53:50 -0800
- To: www-style@w3.org
As planned, I have moved the skeleton definition of text-overflow:ellipsis from CSS3-Text[1] to CSS3-UI[2], and then expanded it to address new information and details. [1] http://dev.w3.org/csswg/css3-text/#text-overflow [2] http://dev.w3.org/csswg/css3-ui/#text-overflow <-- this is the one you want. >From a variety of sources including: * https://bugzilla.mozilla.org/show_bug.cgi?id=312156 * http://www.w3.org/blog/CSS/2009/11/25/resolutions_84 * https://developer.mozilla.org/En/CSS/text-overflow * http://msdn.microsoft.com/en-us/library/ms531174(VS.85).aspx * http://developer.apple.com/library/safari/documentation/appleapplications/reference/SafariCSSRef/Articles/StandardCSSProperties.html#//apple_ref/doc/uid/TP30001266-SW24 (anyone know how to create more usable/sharable non-#-abusing URLs for WebKit CSS documentation?) I've applied the filter of only documenting what appears to be interoperably implemented, dropping things like the <string> value that are not (I'm willing to consider such forward looking features for CSS4-UI). If text-overflow:ellipsis interests you, please take a look. http://dev.w3.org/csswg/css3-ui/#text-overflow If something seems vague or underspecified, please phrase your request for clarification as * a question about a specific case "What happens when ..." * and/or an HTML+CSS test case that illustrates an example of what you think is vaguely specified. I'm especially interested in test cases which demonstrate behavior in existing implementations that appear to contradict the spec, as the intent of the spec is to reflect existing interoperable implementations. Thanks, Tantek -- http://tantek.com/ - I made an HTML5 tutorial! http://tantek.com/html5
Received on Saturday, 22 January 2011 06:55:04 UTC