Re: [whatwg] Proposal: Inline pronounce element (Tab Atkins Jr.)
On 6/5/2014 3:05 AM, whatwg-requ...@lists.whatwg.org wrote: On Tue, Jun 3, 2014 at 3:26 AM, Daniel Morris wrote: Hello, With existing assistive technology such as screen readers, and more recently the pervasiveness of new technologies such as Siri and Google Now to name two examples, I have been thinking about the appropriateness and potential of having a way to represent the pronunciation of words on a web page. There is currently no other text-level semantic that I know of for pronunciation, but we have elements for abbreviation and definition. As an initial suggestion: iPad (Where the `ipa` attribute is the pronunciation using the International Phonetic Alphabet.) What are your thoughts on this, or does something already exist that I am not aware of? This is already theoretically addressed by , linking to a well-defined pronunciation file format. Nobody implements that, but nobody implements anything new either, of course. ~TJ I think it'd be a lot easier for sites, say along the lines of Wikipedia, to support inline markup to allow users to get a word referenced at the beginning of an article, for example, pronounced accurately. Brett
[whatwg] Missing HTMLSelectElement.autocomplete
Hello, Is it intentional that there is no HTMLSelectElement.autocomplete IDL attribute[1]? Both [2] and [3] have it so there is currently inconsistency. Thanks, Matthew Noorenberghe [1] http://www.whatwg.org/specs/web-apps/current-work/#the-select-element [2] http://www.whatwg.org/specs/web-apps/current-work/#the-input-element [3] http://www.whatwg.org/specs/web-apps/current-work/#the-textarea-element
Re: [whatwg] Missing HTMLSelectElement.autocomplete
I would like to insist on the datalist proposition I posted on this list (didn't caught any interest, though). A datalist for select would enable to have the contents of a select defined externally, and would also enable the reuse of this data. I don't see why datalist can be applied to an input and not to a select. Cheers, Luis On Wed, Jun 4, 2014 at 10:13 PM, Matthew Noorenberghe < mattn+wha...@mozilla.com> wrote: > Hello, > > Is it intentional that there is no HTMLSelectElement.autocomplete IDL > attribute[1]? Both [2] and [3] have it so there is > currently inconsistency. > > Thanks, > Matthew Noorenberghe > > [1] http://www.whatwg.org/specs/web-apps/current-work/#the-select-element > [2] http://www.whatwg.org/specs/web-apps/current-work/#the-input-element > [3] > http://www.whatwg.org/specs/web-apps/current-work/#the-textarea-element >
Re: [whatwg] Missing HTMLSelectElement.autocomplete
On Wed, Jun 4, 2014 at 6:13 PM, Matthew Noorenberghe wrote: > Hello, > > Is it intentional that there is no HTMLSelectElement.autocomplete IDL > attribute[1]? Both [2] and [3] have it so there is currently > inconsistency. I discovered the same issue while working on Autofill/requestAutocomplete in Chrome and Ian Hickson mentioned it was likely just an oversight. Autofill in Chrome didn't always work [well] with tags, so I could see how Autofill-related stuff like [autocomplete] could be out of date. It'd be nice to avoid more attribute accessors (and encourage authors to use getAttribute() instead), but if and have them we should probably be consistent. -- Dan Beam db...@chromium.org > > Thanks, > Matthew Noorenberghe > > [1] http://www.whatwg.org/specs/web-apps/current-work/#the-select-element > [2] http://www.whatwg.org/specs/web-apps/current-work/#the-input-element > [3] http://www.whatwg.org/specs/web-apps/current-work/#the-textarea-element
Re: [whatwg] Missing HTMLSelectElement.autocomplete
On Wed, 4 Jun 2014, Matthew Noorenberghe wrote: > > Is it intentional that there is no HTMLSelectElement.autocomplete IDL > attribute? Both and have it so there is currently > inconsistency. Woops. Totally an oversight on my part. When I added autocomplete to select recently, I forgot to fix that. Fixed. Thanks. On Wed, 4 Jun 2014, Luis Farzati wrote: > > I would like to insist on the datalist proposition I posted on this list > (didn't caught any interest, though). > > A datalist for select would enable to have the contents of a select > defined externally, and would also enable the reuse of this data. > > I don't see why datalist can be applied to an input and not to a select. Don't worry, your e-mail is in the queue! Requests for features tend to take a bit longer for me to deal with than simple bug reports, though. On Wed, 4 Jun 2014, Dan Beam wrote: > > It'd be nice to avoid more attribute accessors (and encourage authors to > use getAttribute() instead), but if and have them we > should probably be consistent. Can you elaborate on the cost of attribute accessors? -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Re: [whatwg] Missing HTMLSelectElement.autocomplete
On Wed, Jun 4, 2014 at 7:16 PM, Ian Hickson wrote: > On Wed, 4 Jun 2014, Matthew Noorenberghe wrote: >> >> Is it intentional that there is no HTMLSelectElement.autocomplete IDL >> attribute? Both and have it so there is currently >> inconsistency. > > Woops. Totally an oversight on my part. When I added autocomplete to > select recently, I forgot to fix that. > > Fixed. Thanks. > > > On Wed, 4 Jun 2014, Luis Farzati wrote: >> >> I would like to insist on the datalist proposition I posted on this list >> (didn't caught any interest, though). >> >> A datalist for select would enable to have the contents of a select >> defined externally, and would also enable the reuse of this data. >> >> I don't see why datalist can be applied to an input and not to a select. > > Don't worry, your e-mail is in the queue! Requests for features tend to > take a bit longer for me to deal with than simple bug reports, though. > > > On Wed, 4 Jun 2014, Dan Beam wrote: >> >> It'd be nice to avoid more attribute accessors (and encourage authors to >> use getAttribute() instead), but if and have them we >> should probably be consistent. > > Can you elaborate on the cost of attribute accessors? Namespace exhaustion (maybe form.autocomplete() would've worked instead of requestAutocomplete() if autocomplete="" hadn't taken it?), multiple ways to do things (vs getAttribute), longer specs/IDLs/compile times. -- Dan Beam db...@chromium.org > > -- > Ian Hickson U+1047E)\._.,--,'``.fL > http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. > Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Re: [whatwg] Missing HTMLSelectElement.autocomplete
Thanks Ian. - Original Message - > From: "Dan Beam" > > It'd be nice to avoid more attribute accessors (and encourage authors > to use getAttribute() instead), but if and have > them we should probably be consistent. At least in this case it's not just mirroring the attribute content so it adds some value over getAttribute. Matthew Noorenberghe
Re: [whatwg] Missing HTMLSelectElement.autocomplete
On Wed, 4 Jun 2014, Dan Beam wrote: > > On Wed, 4 Jun 2014, Dan Beam wrote: > >> > >> It'd be nice to avoid more attribute accessors (and encourage authors > >> to use getAttribute() instead), but if and have > >> them we should probably be consistent. > > > > Can you elaborate on the cost of attribute accessors? > > Namespace exhaustion (maybe form.autocomplete() would've worked instead > of requestAutocomplete() if autocomplete="" hadn't taken it?) I think it would have been very confusing to have a method with the same name as a content attribute. > multiple ways to do things (vs getAttribute) Well sure, but isn't the IDL attribute a lot cleaner-looking? > longer specs/IDLs/compile times. Surely authors' needs outweigh these. -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
