- 15 Feb, 2014 40 commits
-
-
mallinath@chromium.org authored
Roll webrtc to r5549. Major change in this revision is addition of PacketOptions structure to every packet sent over network in AsyncPacketSocket::Send methods. This structure has information about parameters required for packet authentication outside libsrtp. R=ronghuawu@chromium.org, sergeyu@chromium.org Review URL: https://codereview.chromium.org/167893002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251548 0039d316-1c4b-4281-b951-d872f2087c98
-
shashishekhar@chromium.org authored
In order to support distillation of previous pages and enable meaningful incremental updates for viewers, distiller needs to maintain page number information for pages under distillation. This information will be used to add support for incremental updates and distilling previous pages of an article. BUG=288015 TEST=Covered by existing tests + added tests for failure and page limit for distiller. Review URL: https://codereview.chromium.org/130543003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251546 0039d316-1c4b-4281-b951-d872f2087c98
-
mattm@chromium.org authored
BUG=none Review URL: https://codereview.chromium.org/166223004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251545 0039d316-1c4b-4281-b951-d872f2087c98
-
epenner@chromium.org authored
We now have a soft limit, so we adjust some memory limits up, and enable the soft-limit to bring the effective usage down. Initially we bump most limits up a bit (except for really high-end which is already at 256MB), and then we cut the soft limit to 50% of that. For low-end, to be extra careful we only increase the limit from 8MB to 12MB, and set the soft limit back to 8MB. BUG=337940,273127 TBR=piman@chromium.org Review URL: https://codereview.chromium.org/168053002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251544 0039d316-1c4b-4281-b951-d872f2087c98
-
koss@chromium.org authored
Test tuns without errors or warning on my machine. BUG=163931 Review URL: https://codereview.chromium.org/163433014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251543 0039d316-1c4b-4281-b951-d872f2087c98
-
jamescook@chromium.org authored
* Rename ShellWindowRegistry * Rename ShellWindowGeometryCache * Rename members like shell_window_ to app_window_ * Rename locals like shell_window to app_window BUG=343591 TEST=compiles COLLABORATOR=scheib@chromium.org TBR=skuhne@chromium.org for chrome/browser/ui/ash/launcher TBR=thakis@chromium.org for chrome/browser/ui/cocoa TBR=erg@chromium.org for chrome/browser/ui/gtk TBR=sky@chromium.org for chrome/test Review URL: https://codereview.chromium.org/166573005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251542 0039d316-1c4b-4281-b951-d872f2087c98
-
vandebo@chromium.org authored
Since adding the preferences observer, RevokeOldGalleries() has been dead code. BUG=NONE Review URL: https://codereview.chromium.org/164983006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251541 0039d316-1c4b-4281-b951-d872f2087c98
-
skuhne@chromium.org authored
BUG=343715 TEST=visual Review URL: https://codereview.chromium.org/168033002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251540 0039d316-1c4b-4281-b951-d872f2087c98
-
oshima@chromium.org authored
* Introduced WindowStateObserver::{Pre|Post}WindowShowTypeChange We had implicit dependency between OnWindowShowTypeChanged implementations. This clearly separate the things that should happen before and after the window's bounds is updated. This is another step to introduce state machine. BUG=318325 TEST=no functional change. all tests should pass. TBR=benwells@chromium.org Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=251191 Review URL: https://codereview.chromium.org/149303003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251539 0039d316-1c4b-4281-b951-d872f2087c98
-
danakj@chromium.org authored
The ui flag is always true on ChromeOS and off elsewhere. The other is never on and we're not planning to turn it on. R=piman BUG= Review URL: https://codereview.chromium.org/164183012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251538 0039d316-1c4b-4281-b951-d872f2087c98
-
samarth@chromium.org authored
BUG=333397 Review URL: https://codereview.chromium.org/135383002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251537 0039d316-1c4b-4281-b951-d872f2087c98
-
scottmg@chromium.org authored
R=thakis@chromium.org Review URL: https://codereview.chromium.org/167943002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251536 0039d316-1c4b-4281-b951-d872f2087c98
-
jianli@chromium.org authored
We should only require the manifest key for gcm.register. A meaningful error should also be returned. BUG=344027 TEST=tests updated and new test added Review URL: https://codereview.chromium.org/167063004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251535 0039d316-1c4b-4281-b951-d872f2087c98
-
mad@chromium.org authored
BUG= Review URL: https://codereview.chromium.org/167453002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251534 0039d316-1c4b-4281-b951-d872f2087c98
-
tdresser@chromium.org authored
This implements (In Clank) the touch disposition handling method outlined here: https://docs.google.com/a/chromium.org/document/d/176xYUC3WbiSl7qd08SBW4NiI4_gO0N4PN6tPAq49-68/edit?pli=1#bookmark=id.wu82d53abe2w We also modify the way in which Aura handles touch move events to line up with the new way Android handles them. That is, consuming a touch move event prevents the next scroll update event, but does not prevent future scroll update events. This change will have little impact until https://codereview.chromium.org/166923002/ has landed. BUG=328503 Review URL: https://codereview.chromium.org/156783006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251533 0039d316-1c4b-4281-b951-d872f2087c98
-
rkaplow@chromium.org authored
On mobile this will launch a (slightly delayed) request, iff the seed hasn't been refreshed in the past 5 hours. On desktop this will use the currently existing method on desktop, which does not do that check. BUG=321379 Review URL: https://codereview.chromium.org/147723010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251532 0039d316-1c4b-4281-b951-d872f2087c98
-
dnicoara@chromium.org authored
On Ozone font rendering is disabled. The test cannot get the string width without a valid font. NOTRY=true BUG=320050 Review URL: https://codereview.chromium.org/167393003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251531 0039d316-1c4b-4281-b951-d872f2087c98
-
weitaosu@chromium.org authored
1. Don't close the delegate read/write handles twice in the me2me native messaging host. The handles are already closed by the native messaging channel in DuplicateHandle. 2. Keep the host alive and send a false response to the client if the user rejects the UAC request. 3. Added some comments. BUG=325567 Review URL: https://codereview.chromium.org/165363002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251529 0039d316-1c4b-4281-b951-d872f2087c98
-
mangini@chromium.org authored
NOTRY=true R=kalman@chromium.org Review URL: https://codereview.chromium.org/166073007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251528 0039d316-1c4b-4281-b951-d872f2087c98
-
rsleevi@chromium.org authored
BUG=none R=wtc@chromium.org, phajdan.jr@chromium.org TBR=willchan Review URL: https://codereview.chromium.org/167693002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251527 0039d316-1c4b-4281-b951-d872f2087c98
-
pshenoy@chromium.org authored
Disable FirstRunMasterPrefsWithTrackedPreferences.TrackedPreferencesSurviveFirstRun on Linux on official builder. See below issues for details. http://crbug.com/342427 http://crbug.com/314221 BUG=342427,314221 Review URL: https://codereview.chromium.org/163613003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251526 0039d316-1c4b-4281-b951-d872f2087c98
-
pmarch@chromium.org authored
BUG=344042 Review URL: https://codereview.chromium.org/166233006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251525 0039d316-1c4b-4281-b951-d872f2087c98
-
chrome-admin@google.com authored
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251524 0039d316-1c4b-4281-b951-d872f2087c98
-
eseidel@chromium.org authored
http://build.chromium.org/f/chromium/perf/dashboard/ui/changelog_blink.html?url=/trunk&range=167111:167223&mode=html TBR= BUG= Review URL: https://codereview.chromium.org/167473004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251523 0039d316-1c4b-4281-b951-d872f2087c98
-
xiyuan@chromium.org authored
> cros: Enable multiprofile for everyone. > > BUG=338941 > R=dpolukhin@chromium.org, nkostylev@chromium.org R=dpolukhin@chromium.org, nkostylev@chromium.org Review URL: https://codereview.chromium.org/146193005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251522 0039d316-1c4b-4281-b951-d872f2087c98
-
imcheng@chromium.org authored
All raw events are categorized into one of three types: video, audio, or other (i.e. not associated with a particular stream). EncodingEventSubscriber can be configured to only process either audio or video events. The subscriber can also be configured on having a max limit on number of frames to store in the frame and packet maps. This helps bound the memory usage of logging and the size of the blob we are uploading at the end. How they are going to be used: for each CastRtpStream (one audio, one video) we will install a EncodingEventSubscriber, listening to AUDIO / VIDEO events respectively. The number of events to store is yet to be determined and is dependent on how well the data can be compressed, or what's the size limit for uploading. Lastly, EncodingEventSubscriber has been changed to only process frame and packet related events and not generic events. We are not interested in generic events right now, and they can be computed from frame / packet events anyways. Review URL: https://codereview.chromium.org/165723002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251521 0039d316-1c4b-4281-b951-d872f2087c98
-
estade@chromium.org authored
BUG=340905 TBR=aruslan@chromium.org Review URL: https://codereview.chromium.org/151383003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251520 0039d316-1c4b-4281-b951-d872f2087c98
-
enne@chromium.org authored
BUG=none Review URL: https://codereview.chromium.org/166073008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251519 0039d316-1c4b-4281-b951-d872f2087c98
-
hans@chromium.org authored
We're bringing the regular Clang-based ASan to Windows and will put it behind asan==1 like on all other platforms. BUG=343960 Review URL: https://codereview.chromium.org/167773002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251518 0039d316-1c4b-4281-b951-d872f2087c98
-
dbeam@chromium.org authored
BUG=342990 TEST=no more crashes R=estade@chromium.org Review URL: https://codereview.chromium.org/165223002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251517 0039d316-1c4b-4281-b951-d872f2087c98
-
msw@chromium.org authored
BUG=343852 TEST=With a clear selection clipboard on Linux Aura; type "chrome://apps"+[ENTER]; open a new tab and middle click in the empty omnibox; no text should be pasted. No selection/update or other Omnibox behavior regressions. R=pkasting@chromium.org Review URL: https://codereview.chromium.org/164753008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251516 0039d316-1c4b-4281-b951-d872f2087c98
-
thestig@chromium.org authored
TBR=vandebo@chromium.org Review URL: https://codereview.chromium.org/168303004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251513 0039d316-1c4b-4281-b951-d872f2087c98
-
thestig@chromium.org authored
TBR=vandebo@chromium.org Review URL: https://codereview.chromium.org/167423003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251512 0039d316-1c4b-4281-b951-d872f2087c98
-
chrome-release@google.com authored
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251509 0039d316-1c4b-4281-b951-d872f2087c98
-
gab@chromium.org authored
R=nduca BUG=343692 Review URL: https://codereview.chromium.org/165123003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251506 0039d316-1c4b-4281-b951-d872f2087c98
-
thestig@chromium.org authored
Fix lint errors too. Review URL: https://codereview.chromium.org/166243002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251505 0039d316-1c4b-4281-b951-d872f2087c98
-
thestig@chromium.org authored
Review URL: https://codereview.chromium.org/166353002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251504 0039d316-1c4b-4281-b951-d872f2087c98
-
rogerta@chromium.org authored
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= This is a dup of https://codereview.chromium.org/130963006/ since I cannot upload to that issue. The only change is to address Xiyuan's two comments in patchset 3 of that CL. =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= Inline signin chrome://chrome-signin is currently implemented using webview embedded in webUI, which breaks a couple of features in webUI and has serious accessbility issues. Since webview will be reimplemented based on OOPIF in the near future, and all the issues we have today will no longer apply, thus it is not worth the effort to fix them as they are throw away work. Instead, as suggested by John and prototyped in https://codereview.chromium.org/141363006/, we decide to switch to iframe instead. A few issues worth to mention, 1. The iframe shares the same renderer as the embedder webUI, and thus could be potentially exposed to dangerous webUI privileges. John suggested a fix by assigning a unique storage partition ID to the inline signin page. As a result the inline signin and its embedded web content should never share the same renderer with other webUI pages. 2. webview provides a direct API to inject script and to monitor requests/responses, which is not (directly) available with iframe. The CL works around the issue using content script and background script, quite similar to what CrOS is doing for SAML flow today. Thus it is also the first step towards unifying SAML flows on CrOS and desktop. 3. with webview approach, we used to have a unique temporary partition for each instance of inline signin, in order to make sure multiple instances do not interfere with each other. This is more difficult with the iframe approach, since the partition ID is hardcoded in a quite low layer. In this CL, all inline signin pages share the same persistent partition, which means we have to handle the case when user loads the sign in page with a dirty cookie jar, and thus the newly connected user may not be stored in the primary session. The CL solves the issue by reading 'session_index' from 'google-accounts-signin' header. BUG=338127 Review URL: https://codereview.chromium.org/134263005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251503 0039d316-1c4b-4281-b951-d872f2087c98
-
stevenjb@chromium.org authored
BUG=329738 Review URL: https://codereview.chromium.org/156353002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251501 0039d316-1c4b-4281-b951-d872f2087c98
-
gab@chromium.org authored
This add ~0.18ms to startup on my machine; note that it's already called 4 times before me (the first call costing ~0.38m followed by 3 X 0.18ms). See my analysis on http://codereview.chromium.org/140553005 It's not clear whether this can get worse in some scenarios, but I'm already calling this later than the current caller so... I'm also keeping the result as a static to avoid calling this multiple times (e.g. when doing unloaded profile initialization we don't want to call this multiple times in a loop in a short time span). And we have timing stats for Settings.FilterOnLoadTime which will let us know if there are any big outliers coming out of this CL. Review URL: https://codereview.chromium.org/156693003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251500 0039d316-1c4b-4281-b951-d872f2087c98
-