Revert of Refine the accessibility label of Clear Browsing Data flow.

Revert of Refine the accessibility label of Clear Browsing Data flow. (patchset #2 id:20001 of https://codereview.chromium.org/2750403002/ )

Reason for revert:
Caused a variety of EG test failures.
For example:
SettingsTestCase.testClearPasswords
SettingsTestCase.testClearPasswords:
../../ios/chrome/browser/ui/settings/settings_egtest.mm:294: error: -[SettingsTestCase testClearPasswords] : Exception: NoMatchingElementException

Exception Name: NoMatchingElementException
Exception Reason: Cannot find UI element.
Exception with Action: {
  "Action Name" : "Tap",
  "Element Matcher" : "((((respondsToSelector(isAccessibilityElement) && isAccessibilityElement) && accessibilityLabel('Clear Browsing Data')) && ((respondsToSelector(isAccessibilityElement) && isAccessibilityElement) && accessibilityTraits: UIAccessibilityTraitButton)) && !kindOfClass('MDCCollectionViewTextCell'))",
  "Recovery Suggestion" : "Check if element exists in the UI, modify assert criteria, or adjust the matcher"
}

Original issue's description:
> Refine the accessibility label of Clear Browsing Data flow.
> 
> When using VoiceOver, the user taps a button to Clear Browsing Data then
> gets on a new Clear Browsing Data button, which can be confusing.
> To make it more understandable, this CL changes the accessibility label
> of the second button to "Confirm Clear Browsing Data".
> 
> BUG=688415
> R=lindsayw@chromium.org
> 
> Review-Url: https://codereview.chromium.org/2750403002
> Cr-Commit-Position: refs/heads/master@{#458186}
> Committed: https://chromium.googlesource.com/chromium/src/+/cf84fa5c1519b0d0867d49071d3266004605d53b

TBR=lindsayw@chromium.org,noyau@chromium.org,olivierrobin@chromium.org,lpromero@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=688415
Review-Url: https://codereview.chromium.org/2763793002
Cr-Commit-Position: refs/heads/master@{#458234}
Committed: https://chromium.googlesource.com/chromium/src/+/b1cb679f18cefc5699f848827ba9b94751ec898c

[gchatz, 2017-03-20 23:24:06]

The CQ bit was checked by gchatz@chromium.org

[gchatz, 2017-03-20 23:24:06]

Created Revert of Refine the accessibility label of Clear Browsing Data flow.

[commit-bot: I haz the power, 2017-03-20 23:24:49]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-03-20 23:24:50]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-03-20 23:24:51]

No L-G-T-M from a valid reviewer yet.
CQ run can only be started once the patch has received an L-G-T-M from a full
committer.
Even if an L-G-T-M may have been provided, it was from a non-committer,_not_ a
full super star committer.
Committers are members of the group "project-chromium-committers".
Note that this has nothing to do with OWNERS files.

[edchin, 2017-03-20 23:25:58]

edchin@chromium.org changed reviewers:
+ edchin@chromium.org

[edchin, 2017-03-20 23:25:58]

lgtm

[gchatz, 2017-03-20 23:26:14]

The CQ bit was checked by gchatz@chromium.org

[commit-bot: I haz the power, 2017-03-20 23:27:02]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-03-20 23:28:31]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1490052374022020, "parent_rev":
"1af04705b43547c1b6fef0080c092aae06b1dca8", "commit_rev":
"b1cb679f18cefc5699f848827ba9b94751ec898c"}

[commit-bot: I haz the power, 2017-03-20 23:29:13]

Description was changed from

==========
Revert of Refine the accessibility label of Clear Browsing Data flow. (patchset
#2 id:20001 of https://codereview.chromium.org/2750403002/ )

Reason for revert:
Caused a variety of EG test failures.
For example:
SettingsTestCase.testClearPasswords
SettingsTestCase.testClearPasswords:
../../ios/chrome/browser/ui/settings/settings_egtest.mm:294: error:
-[SettingsTestCase testClearPasswords] : Exception: NoMatchingElementException

Exception Name: NoMatchingElementException
Exception Reason: Cannot find UI element.
Exception with Action: {
  "Action Name" : "Tap",
  "Element Matcher" : "((((respondsToSelector(isAccessibilityElement) &&
isAccessibilityElement) && accessibilityLabel('Clear Browsing Data')) &&
((respondsToSelector(isAccessibilityElement) && isAccessibilityElement) &&
accessibilityTraits: UIAccessibilityTraitButton)) &&
!kindOfClass('MDCCollectionViewTextCell'))",
  "Recovery Suggestion" : "Check if element exists in the UI, modify assert
criteria, or adjust the matcher"
}

Original issue's description:
> Refine the accessibility label of Clear Browsing Data flow.
> 
> When using VoiceOver, the user taps a button to Clear Browsing Data then
> gets on a new Clear Browsing Data button, which can be confusing.
> To make it more understandable, this CL changes the accessibility label
> of the second button to "Confirm Clear Browsing Data".
> 
> BUG=688415
> R=lindsayw@chromium.org
> 
> Review-Url: https://codereview.chromium.org/2750403002
> Cr-Commit-Position: refs/heads/master@{#458186}
> Committed:
https://chromium.googlesource.com/chromium/src/+/cf84fa5c1519b0d0867d49071d32...

TBR=lindsayw@chromium.org,noyau@chromium.org,olivierrobin@chromium.org,lprome...
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=688415
==========

to

==========
Revert of Refine the accessibility label of Clear Browsing Data flow. (patchset
#2 id:20001 of https://codereview.chromium.org/2750403002/ )

Reason for revert:
Caused a variety of EG test failures.
For example:
SettingsTestCase.testClearPasswords
SettingsTestCase.testClearPasswords:
../../ios/chrome/browser/ui/settings/settings_egtest.mm:294: error:
-[SettingsTestCase testClearPasswords] : Exception: NoMatchingElementException

Exception Name: NoMatchingElementException
Exception Reason: Cannot find UI element.
Exception with Action: {
  "Action Name" : "Tap",
  "Element Matcher" : "((((respondsToSelector(isAccessibilityElement) &&
isAccessibilityElement) && accessibilityLabel('Clear Browsing Data')) &&
((respondsToSelector(isAccessibilityElement) && isAccessibilityElement) &&
accessibilityTraits: UIAccessibilityTraitButton)) &&
!kindOfClass('MDCCollectionViewTextCell'))",
  "Recovery Suggestion" : "Check if element exists in the UI, modify assert
criteria, or adjust the matcher"
}

Original issue's description:
> Refine the accessibility label of Clear Browsing Data flow.
> 
> When using VoiceOver, the user taps a button to Clear Browsing Data then
> gets on a new Clear Browsing Data button, which can be confusing.
> To make it more understandable, this CL changes the accessibility label
> of the second button to "Confirm Clear Browsing Data".
> 
> BUG=688415
> R=lindsayw@chromium.org
> 
> Review-Url: https://codereview.chromium.org/2750403002
> Cr-Commit-Position: refs/heads/master@{#458186}
> Committed:
https://chromium.googlesource.com/chromium/src/+/cf84fa5c1519b0d0867d49071d32...

TBR=lindsayw@chromium.org,noyau@chromium.org,olivierrobin@chromium.org,lprome...
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=688415

Review-Url: https://codereview.chromium.org/2763793002
Cr-Commit-Position: refs/heads/master@{#458234}
Committed:
https://chromium.googlesource.com/chromium/src/+/b1cb679f18cefc5699f848827ba9...
==========

[commit-bot: I haz the power, 2017-03-20 23:29:14]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/b1cb679f18cefc5699f848827ba9...