Automated Commit: Committing new LKGM version 5274.0.0 for chromeos.

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@246241 0039d316-1c4b-4281-b951-d872f2087c98
PerformRemoveAction in account_reconcilor.

BUG=305249

Review URL: https://codereview.chromium.org/93593006

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@246242 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 246242
NSS Certificate Manager: Use NSSCertDatabaseChromeOS.

BUG=218643

Review URL: https://codereview.chromium.org/105663004

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@246243 0039d316-1c4b-4281-b951-d872f2087c98
Linux Aura: Added --use-system-title-bar flag.

This flag makes browser windows use the system window dressing and title
bar, instead of the custom frame. This is a Linux Aura equivalent of the
"Use System Title Bar and Border" preference in Linux GTK. (Eventually,
this part will be controlled by the same preference, rather than this
flag.)

With this flag, browser windows use the native system window decoration,
with our custom close/minimize/maximize buttons removed, and the tab
strip being condensed vertically with square corners (like the maximized
tab strip).  Popup browser windows (including V1 apps and the Developer
Tools window) drop the blue custom frame altogether in favour of the
native frame.

BUG=317859
TEST=With --use-system-title-bar, open a browser window. Both maximized
and restored windows should have a system native title bar, and the tab
strip should be compacted into a single row (as when maximized).
TEST=With --use-system-title-bar, open a hosted app window. It should
have a system native title bar, with no second blue title bar.

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=245433

Review URL: https://codereview.chromium.org/111723012

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@246244 0039d316-1c4b-4281-b951-d872f2087c98
IndexedDB: Only reset prefetch caches for cursors in same transaction

Correct prefetching is predicated on resetting the cache when other
requests come in that could invalidate it (i.e. writes) or result in
requests processing out of order (i.e. everything). When prefetching
was originally implemented, the IDB implementation only handled one
transaction at a time, so resetting was done with a big hammer - reset
all of a front-end's caches when any other request is made. This was
acknowledged as future work during code review.

The future is now! Only reset caches for cursors from the same
transaction as the triggering request, which should be a performance
win for concurrent transactions in the same front-end.

BUG=329950

Review URL: https://codereview.chromium.org/128713006

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@246245 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 246245