- From: Koji Ishii <kojiishi@gluesoft.co.jp>
- Date: Fri, 29 Oct 2010 07:17:19 -0400
- To: Alan Gresley <alan@css-class.com>
- CC: CSS W3C Group <www-style@w3.org>
Alan, I'm sorry to say that I still don't understand what you want in this thread, so allow me to write the best I can do. If you're proposing a new feature to CSS3 writing modes, it's probably better to talk about the use case and what problems you want to solve first, rather than the solution you found. If people agrees that it is useful and/or the problems should be solved, we can then discuss how to solve it. If you're talking about CSS 2.1 problems you can reproduce by 'direction' and/or 'uncode-bidi' properties, please use [css21] prefix instead of [css3-writing-modes] and people looking at the tag must help you much better than I can. If you're talking about problems you can reproduce using a browser when you used 'writing-mode' property, you should first determine whether the issue is still true for the current editor's draft of CSS3 writing modes spec [1] or not. Unfortunately, there's no implementation of the spec at this point, so you have to use your imaginations. Also please be aware that the spec is very fragile at this point. If you found the issue in the spec, I think you can point out where it is, including the case something is missing. We can then discuss based on the spec. If not, I'm sorry to say this again but it's better solved by the browser vendors. [1] http://dev.w3.org/csswg/css3-writing-modes/ This process must be frustrating to you, I'm sorry about that. As you might be aware of, CSS3 writing mode spec was once CR but now back to ED, and it was changed so much since the last CR that I can't find any better solutions than what I wrote above. Hope this helps. Regards, Koji
Received on Friday, 29 October 2010 11:15:06 UTC