lgtm Thanks for getting to this so quickly. https://codereview.chromium.org/2306383005/diff/20001/third_party/WebKit/Source/modules/accessibility/AXLayoutObject.cpp File third_party/WebKit/Source/modules/accessibility/AXLayoutObject.cpp (left): https://codereview.chromium.org/2306383005/diff/20001/third_party/WebKit/Source/modules/accessibility/AXLayoutObject.cpp#oldcode1331 third_party/WebKit/Source/modules/accessibility/AXLayoutObject.cpp:1331: // ...
4 years, 3 months ago
(2016-09-06 22:39:53 UTC)
#4
4 years, 3 months ago
(2016-09-06 22:49:54 UTC)
#5
ttps://codereview.chromium.org/2306383005/diff/20001/third_party/WebKit/Source/modules/accessibility/AXLayoutObject.cpp
<https://codereview.chromium.org/2306383005/diff/20001/third_party/WebKit/Sour...>
> File third_party/WebKit/Source/modules/accessibility/AXLayoutObject.cpp
> (left):
>
>
https://codereview.chromium.org/2306383005/diff/20001/third_party/WebKit/Sour...
> third_party/WebKit/Source/modules/accessibility/AXLayoutObject.cpp:1331:
> // case SeparatorRole:
> Is this an unrelated change?
Sorry, I thought I reverted that.
I'll send out this in a different patch.
--
You received this message because you are subscribed to the Google Groups "Blink
Reviews" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to blink-reviews+unsubscribe@chromium.org.
4 years, 3 months ago
(2016-09-06 22:49:54 UTC)
#6
ttps://codereview.chromium.org/2306383005/diff/20001/third_party/WebKit/Source/modules/accessibility/AXLayoutObject.cpp
<https://codereview.chromium.org/2306383005/diff/20001/third_party/WebKit/Sour...>
> File third_party/WebKit/Source/modules/accessibility/AXLayoutObject.cpp
> (left):
>
>
https://codereview.chromium.org/2306383005/diff/20001/third_party/WebKit/Sour...
> third_party/WebKit/Source/modules/accessibility/AXLayoutObject.cpp:1331:
> // case SeparatorRole:
> Is this an unrelated change?
Sorry, I thought I reverted that.
I'll send out this in a different patch.
--
You received this message because you are subscribed to the Google Groups
"Chromium-reviews" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to chromium-reviews+unsubscribe@chromium.org.
nektarios
The CQ bit was checked by nektar@chromium.org
4 years, 3 months ago
(2016-09-06 22:59:18 UTC)
#7
Try jobs failed on following builders: chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presubmit/builds/253931)
4 years, 3 months ago
(2016-09-06 23:09:58 UTC)
#11
Description was changed from ========== Made date input field read "mm", "dd", "yyyy", or equivalents ...
4 years, 3 months ago
(2016-09-06 23:30:37 UTC)
#12
Description was changed from
==========
Made date input field read "mm", "dd", "yyyy", or equivalents in other
languages, instead of "blank" when no date has been selected.
This matches visual experience, as well as screen reader experience in Firefox.
BUG=643423
R=dtseng@chromium.org
TESTED=manually with Jaws
==========
to
==========
Made date input field read "mm", "dd", "yyyy", or equivalents in other
languages, instead of "blank" when no date has been selected.
This matches visual experience, as well as screen reader experience on many
websites.
BUG=643423
R=dtseng@chromium.org, esprehn@chromium.org
TESTED=manually with Jaws
==========
Description was changed from ========== Made date input field read "mm", "dd", "yyyy", or equivalents ...
4 years, 3 months ago
(2016-09-06 23:32:08 UTC)
#14
Description was changed from
==========
Made date input field read "mm", "dd", "yyyy", or equivalents in other
languages, instead of "blank" when no date has been selected.
This matches visual experience, as well as screen reader experience on many
websites.
BUG=643423
R=dtseng@chromium.org, esprehn@chromium.org
TESTED=manually with Jaws
==========
to
==========
Made date input field read "mm", "dd", "yyyy", or equivalents in other
languages, instead of "blank" when no date has been selected.
This matches visual experience, as well as screen reader experience on many
websites.
BUG=643423
R=dtseng@chromium.org, esprehn@chromium.org, keishi@chromium.org,
tkent@chromium.org
TESTED=manually with Jaws
==========
@esprehn Please review changes to content/child/ @tkent or @keishi Please review a small change to ...
4 years, 3 months ago
(2016-09-06 23:33:51 UTC)
#16
@esprehn
Please review changes to content/child/
@tkent or @keishi
Please review a small change to the date input field.
tkent
lgtm. I'm wonder if reading 'mm' would be helpful. However I trust AX team decision.
4 years, 3 months ago
(2016-09-06 23:57:16 UTC)
#17
lgtm.
I'm wonder if reading 'mm' would be helpful. However I trust AX team decision.
esprehn
Got some tests? :)
4 years, 3 months ago
(2016-09-06 23:57:28 UTC)
#18
Got some tests? :)
tkent
Some tests in LayoutTests/fast/forms/ are failing. Need to update them.
4 years, 3 months ago
(2016-09-07 00:00:12 UTC)
#19
Some tests in LayoutTests/fast/forms/ are failing. Need to update them.
chromium-reviews
On 9/6/2016 7:57 PM, tkent@chromium.org wrote: > lgtm. > I'm wonder if reading 'mm' would ...
4 years, 3 months ago
(2016-09-07 00:36:08 UTC)
#20
On 9/6/2016 7:57 PM, tkent@chromium.org wrote:
> lgtm.
> I'm wonder if reading 'mm' would be helpful. However I trust AX team
> decision.
Just FYI.
I believe it is because it matches visual experience. If something
doesn't match the visual experience then users who use screen readers
can't easily collaborate with users who don't.
Also, "mm", "dd" and "yyyy" are very prevalent. They are on almost all
websites I ever visited that have a custom date picker so they shouldn't
cause surprise.
"Blank" however creates some surprise, and in fact a bug was filed about it.
--
You received this message because you are subscribed to the Google Groups
"Chromium-reviews" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to chromium-reviews+unsubscribe@chromium.org.
blink-reviews
On 9/6/2016 7:57 PM, tkent@chromium.org wrote: > lgtm. > I'm wonder if reading 'mm' would ...
4 years, 3 months ago
(2016-09-07 00:36:11 UTC)
#21
On 9/6/2016 7:57 PM, tkent@chromium.org wrote:
> lgtm.
> I'm wonder if reading 'mm' would be helpful. However I trust AX team
> decision.
Just FYI.
I believe it is because it matches visual experience. If something
doesn't match the visual experience then users who use screen readers
can't easily collaborate with users who don't.
Also, "mm", "dd" and "yyyy" are very prevalent. They are on almost all
websites I ever visited that have a custom date picker so they shouldn't
cause surprise.
"Blank" however creates some surprise, and in fact a bug was filed about it.
--
You received this message because you are subscribed to the Google Groups "Blink
Reviews" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to blink-reviews+unsubscribe@chromium.org.
blink-reviews
Tests fixed. I think they should be enough for coverage, do you agree? -- You ...
4 years, 3 months ago
(2016-09-07 01:26:55 UTC)
#22
Tests fixed. I think they should be enough for coverage, do you agree?
--
You received this message because you are subscribed to the Google Groups "Blink
Reviews" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to blink-reviews+unsubscribe@chromium.org.
chromium-reviews
Tests fixed. I think they should be enough for coverage, do you agree? -- You ...
4 years, 3 months ago
(2016-09-07 01:27:04 UTC)
#23
Tests fixed. I think they should be enough for coverage, do you agree?
--
You received this message because you are subscribed to the Google Groups
"Chromium-reviews" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to chromium-reviews+unsubscribe@chromium.org.
tkent
On 2016/09/07 at 01:27:04, chromium-reviews wrote: > Tests fixed. I think they should be enough ...
4 years, 3 months ago
(2016-09-07 01:41:32 UTC)
#24
On 2016/09/07 at 01:27:04, chromium-reviews wrote:
> Tests fixed. I think they should be enough for coverage, do you agree?
agree. still lgtm
nektarios
The CQ bit was checked by nektar@chromium.org to run a CQ dry run
4 years, 3 months ago
(2016-09-07 15:46:45 UTC)
#25
Dry run: Try jobs failed on following builders: win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_ng/builds/288802)
4 years, 3 months ago
(2016-09-07 17:24:25 UTC)
#28
Try jobs failed on following builders: chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presubmit/builds/254744)
4 years, 3 months ago
(2016-09-07 19:39:59 UTC)
#33
@tkent Have you given me an LGTM. I think I am still missing an LGTM ...
4 years, 3 months ago
(2016-09-07 20:16:00 UTC)
#34
@tkent
Have you given me an LGTM. I think I am still missing an LGTM from somewhere.
nektarios
Description was changed from ========== Made date input field read "mm", "dd", "yyyy", or equivalents ...
4 years, 3 months ago
(2016-09-07 20:18:07 UTC)
#35
Description was changed from
==========
Made date input field read "mm", "dd", "yyyy", or equivalents in other
languages, instead of "blank" when no date has been selected.
This matches visual experience, as well as screen reader experience on many
websites.
BUG=643423
R=dtseng@chromium.org, esprehn@chromium.org, keishi@chromium.org,
tkent@chromium.org
TESTED=manually with Jaws
==========
to
==========
Made date input field read "mm", "dd", "yyyy", or equivalents in other
languages, instead of "blank" when no date has been selected.
This matches visual experience, as well as screen reader experience on many
websites.
BUG=643423
R=dtseng@chromium.org, esprehn@chromium.org, keishi@chromium.org,
tkent@chromium.org, avi@chromium.org
TESTED=manually with Jaws
==========
Issue 2306383005: Made date input field read "mm", "dd", "yyyy", or equivalents in other languages, instead of "blank…
(Closed)
Created 4 years, 3 months ago by nektarios
Modified 4 years, 3 months ago
Reviewers: Avi (use Gerrit), David Tseng, esprehn, keishi, tkent
Base URL:
Comments: 1