[C++11 Allowed Features] Declares a type-safe null pointer converting from NULL to nullptr

content/browser/accessibility/accessibility_mode_browsertest.cc

Index: content/browser/accessibility/accessibility_mode_browsertest.cc
diff --git a/content/browser/accessibility/accessibility_mode_browsertest.cc b/content/browser/accessibility/accessibility_mode_browsertest.cc
index 656e009783ab9432ecd11eb5c4dac07b8dfa2ae3..c9f3cbc140e67a92d509b6c09584d26e0e04da87 100644
--- a/content/browser/accessibility/accessibility_mode_browsertest.cc
+++ b/content/browser/accessibility/accessibility_mode_browsertest.cc
@@ -33,11 +33,11 @@ class AccessibilityModeTest : public ContentBrowserTest {
                                          std::string message = "") {
     if (expect_bam) {
       EXPECT_NE(
-          (BrowserAccessibilityManager*)NULL,
+          (BrowserAccessibilityManager*)nullptr,

[dmazzoni, 2014/10/10 16:49:49]

Is the typecast still necessary when we use nullptr? I expect it isn't. Please
try removing the typecast whenever NULL was used inside an EXPECT or ASSERT
assertion in a test.

           web_contents()->GetRootBrowserAccessibilityManager()) << message;
     } else {
       EXPECT_EQ(
-          (BrowserAccessibilityManager*)NULL,
+          (BrowserAccessibilityManager*)nullptr,
           web_contents()->GetRootBrowserAccessibilityManager()) << message;
     }
   }