From 9650eff615a19f2cda06760b2e475b24e8faae2b Mon Sep 17 00:00:00 2001 From: Allan Sandfeld Jensen Date: Fri, 8 Feb 2019 13:13:08 +0100 Subject: Fix misuse of {} initialization Narrowing is supposed to be forbidden in {} initialization, but Chromium doesn't appear to care upstream. Change-Id: Ia3d1dac6ef19ef86afcbeee4ed11d807c53faaaa Reviewed-by: Michal Klocek --- chromium/content/browser/accessibility/browser_accessibility_manager.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'chromium/content/browser/accessibility/browser_accessibility_manager.cc') diff --git a/chromium/content/browser/accessibility/browser_accessibility_manager.cc b/chromium/content/browser/accessibility/browser_accessibility_manager.cc index 572b0e94433..e891c6ea4d1 100644 --- a/chromium/content/browser/accessibility/browser_accessibility_manager.cc +++ b/chromium/content/browser/accessibility/browser_accessibility_manager.cc @@ -438,7 +438,7 @@ bool BrowserAccessibilityManager::OnAccessibilityEvents( // means a node just got repeated or something harmless like that, // but it should still be investigated and could be the sign of a // performance issue. - DCHECK_LE(int{tree_update.nodes.size()}, ax_tree()->size()); + DCHECK_LE(int(tree_update.nodes.size()), ax_tree()->size()); } // If this page is hidden by an interstitial, suppress all events. -- cgit v1.2.1