- From: <bugzilla@jessica.w3.org>
- Date: Fri, 01 Oct 2010 23:06:54 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10923 --- Comment #6 from Jonas Sicking <jonas@sicking.cc> 2010-10-01 23:06:54 UTC --- (In reply to comment #4) > If we actually want that behavior should not we try to use localized strings > based on the language of the page rather than based on the language of the > browser? I suspect this is already allowed by spec and is basically a quality-of-implementation issue. However at least in firefox we only ship with one set of localized strings as things stand now. I suspect this is something we'll look into in the future. > And just as a sanity check, there is no use case for different error messages > depending on what constraint was violated? I would say there is. That was one of the issues I originally raised in the thread pointed to in comment 0. However I think it's ok to start simple here and expand as we see need. One problem is that there isn't really a specified set of possible error messages. For example a browser could have different error messages for an invalid email address with a pattern, a invalid email address without pattern and an invalid email address that has required set. In any case, with a bit of js-code this can be handled. In the event handler you can inspect the .value as well as the various properties properties on .validity and using that information set the new attribute to whatever you want. -- 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 Friday, 1 October 2010 23:06:57 UTC