This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
input type text, email, tel etc have own descriptions, it should be nice to combine them into one item (note, these elements in case of autocomplete share the same description). Sounds good?
(In reply to comment #0) > input type text, email, tel etc have own descriptions, it should be nice to > combine them into one item (note, these elements in case of autocomplete > share the same description). Sounds good? Possibly. input type search has a different AXRoleDescription. I wouldn't be surprised if things like type email and tel get different AXRoleDescriptions somewhere along the way. Perhaps we can leave them for now, until we can be certain which input types will have identical mappings across all APIs, and then at that time combine those that do into a single entry?
(In reply to comment #1) > (In reply to comment #0) > > input type text, email, tel etc have own descriptions, it should be nice to > > combine them into one item (note, these elements in case of autocomplete > > share the same description). Sounds good? > > Possibly. input type search has a different AXRoleDescription. I wouldn't be > surprised if things like type email and tel get different AXRoleDescriptions > somewhere along the way. Perhaps we can leave them for now, until we can be > certain which input types will have identical mappings across all APIs, and > then at that time combine those that do into a single entry? ok, makes sense, then the same must applicable to these controls having associated autocomplets, currently they are merged into single item
(In reply to comment #1) > (In reply to comment #0) > > input type text, email, tel etc have own descriptions, it should be nice to > > combine them into one item (note, these elements in case of autocomplete > > share the same description). Sounds good? > > Possibly. input type search has a different AXRoleDescription. I wouldn't be > surprised if things like type email and tel get different AXRoleDescriptions > somewhere along the way. Perhaps we can leave them for now, until we can be > certain which input types will have identical mappings across all APIs, and > then at that time combine those that do into a single entry? agree with jason here as UI may differ dependent type
(In reply to comment #2) > ok, makes sense, then the same must applicable to these controls having > associated autocomplets, currently they are merged into single item That makes sense. I propose we wait until after heartbeat then confirm appropriate mappings and split into separate mappings where necessary.