W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2008

[whatwg] Review of the 3.16 section and the HTMLInputElement interface

From: Ian Hickson <ian@hixie.ch>
Date: Wed, 5 Nov 2008 17:20:46 +0000 (UTC)
Message-ID: <Pine.LNX.4.62.0811051717000.1237@hixie.dreamhostps.com>
On Sun, 10 Feb 2008, Samuel Santos wrote:
> 
> This is a problem for the input element with type="file". If the 
> language selected in his profile is, e.g. portuguese, and the language 
> in the browser is english (the default), he will see all the application 
> in portuguese and the input file browse button text value will be in 
> english.

Why is this a problem given that all the rest of the UA strings -- menus, 
for example -- will also be in the default language? Isn't it up to the 
user to pick the right language in the UA?


> What I propose is to add a new attribute to the input element like this:
>            attribute DOMString       browseText;
> this allows us developers to change the input file browse button text to
> have it in the same language as the rest of the application and not with the
> language selected in the browser.

We really don't want to allow authors to fiddle with this control, because 
it is highly security-sensitive (similarly browsers don't allow styling of 
this control).

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 5 November 2008 09:20:46 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:07 UTC