- From: <bugzilla@jessica.w3.org>
- Date: Tue, 26 Oct 2010 15:50:57 +0000
- To: public-i18n-bidi@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10809 --- Comment #27 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2010-10-26 15:50:57 UTC --- (In reply to comment #26) > It is not intrusive if that's what the app wants to do. It's very intrusive to store out-of-band directionality info for each submitted item. Applications normally pass around user input as strings. If suddenly you have to pass them around as strings-plus-direction, you have to change all your functions to recognize this format throughout the code. > And if the app wants to > store it by adding control characters to the input value, it can do that too - > that's their business. Adding control characters is a lot easier than stripping > them off. It's not trivial, though, if the input is multiple paragraphs, right? > As explained in the proposal, this is only so when the page can use script. > What if the page is being sent as HTML-mail, where script is not allowed - but > forms are. We should aim to cover the most common use-cases first. If it's possible using JavaScript, that means it's possible 95% of the time. If authors do this in JavaScript often enough, that's when we should consider a declarative, non-scripted way of doing it. If it turns out that authors don't do it in JavaScript even when they can, then it's not worth adding the feature for. (Do e-mails really allow forms in practice? I can't recall ever seeing a form in an e-mail in my life.) -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You reported the bug.
Received on Tuesday, 26 October 2010 15:50:59 UTC