| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
BUG=94925
TEST=none
Review URL: http://codereview.chromium.org/7839019
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99908 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=94694
TEST=ensure --enable-sync-tabs,--enable-sync-tabs-for-other-clients switches
work. Verify "Open Tabs" on sync setup pane. Verify about:flags describes
"Enable syncing open tabs" accurately. Ensure functionality of
--enable-sync-tabs-for-other-clients still works.
R=tim@chromimum.org,yfriedman@chromium.org
Review URL: http://codereview.chromium.org/7837014
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99890 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
chrome.webstore.install()
The link URL is used to select between multiple <link rel="chrome-webstore-item">
elements on the page.
To keep track of callbacks, an install ID is generated at the start of each
chrome.webstore.install() call, so that the browser knows which ones to invoke
when an install completes.
Also adds validation of install requesting URL against the item's verified
domain (wasn't done until now since it wasn't testable).
R=aa@chromium.org
BUG=93380
Review URL: http://codereview.chromium.org/7795032
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99889 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
all embedders of content. I've based the refactoring on the existing BrowserMainParts. This is the first step; I didn't want to do it all at the same time because it would be too big. Remaining tasks:-rename the browser_main files in chrome to chrome_browser_main-move the OS specific implementations of BrowserMainParts that are needed for content-finish splitting the remaining BrowserMain function (now that's in TemporaryContinue())BUG=90445
Review URL: http://codereview.chromium.org/7779040
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99884 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
http://crbug.com/93947
TEST=none
Review URL: http://codereview.chromium.org/7839002
Review URL: http://codereview.chromium.org/7839002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99830 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
with USE_AURA.
http://crbug.com/93947
TEST=none
Review URL: http://codereview.chromium.org/7839002
TBR=ben@chromium.org
Review URL: http://codereview.chromium.org/7840010
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99813 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
http://crbug.com/93947
TEST=none
Review URL: http://codereview.chromium.org/7839002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99810 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
packaged the extension you're uploading.
(This page is in the extension doc set, thus the references to
"extension". We should eventually move all .crx and manifest-related
docs out of the extension doc set and into a Chrome-wide doc set.)
BUG=93218
TEST=none
Review URL: http://codereview.chromium.org/7824048
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99790 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
This gets browser.lib to build.
http://crbug.com/93947
TEST=none
Review URL: http://codereview.chromium.org/7834048
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99787 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also sniffer listener was implemented on the WebUI side, which signals when
GAIA page loading error appears.
BUG=chromium-os:18744
TEST=Behind captive portal, try to click 'Add new user'. Corresponding message page should be shown.
Review URL: http://codereview.chromium.org/7779010
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99777 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
For the browser process, this will be overridden by
-[BrowserCrApplication init] (which raises it).
BUG=94551
TEST=Developers don't complain about zombie objects in other processes.
Review URL: http://codereview.chromium.org/7826016
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99754 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
content setting instead of the type ContentSetting.
The HostContentSettingsMap should allow storing arbitrary |Value|s instead of only |ContentSettings| for content settings types (BTW: content settings should be called website settings). This allows to add other content settings type(website settings types) to the host content settings map that require more complex settings than ALLOW, BLOCK, ASK, ... . CONTENT_TYPE_AUTO_SELECT_CERTIFICATE is one example of such a content settings type. CONTENT_TYPE_AUTO_SELECT_CERTIFICATE requires a map with certain criteria that a certificate must match to be selected.
- Add filter to the AutoSelectCertificate policy.
Instead of only giving a list of origin patterns that specify origins for which client certificates should be auto selected, each origin pattern now also requires a filter with certificate criteria.
This is the second CL in a series and follows CL http://codereview.chromium.org/7831004/
BUG=63656, 81825
TEST=host_content_settings_map_unittest.cc,
content_settings_policy_provider_unittests.cc
TBR=pam@chromium.org
Review URL: http://codereview.chromium.org/7828022
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99672 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=none
TEST=none
TBR=jstritar@chromium.org
Review URL: http://codereview.chromium.org/7834022
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99654 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
This change integrates the Spelling service (a.k.a. "Did you mean") to a context-menu of Chrome so we can see the spell-check result retrieved from the Spelling service. This change sends a JSON-RPC request to the service in the background and update a context-menu item while showing to prevent junkiness.
BUG=29191,93746
TEST=right-click a misspelled word and see it is updated.
Review URL: http://codereview.chromium.org/7713033
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99633 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
This lets you define apps promo logos as https URLs in the promo feed. The AppsPromoLogoDownloader only downloads the image over https and from *.google.com domains. AppsPromo caches the image until the URL changes in the promo feed.
BUG=84506
TEST=*Promo*
Review URL: http://codereview.chromium.org/7820003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99621 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is part of a work in progress (http://codereview.chromium.org/7716003).
This patch is meant to introduce the blacklist manager, which listens to prefs
changes on the UI thread (later to be managed by policies) and filters
URLRequests on the IO thread.
Subsequent patches will build the blacklist based on the preferences, and
block URLRequests that match the list. The policy will be introduced once
everything else is ready.
BUG=49612
TEST=URLBlacklistManagerTest; everything still works as before
Review URL: http://codereview.chromium.org/7747018
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99608 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=94925
TEST=trybots
Review URL: http://codereview.chromium.org/7826038
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99526 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/7824022
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99473 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
with or without Autofill.
BUG=none
TEST=unit_tests --gtest_filter=AutofillMetricsTest.*
Review URL: http://codereview.chromium.org/7740070
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99447 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
original CL w/LGTMs: http://codereview.chromium.org/7812036/
Review URL: http://codereview.chromium.org/7824041
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99409 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update automation connection code to wait for webui login screen to become ready.
NativeUI login automation continues to work as is.
BUG=chromium-os:18271, chromium-os:17712
TEST=
Review URL: http://codereview.chromium.org/7819013
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99408 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To make this easier, the extension install dialog was changed from doing layout
by hand to using GridLayout (thus no longer necessitating overrides of
GetPreferredSize/Layout or lots of math).
To lessen the repeated logic between the inline install UIs,
ExtensionInstallUI::Prompt was beefed up to return formatted data directly
(and in the case of rating stars, include the logic for which ones to show).
Also includes some other tweaks:
- Rename inline install dialog to "Add to Chrome" and the install button in it
to "Add"
- Use the final webstore JSON data URLs
R=asargent@chromium.org
BUG=93380
TEST=no
Review URL: http://codereview.chromium.org/7826029
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99407 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=none
TEST=added test to ExtensionManagementApiTest.Basics
Review URL: http://codereview.chromium.org/7826020
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99398 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=94925
TEST=None
Review URL: http://codereview.chromium.org/7824011
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99388 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
This should get rid of all references to webkit::npapi::IsPluginEnabled in content/.
BUG=80794
TEST=none
Review URL: http://codereview.chromium.org/7387010
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99355 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
For reference, see: http://codereview.chromium.org/7669073/
BUG=
TEST=
Review URL: http://codereview.chromium.org/7767013
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99317 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=
TEST=
Review URL: http://codereview.chromium.org/7831026
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99314 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/7826002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99310 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
if needed.
John: can you plase look at the content\... changes?
Scott: can you plase look at the chrome\... changes?
BUG=0
TEST=Install an official chrome build (not a chromium build) with a non
organic brand code. During the install, make sure to choose google as the
home page. When google is running, pressing the home page button should
cause the request to include the RLZ http header. Pressed Alt-Home should
do the samer thing.
When starting chrome, the RLZ header should also be present since the startup
page is the home page, and the home page is set to google.
Navigating to the google.com manually by typing the URL or by clicking on
a link should not cause the hrrp header to be added.
Not choosing google as the home during install, or changing the home page
to be something other than google should stop the http header from being
added. This is true is even if the user subsequently set his home page to
google again.
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=99283
Review URL: http://codereview.chromium.org/7791029
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99309 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
R=jam@chromium.org
BUG=None
TEST=None
Review URL: http://codereview.chromium.org/7821010
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99292 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
so the original code that created the delayed callback is lost."
This reverts commit 4cf5cf73d319b69c32ad30af8954235755856455. (r99284)
TBR=jbates@chromium.org
Review URL: http://codereview.chromium.org/7825026
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99290 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the RLZ string
if needed.
John: can you plase look at the content\... changes?
Scott: can you plase look at the chrome\... changes?
BUG=0
TEST=Install an official chrome build (not a chromium build) with a non
organic brand code. During the install, make sure to choose google as the
home page. When google is running, pressing the home page button should
cause the request to include the RLZ http header. Pressed Alt-Home should
do the samer thing.
When starting chrome, the RLZ header should also be present since the startup
page is the home page, and the home page is set to google.
Navigating to the google.com manually by typing the URL or by clicking on
a link should not cause the hrrp header to be added.
Not choosing google as the home during install, or changing the home page
to be something other than google should stop the http header from being
added. This is true is even if the user subsequently set his home page to
google again.
Review URL: http://codereview.chromium.org/7791029
TBR=rogerta@chromium.org
Review URL: http://codereview.chromium.org/7831030
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99286 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
the original code that created the delayed callback is lost.
This change adds a tracked_objects::Location parameter to the APIs in base/timer.h so we can trace the PostTask callbacks. The other files are touched to add the FROM_HERE Location parameter.
Review URL: http://codereview.chromium.org/7812036
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99284 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
if needed.
John: can you plase look at the content\... changes?
Scott: can you plase look at the chrome\... changes?
BUG=0
TEST=Install an official chrome build (not a chromium build) with a non
organic brand code. During the install, make sure to choose google as the
home page. When google is running, pressing the home page button should
cause the request to include the RLZ http header. Pressed Alt-Home should
do the samer thing.
When starting chrome, the RLZ header should also be present since the startup
page is the home page, and the home page is set to google.
Navigating to the google.com manually by typing the URL or by clicking on
a link should not cause the hrrp header to be added.
Not choosing google as the home during install, or changing the home page
to be something other than google should stop the http header from being
added. This is true is even if the user subsequently set his home page to
google again.
Review URL: http://codereview.chromium.org/7791029
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99283 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
On the server side we have a 1% experiment.
BUG=94757
TEST=None
Review URL: http://codereview.chromium.org/7809011
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99281 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Scott: please review the code under UI.
Tim: please review the rest.
BUG=None
TEST=Make sure these feature are not enabled if the about:flags option is
not set. Also make sure the option to enable auto-login is not visible
in the Passwords section of the Personal Stuff section of the options page.
Review URL: http://codereview.chromium.org/7740083
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99131 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=94082
TEST=none
Review URL: http://codereview.chromium.org/7740005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99123 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
Engines. Removed some sync fields from search engine proto.
TEST=Ensure that you can enable Search Engine Sync through the about:flags page and sync setup UI. With both enabled search engines should start syncing.
BUG=15548
Review URL: http://codereview.chromium.org/7669052
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99114 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
run.
Patch by guohui@chromium.org
BUG=93406
TEST=Delete first run sentinel file and launch chrome. Confirm ntp4 bubble is not shown.
Review URL: http://codereview.chromium.org/7716005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99105 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This replaces the nacl_helper_bootstrap program, dynamically-linked against
nacl_helper.so, with a standalone, statically-linked nacl_helper_bootstrap
program that loads the dynamic linker, instructing it in turn to load the
nacl_helper program (now a PIE rather than a DSO).
This avoids two problems with the old scheme:
1. The nacl_helper_bootstrap program remained in the dynamic linker's
list of loaded objects, as the main executable, even though the
memory where its .dynamic section had been was overwritten with
the NaCl untrusted address space. Code that traverses the list of
all loaded objects could thus attempt to look at pointers into this
part of memory, and be led astray.
2. nacl_helper_bootstrap's large (~1G) bss segment could cause the kernel
to refuse to load the program because it didn't think there was enough
free memory in the system for so large an allocation of anonymous memory.
The bootstrap program is kept very small by avoiding all use of libc
(except for memset and integer division routines needed on ARM). It has
its own custom start-up code hand-written in assembly and its own custom
system call stubs done with hand-written GCC inline asm statements.
To avoid the second problem, the bootstrap program no longer has a large
bss. Instead, it has a special ELF segment (i.e. PT_LOAD header) that
specifies no memory access, and a large (~1G) mapping size from the file.
This mapping is way off the end of the file, but the kernel doesn't mind
that, and since it's all a file mapping, the kernel does not do its normal
memory accounting for consuming a large amount of anonymous memory.
Unfortunately, it's impossible to get the linker to produce exactly the
right PT_LOAD header by itself. Using a custom linker script, we get the
layout exactly how we want it and a PT_LOAD header that is almost right.
We then use a build-time helper program to munge one field of the PT_LOAD
to make it exactly what we need.
BUG= http://code.google.com/p/chromium/issues/detail?id=94147
TEST= hand-tested chromium build
R=bradchen@google.com
Review URL: http://codereview.chromium.org/7776034
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99089 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
values to DCHECK(), ASSERT_EQ(), etc.), generally by naming previously-anonymous enums. We've decided not to eliminate the warning entirely because doing so is only possible with tons of ugly static_cast<>()s in Mac code.
BUG=92247
TEST=Compiles
Review URL: http://codereview.chromium.org/7605019
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99086 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
out of content
into Chrome.
1. PluginProcessHostMsg_GetPluginFinderUrl
2. PluginProcessHostMsg_MissingPluginStatus
3. PluginProcessHostMsg_DownloadUrl
These messages are prefixed with Chrome. Removed the InstallMissingPlugin and OnInstallMissingPlugin
handlers from the NPAPI plugin sources and from our webkit plugin implementation. The plugin infobar
no longer sends over an IPC message to initiate installation of the third party plugin. It sends over
a windows message which is handled in the plugin installer for Windows. This functionality is not
implemented for the mac and linux as before.
To display the plugin installation infobar the PluginProcessHostMsg_MissingPluginStatus message
sent by the plugin needs the routing id and the renderer process id. This information is now
passed along with the plugin instantiation parameters in NPP_New. These parameters are only read
by the default plugin.
This is a continuation of the fixes to ensure that IPC's don't span across content and chrome.
BUG=87335
Review URL: http://codereview.chromium.org/7812020
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99062 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=81752
TEST=None
Review URL: http://codereview.chromium.org/7672009
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@98981 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
of the page.
Preliminary design doc:
https://docs.google.com/a/google.com/document/d/1KWsF52ImY4eJbNgizaA6Gw_aMVg24zgZfypKZBs376k/edit?hl=en_US&ndplr=1
TEST=set some policies, start chrome and go to chrome://policy
Review URL: http://codereview.chromium.org/7585036
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@98977 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
dialog.
BUG=chromium-os:19870
TEST=try
Review URL: http://codereview.chromium.org/7811017
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@98971 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
content_settings::NotificationsProvider.
BUG=63656
TEST=host_content_settings_map_unittest.cc,
content_settings_pref_provider.cc,
desktop_notifications_service_unittest.cc
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=98938
Review URL: http://codereview.chromium.org/7655019
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@98960 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- experimental.accessibility.onVolumeChange
I run chrome/common/extensions/docs/build/build.py, but no documents about a11y was changed. So this CL doesn't include any changes of documents.
BUG=chromium-os:16592
TEST=call the APIs manually on chromium-os
Review URL: http://codereview.chromium.org/7708025
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@98948 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
content_settings::NotificationsProvider.
BUG=63656
TEST=host_content_settings_map_unittest.cc,
content_settings_pref_provider.cc,
desktop_notifications_service_unittest.cc
Review URL: http://codereview.chromium.org/7655019
TBR=markusheintz@chromium.org
Review URL: http://codereview.chromium.org/7810017
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@98941 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
content_settings::NotificationsProvider.
BUG=63656
TEST=host_content_settings_map_unittest.cc,
content_settings_pref_provider.cc,
desktop_notifications_service_unittest.cc
Review URL: http://codereview.chromium.org/7655019
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@98938 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
TEST=make sure --test-auth-email and --test-auth-password values are propagated to test auth extension content script while automating login process
BUG=chromium-os:19866
Review URL: http://codereview.chromium.org/7809015
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@98929 0039d316-1c4b-4281-b951-d872f2087c98
|