[omnibox] Stop hardcoding ChromeOS launcher to have no default match
It seems that in the past, we've hardcoded the ChromeOS launcher page context to have no default match. But that seems unnecessary, since nothing in chrome/browser/ui/app_list even looks at the default_match() member. I'm removing this because we want to keep the Autocomplete controller as generic as possible without any special cases. ChromeOS launcher can simply ignore the default match if it wants to, and indeed it seems to. The goal of this CL is to unblock removing the default_match_ member variable entirely, since it's always equal to results_.begin() if that first match has |allowed_to_be_default_match| set to true. Bug: 1016845, 363656 Change-Id: Ifd9f72c71c20b3e49bc4fa006353d980f7ba55a3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1913559Reviewed-by:Jenny Zhang <jennyz@chromium.org> Commit-Queue: Tommy Li <tommycli@chromium.org> Cr-Commit-Position: refs/heads/master@{#715521}
Showing
Please register or sign in to comment