W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2010

[Bug 10808] i18n comment 2 : new dir attribute value: auto, and a new attribute: autodirmethod

From: <bugzilla@jessica.w3.org>
Date: Tue, 19 Oct 2010 06:40:25 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1P85s1-0003A7-3R@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10808

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |ASSIGNED

--- Comment #14 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-10-19 06:40:24 UTC ---
(In reply to comment #11)
> 
> It's never a good idea to fix directionality problems by adding to CSS.  They
> should be fixed on the HTML markup level first, and then possibly backported to
> CSS so that more generic languages without agreed-upon semantics for indicating
> directionality can still be displayed correctly.

This misunderstands the proposal, which was to use markup (<output>) to trigger
the CSS behaviour. HTML rendering in the HTML spec is defined in terms of CSS
even for non-CSS UAs, so adding this to CSS does not require that UAs implement
CSS.


The only use case given in this bug so far is the one in comment 3, which as
far as I can tell is the same as the use cases given in bug 10807. If there are
other use cases to consider here, such as the ones in comment 12, then please
describe them, ideally with URLs pointing to real Web pages showing those use
cases, so that I can study them. It's impossible to evaluate proposals without
concrete use cases.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 19 October 2010 06:40:30 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:30:59 UTC