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

2008-12-02 Thread Ian Hickson
On Mon, 17 Nov 2008, Samuel Santos wrote: On Wed, Nov 12, 2008 at 12:14 AM, Ian Hickson [EMAIL PROTECTED] wrote: On Tue, 11 Nov 2008, Samuel Santos wrote: On Thu, 6 Nov 2008, Samuel Santos wrote: If changing the button text can be a security issue (e.g. induce the user to an

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

2008-11-17 Thread Samuel Santos
On Wed, Nov 12, 2008 at 12:14 AM, Ian Hickson [EMAIL PROTECTED] wrote: On Tue, 11 Nov 2008, Samuel Santos wrote: On Thu, 6 Nov 2008, Samuel Santos wrote: If changing the button text can be a security issue (e.g. induce the user to an action that he's not aware of), we can come up

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

2008-11-11 Thread Samuel Santos
On Thu, Nov 6, 2008 at 6:17 PM, Samuel Santos [EMAIL PROTECTED] wrote: On Thu, Nov 6, 2008 at 5:50 PM, Ian Hickson [EMAIL PROTECTED] wrote: On Thu, 6 Nov 2008, Eduard Pascual wrote: I agree with Samuel in that this is an issue. In Catalunya, most often Spanish software is used (both OS

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

2008-11-11 Thread Ian Hickson
On Tue, 11 Nov 2008, Samuel Santos wrote: On Thu, 6 Nov 2008, Samuel Santos wrote: If changing the button text can be a security issue (e.g. induce the user to an action that he's not aware of), we can come up with some solutions. What about allowing the Author to change the

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

2008-11-06 Thread Ian Hickson
On Thu, 6 Nov 2008, Samuel Santos wrote: Why do they use the wrong language browser in the first place? In Portugal a lot computers come with the english OS version.This means that the browser is in english and configured to have english as the default language. The problem with the

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

2008-11-06 Thread Ian Hickson
On Thu, 6 Nov 2008, Eduard Pascual wrote: I agree with Samuel in that this is an issue. In Catalunya, most often Spanish software is used (both OS and browsers), because a lot of the software is not easily (or at all) available in Catalan (specially Microsoft software, such as Windows and

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

2008-11-06 Thread Samuel Santos
On Thu, Nov 6, 2008 at 5:50 PM, Ian Hickson [EMAIL PROTECTED] wrote: On Thu, 6 Nov 2008, Eduard Pascual wrote: I agree with Samuel in that this is an issue. In Catalunya, most often Spanish software is used (both OS and browsers), because a lot of the software is not easily (or at all)

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

2008-11-06 Thread timeless
On Thu, 6 Nov 2008, Samuel Santos wrote: What about allowing the Author to change the control's locale? By doing so, the UA can then render the button with the same locale as the application without compromising the security. On Thu, Nov 6, 2008 at 5:50 PM, Ian Hickson [EMAIL PROTECTED] wrote:

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

2008-11-05 Thread Ian Hickson
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

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

2008-11-05 Thread Samuel Santos
On Wed, Nov 5, 2008 at 10:46 PM, Ian Hickson [EMAIL PROTECTED] wrote: On Wed, 5 Nov 2008, Samuel Santos wrote: I find it very hard to convince some clients that in order to have the browse button in their language they must configure their browsers. The vast majority of them don't even

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

2008-11-05 Thread Eduard Pascual
On Thu, Nov 6, 2008 at 12:15 AM, Samuel Santos [EMAIL PROTECTED] wrote: On Wed, Nov 5, 2008 at 10:46 PM, Ian Hickson [EMAIL PROTECTED] wrote: On Wed, 5 Nov 2008, Samuel Santos wrote: I find it very hard to convince some clients that in order to have the browse button in their language

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

2008-11-05 Thread Samuel Santos
Ian, If changing the button text can be a security issue (e.g. induce the user to an action that he's not aware of), we can come up with some solutions. What about allowing the Author to change the control's locale? By doing so, the UA can then render the button with the same locale as the

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

2008-05-14 Thread Samuel Santos
This issue seems to be a very recurring and still unsolved problem when dealing with Web internationalization / multi-language Web Apps. I would like to suggest this to be reviewed with an editor comment please. Additionally, it's important if we could decorate separately the file path text field

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

2008-05-14 Thread Darin Adler
On May 14, 2008, at 9:38 AM, Samuel Santos wrote: On Mon, Feb 11, 2008 at 12:11 AM, Samuel Santos [EMAIL PROTECTED] wrote: 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

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

2008-02-10 Thread Samuel Santos
I've already tried to comment on this issue [1] but I think I haven't achieve to make my point clear. When developing a web application I can't usually rely on the languages configured on the user browser (sent through the Accept-Language). Often I need to send e-mail or sms notifications and I