|
|
Created:
6 years, 2 months ago by je_julie(Not used) Modified:
6 years, 2 months ago CC:
abarth-chromium, aboxhall, blink-reviews, dglazkov+blink, jamesr, mkwst+moarreviews_chromium.org Base URL:
https://chromium.googlesource.com/chromium/blink.git@master Project:
blink Visibility:
Public. |
DescriptionAdd AX attribute for input type
When Input type is url, tel, search and email,
AX attributes for them will be exposed.
BUG=323161
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=183119
Patch Set 1 #
Total comments: 4
Patch Set 2 : Move TextInputType to AXNodeObject #
Total comments: 3
Patch Set 3 : Using isTextField() #
Messages
Total messages: 25 (5 generated)
je_julie.kim@samsung.com changed reviewers: + darin@chromium.org, dmazzoni@chromium.org
Dominic, PTAL.
lgtm with changes below https://codereview.chromium.org/596393004/diff/1/Source/core/accessibility/AX... File Source/core/accessibility/AXObject.cpp (right): https://codereview.chromium.org/596393004/diff/1/Source/core/accessibility/AX... Source/core/accessibility/AXObject.cpp:634: const AtomicString& AXObject::textInputType() const This looks great, but please move it to AXNodeObject. In general, AXObject is supposed to contain logic that applies to all AX objects, AXNodeObject should handle things that depend on it being a DOM node, and AXRenderObject for things that may also depend on its RenderObject or exactly how it's laid out on the screen. Put an empty implementation here and override it in AXNodeObject. https://codereview.chromium.org/596393004/diff/1/Source/core/accessibility/AX... Source/core/accessibility/AXObject.cpp:640: if (!elementNode->isElementNode() ||!isHTMLInputElement(*elementNode)) nit: space between || and !
https://codereview.chromium.org/596393004/diff/1/Source/core/accessibility/AX... File Source/core/accessibility/AXObject.cpp (right): https://codereview.chromium.org/596393004/diff/1/Source/core/accessibility/AX... Source/core/accessibility/AXObject.cpp:634: const AtomicString& AXObject::textInputType() const Thanks. I'll update it. On 2014/09/26 15:17:26, dmazzoni wrote: > This looks great, but please move it to AXNodeObject. > > In general, AXObject is supposed to contain logic that applies to all AX > objects, AXNodeObject should handle things that depend on it being a DOM node, > and AXRenderObject for things that may also depend on its RenderObject or > exactly how it's laid out on the screen. > > Put an empty implementation here and override it in AXNodeObject. https://codereview.chromium.org/596393004/diff/1/Source/core/accessibility/AX... Source/core/accessibility/AXObject.cpp:640: if (!elementNode->isElementNode() ||!isHTMLInputElement(*elementNode)) Thanks, I'll update it. On 2014/09/26 15:17:26, dmazzoni wrote: > nit: space between || and !
Hi Dominic, I updated patch. PTAL.
The CQ bit was checked by dmazzoni@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/596393004/20001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: blink_presubmit on tryserver.blink (http://build.chromium.org/p/tryserver.blink/builders/blink_presubmit/builds/1...)
On 2014/09/29 05:57:18, I haz the power (commit-bot) wrote: > Try jobs failed on following builders: > blink_presubmit on tryserver.blink > (http://build.chromium.org/p/tryserver.blink/builders/blink_presubmit/builds/1...) Hi Dominic, I saw error below with blink_presubmit. ** Presubmit ERRORS ** Missing LGTM from an OWNER for these files: Source/web/WebAXObject.cpp public/web/WebAXObject.h Do you have any idea how to handle it?
dmazzoni@chromium.org changed reviewers: + dglazkov@chromium.org - darin@chromium.org
+dglazkov for owners review of public/web and src/web
On 2014/09/29 07:02:21, dmazzoni wrote: > +dglazkov for owners review of public/web and src/web Hi dglazkov, PTAL.
lgtm
https://codereview.chromium.org/596393004/diff/20001/Source/core/accessibilit... File Source/core/accessibility/AXNodeObject.cpp (right): https://codereview.chromium.org/596393004/diff/20001/Source/core/accessibilit... Source/core/accessibility/AXNodeObject.cpp:1052: if (input.type() == InputTypeNames::tel || input.type() == InputTypeNames::url Should this just be input.isTextField()?
https://codereview.chromium.org/596393004/diff/20001/Source/core/accessibilit... File Source/core/accessibility/AXNodeObject.cpp (right): https://codereview.chromium.org/596393004/diff/20001/Source/core/accessibilit... Source/core/accessibility/AXNodeObject.cpp:1052: if (input.type() == InputTypeNames::tel || input.type() == InputTypeNames::url On 2014/10/01 04:37:11, dglazkov wrote: > Should this just be input.isTextField()? I'm referencing to implementation from FireFox for this. https://bugzilla.mozilla.org/show_bug.cgi?id=924896 They handle text input type with just tel, url, email and search because it's worthy of exporting to attribute. If we use isTextField(), it includes email, password, search, tel, text, and URL types. Do we need to include all of them?
https://codereview.chromium.org/596393004/diff/20001/Source/core/accessibilit... File Source/core/accessibility/AXNodeObject.cpp (right): https://codereview.chromium.org/596393004/diff/20001/Source/core/accessibilit... Source/core/accessibility/AXNodeObject.cpp:1052: if (input.type() == InputTypeNames::tel || input.type() == InputTypeNames::url On 2014/10/01 04:53:52, je_julie.kim wrote: > On 2014/10/01 04:37:11, dglazkov wrote: > > Should this just be input.isTextField()? > > I'm referencing to implementation from FireFox for this. > https://bugzilla.mozilla.org/show_bug.cgi?id=924896 > They handle text input type with just tel, url, email and search because it's > worthy of exporting to attribute. > If we use isTextField(), it includes email, password, search, tel, text, and URL > types. > Do we need to include all of them? I think isTextField is probably more correct. Search and Password seem useful to return too, and plus that's probably more future-proof if more are added later. If one of them is not allowed to be returned on a particular platform, let's handle it there.
On 2014/10/01 05:22:57, dmazzoni wrote: > https://codereview.chromium.org/596393004/diff/20001/Source/core/accessibilit... > File Source/core/accessibility/AXNodeObject.cpp (right): > > https://codereview.chromium.org/596393004/diff/20001/Source/core/accessibilit... > Source/core/accessibility/AXNodeObject.cpp:1052: if (input.type() == > InputTypeNames::tel || input.type() == InputTypeNames::url > On 2014/10/01 04:53:52, je_julie.kim wrote: > > On 2014/10/01 04:37:11, dglazkov wrote: > > > Should this just be input.isTextField()? > > > > I'm referencing to implementation from FireFox for this. > > https://bugzilla.mozilla.org/show_bug.cgi?id=924896 > > They handle text input type with just tel, url, email and search because it's > > worthy of exporting to attribute. > > If we use isTextField(), it includes email, password, search, tel, text, and > URL > > types. > > Do we need to include all of them? > > I think isTextField is probably more correct. Search and Password seem useful to > return too, and plus that's probably more future-proof if more are added later. > > If one of them is not allowed to be returned on a particular platform, let's > handle it there. OK, I'll update patch here and also update test result at https://codereview.chromium.org/559343002/. Text and Password type will also generate text-input-type attribute.
On 2014/10/01 05:28:52, je_julie.kim wrote: > On 2014/10/01 05:22:57, dmazzoni wrote: > > > https://codereview.chromium.org/596393004/diff/20001/Source/core/accessibilit... > > File Source/core/accessibility/AXNodeObject.cpp (right): > > > > > https://codereview.chromium.org/596393004/diff/20001/Source/core/accessibilit... > > Source/core/accessibility/AXNodeObject.cpp:1052: if (input.type() == > > InputTypeNames::tel || input.type() == InputTypeNames::url > > On 2014/10/01 04:53:52, je_julie.kim wrote: > > > On 2014/10/01 04:37:11, dglazkov wrote: > > > > Should this just be input.isTextField()? > > > > > > I'm referencing to implementation from FireFox for this. > > > https://bugzilla.mozilla.org/show_bug.cgi?id=924896 > > > They handle text input type with just tel, url, email and search because > it's > > > worthy of exporting to attribute. > > > If we use isTextField(), it includes email, password, search, tel, text, and > > URL > > > types. > > > Do we need to include all of them? > > > > I think isTextField is probably more correct. Search and Password seem useful > to > > return too, and plus that's probably more future-proof if more are added > later. > > > > If one of them is not allowed to be returned on a particular platform, let's > > handle it there. > > OK, I'll update patch here and also update test result at > https://codereview.chromium.org/559343002/. > Text and Password type will also generate text-input-type attribute. Dominic, dglazkov, PTAL.
still lgtm
dglazkov, I updated patch with isTextField() as you commented. Could you take a look one more?
On 2014/10/02 00:22:55, je_julie.kim wrote: > dglazkov, I updated patch with isTextField() as you commented. > Could you take a look one more? He already said lgtm with his review so you don't need to wait for a second lgtm.
The CQ bit was checked by dmazzoni@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/596393004/40001
Message was sent while issue was closed.
Committed patchset #3 (id:40001) as 183119 |