| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
insensitive
When storing headers in a map the map should be case insensitive (like HTTPHeaderMap in Blink) so that headers can be easily searched for and coalesced when necessary.
BUG=392621
Review URL: https://codereview.chromium.org/576973004
Cr-Commit-Position: refs/heads/master@{#296387}
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, overscroll notifications are always sent as a separate IPC message,
regardless of the causal event. Instead, bundle the overscroll metadata with
the event ack if the event caused the overscroll, saving an IPC message in the
most common overscroll case.
BUG=328503
Review URL: https://codereview.chromium.org/281723010
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@271541 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The typical number of components per LatencyInfo instance is quite small. Avoid
unnecessary heap allocation by using a SmallMap to store component entries.
This reduces the average browser send time cost per touch or scroll event by
~15us on a Nexus 4, and ~22us on a Galaxy Nexus.
BUG=341613
Review URL: https://codereview.chromium.org/157003005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@257740 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Unfortunately, this brings in changes to webkit/browser/fileapi, and once
that changes, a lot of files have to be updated.
The bright side is that most of the collateral changes are just trivial
renaming of PlatformFileError -> File::Error and PlatformFileInfo ->
File::Info
BUG=322664
Review URL: https://codereview.chromium.org/145303002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@247301 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
This makes base, ui, and net compile without the "using base::string16" directive that's currently checked in.
BUG=
Review URL: https://codereview.chromium.org/100303003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@238246 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These function become hot on some benchmarks. WriteData is inefficient because
it writes the length, even though it's known on the reader side (compile-time
constant).
For <float> we can simply use WriteFloat. For <double> we can use WriteBytes
instead of WriteData.
BUG=307480
Review URL: https://codereview.chromium.org/39363002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@232060 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
Minor bug in r211473.
R=tsepez@chromium.org
TBR=tsepez@chromium.org
Review URL: https://chromiumcodereview.appspot.com/19023006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@211546 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, we've supported unsigned short, but not unsigned char. There
are a few places where folks are passing around color values that must be
in the 0..255, and we can save both bytes written and avoid explicit range
checks by the receiving method by using this rather than larger types.
We support unsigned char only. Signed char is evil due to questionable
signedness in the C specs.
I've re-arranged the order of these specializatons so that they go in
order of increasing size as they go down the page.
R=jam@chromium.org
BUG=259903
Review URL: https://chromiumcodereview.appspot.com/18068016
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@211473 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=247723
TEST=no change
TBR=brettw@chromium.org
Review URL: https://codereview.chromium.org/16415016
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@206066 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=247723
TEST=none
TBR=ben@chromium.org
Review URL: https://chromiumcodereview.appspot.com/16684003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@205436 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It builds and runs, but not a whole lot else. This change includes:
* ChromeFrameAutomationProvider is now OS_WIN only. In practice, this
has been the case for some time. Now it's formalized by giving the
implementation files the _win suffix.
* Automation messages and datatypes used exclusively by Chrome Frame now
use HWND directly rather than a toolkit-specific gfx typedef of one
since the requirement is that an actual HWND be sent over the
channel. A change in toolkit (e.g., switching to Aura) must not change
this. As a consequence of this change, some automation types and
messages are now only defined for OS_WIN builds.
* ExternalTabContainerWin is no longer derived from a NativeWidget type
(this was previously the case so that the ETCW could be notified of NW
lifecycle events). Now, in contrast, ETCW registers itself as an
observer of its Widget. Two additional lifecycle methods have been
added to WidgetObserver: OnWidgetCreated and OnWidgetDestroyed.
* ExternalTabContianerWin initializes its Widget with an instance of
DesktopNativeWidgetAura when use_aura.
* A special note about HWND IPC marshaling: this change adds a type
mapping from HWND to a generic HANDLE in ipc_message_utils.h, which
allows for the removal of a hack in content_message_generator.h to
marshal HWNDs.
This change reverts all of:
* r178752 -- Remove CF from all.gyp targets if use_aura is defined.
* r164590 -- Remove setup -> Chrome Frame dependency. Make it possible
to build an installer for Aura.
and portions of:
* r99993 -- Get chrome to link with USE_AURA
* r99787 -- Preliminary work to allow Chrome to build with USE_AURA.
BUG=171018
TEST=chrome_frame_tests provides good coverage in non-Aura builds.
Review URL: https://chromiumcodereview.appspot.com/12220101
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@185328 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
| |
This updates headers that forward-declare it and a few random places to use the namespace explicitly. There us a using declaration in file_path.h that makes the rest compile, which we can do in future passes.
Review URL: https://codereview.chromium.org/12163003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@180245 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
It's a rarely-used and completely unnecessary (and thin) wrapper around
PickleIterator.
Review URL: https://chromiumcodereview.appspot.com/11570038
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@173525 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Using std::vector to hold UploadElement is bad for two reasons:
1. It results in a lot of unnecessary copy of uploaded data.
2. Appending new chunks may result in invalidating the pointer held by UploadBytesElementReader.
BUG=160028
TEST=git try
TBR=ananta@chromium.org, tony@chromium.org
Review URL: https://chromiumcodereview.appspot.com/11275223
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@167611 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
that new message files can't be added to chromium without triggering a security review.
Review URL: https://chromiumcodereview.appspot.com/11048038
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@163713 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=136677
Review URL: https://chromiumcodereview.appspot.com/10979047
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@160431 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
Render to the surface it provides to us.
BUG=151718
Review URL: https://codereview.chromium.org/10984007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@159559 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
-traits that are only used by chrome should be in chrome
-traits that aren't used by chrome shouldn't be in content/public
-use macros for serialization where possible
-traits that are only used by one message file should just be listed in it
-get rid of webkit_param_traits since it's not needed anymore. It was added as a hack to keep npchrome_frame.dll's size small by giving a hint to the MSVS linker, but now that there's more split between the message files because of the content split it's not necessary anymore. I've verified that npchrome_frame.dll's size (Release, non-component) size doesn't change.
Review URL: https://codereview.chromium.org/10980010
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@158570 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
Only hooked up in "aura_demo --viewer" right now, and doesn't actually accomplish anything other than opening a window yet.
Review URL: https://codereview.chromium.org/10872002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@157367 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change integrates the Hyphenator class to content so Chrome can use it. This change basically consists of two parts:
* Adds a couple of IPC messages so a renderer asks a browser to open hyphenation dictionaries;
* Adds a HyphenatorMessageFilter class, which opens hyphenation dictionaries in a browser process;
* Changes the Hyphenator class to send IPC messages to open hyphenation dictionaries.
BUG=47083
TEST=HyphenatorTest.SetDictionary,HyphenatorMessageFilterTest.OpenDictionary
Review URL: https://chromiumcodereview.appspot.com/10854245
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@154663 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
Requires new plumbing to get custom android_webview
layer IPC messages a flowing.
BUG=
Review URL: https://chromiumcodereview.appspot.com/10890024
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@154564 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds the motion message filter, motion ipc messages, and related motion
files. This was originally part of a larger patch
(http://codereview.chromium.org/10698046/).
BUG=59201
Review URL: https://chromiumcodereview.appspot.com/10823310
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@151908 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=140306
Tested: Added new browser tests!
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=150654
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=150863
Review URL: https://chromiumcodereview.appspot.com/10830072
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@150956 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=140306
Tested: Added new browser tests!
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=150654
Review URL: https://chromiumcodereview.appspot.com/10830072
TBR=fsamuel@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10827257
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@150873 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=140306
Tested: Added new browser tests!
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=150654
Review URL: https://chromiumcodereview.appspot.com/10830072
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@150863 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=140306
Tested: Added new browser tests!
Review URL: https://chromiumcodereview.appspot.com/10830072
TBR=fsamuel@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10832219
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@150681 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=140306
Tested: Added new browser tests!
Review URL: https://chromiumcodereview.appspot.com/10830072
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@150654 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
OldBrowserPluginMsg/OldBrowserPluginHostMsg
The upcoming rewrite of the browser plugin has colliding names for IPC messages.
Rename existing messages to Old in preparation for the new implementation.
BUG=none
Review URL: https://chromiumcodereview.appspot.com/10829074
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149116 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
For context see this thread:
https://groups.google.com/a/chromium.org/forum/?fromgroups#!topic/chromium-dev/RMcVNGjB4II
TBR=thakis,pkasting,jam
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@146163 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
file the same. It makes all non-trivial Read/Write calls non-inline.
TEST=it compiles
BUG=none
Review URL: https://chromiumcodereview.appspot.com/10498002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@140375 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
TEST=it compiles
BUG=none
Review URL: https://chromiumcodereview.appspot.com/10485002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@140138 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
Move thse to ipc/ from content/common so that they may be used in directories
parallel to content/. Pre-requisite for fixing the associated bug.
BUG=127624
Review URL: https://chromiumcodereview.appspot.com/10442072
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@139636 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, we would open the NaCl loader's Windows process handle by
its PID in the NaCl broker (when attaching a Windows debug exception
handler). But there is a potential race condition here: if the NaCl
loader dies, and its PID is reused, we could be opening the wrong
process.
Fix this by opening the process handle in the browser process and
passing it to the 64-bit NaCl broker.
This requires fixing a bug in ipc_message_utils.h. This code could
cope with sending a handle from a 64-bit process to a 32-bit process
(NaCl broker to browser), but the DCHECK would fail when sending a
handle from a 32-bit process to a 64-bit process (browser to NaCl
broker).
This change is in preparation for changing NaCl's Windows debug
exception handler to attach on demand, which would allow untrusted
NaCl code to cause the NaCl process to exit before
OnDebugExceptionHandlerLaunched() runs.
BUG=http://code.google.com/p/nativeclient/issues/detail?id=2618
TEST=run_inbrowser_exception_test in nacl_integration
Review URL: https://chromiumcodereview.appspot.com/10174031
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@134189 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=117897
TEST=manually
Review URL: http://codereview.chromium.org/9924026
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@131054 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
Pickle::WriteLong() to WriteLongUsingDangerousNonPortableLessPersistableForm()
and add a strongly-worded comment against its use; it is used only for IPC
which is safe. (These methods write variable amounts of data to pickles,
depending on architecture, and aren't safe if pickles are persisted.)
Review URL: http://codereview.chromium.org/9641005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128347 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: https://chromiumcodereview.appspot.com/9718019
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@127420 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
The default SAS is Ctrl+Alt+Delete. It can neither be intercepted by the client (at least on Windows) nor it can be injected the same way other key strokes are injected. This CL makes the Windows host to interpret a double Scroll Lock as a SAS and invoke the Chromoting service to issue the actual SAS.
Review URL: http://codereview.chromium.org/9617027
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@126186 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
They used to get swapped in by observing provisional loads. This is being changed to Navigate so renderer-issued navigations into a prerender can be handled with the same mechanism that is used to handle renderer-issued navigations which need to cross process boundaries, such as clicking into a hosted app.
For browser issued navigations, this means that we will immediately swap in the prerender, instead of sending a Navigate message to the render view and swapping in on the provisional load statement.
For renderer issued navigations, decidePolicyForNavigation will ultimately cancel the navigation in the renderer and send an OpenURL up to the browser process.
In order to make the renderer know that a navigation could be prerendered, a set of prerendered URLs need to be sent to a render process.
BUG=104493
TEST=Existing browser tests, manual tests that omnibox prerenders work. There should be no user-visible changes.
Review URL: http://codereview.chromium.org/9623018
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@125836 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There was a lot of redundant error checking and initialization code in all Pickle Read methods because of the void** iterator type. This change replaces the void* iterator with PickleIterator, which encapsulates the read pointer so that less error checking and initialization code is needed for reading.
PickleIterator has all the necessary data to do the actual reading. The advantage of having it provide Read methods (as opposed to leaving them solely in the Pickle interface) is that the callers do not need to pass around the const Pickle* once they have a PickleIterator.
Followup CLs will refactor the call sites to remove const Pickle* arguments where they are now unnecessary. Then the Pickle::Read* methods can be removed entirely.
The alternative approach would have been to change the Pickle::Read methods to non-const and remove the iterator parameter (making Read methods advance an internal read pointer). Unfortunately, the const Read with iterator design is entrenched throughout the chromium code, making this a much more complex change with the same performance outcome.
BUG=13108
Review URL: https://chromiumcodereview.appspot.com/9447084
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@125447 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
implementation.
- The general-purpose speech recognition classes (that will be needed also by future code) have been renamed to SpeechRecognition*;
- The IPC Messages and dispatcher(host) classes that are only related to the current input tag (x-webkit-speech) support have been renamed to InputTagSpeech*;
- The namespace has been renamed from speech_input to speech;
BUG=116954
TEST=
Review URL: https://chromiumcodereview.appspot.com/9568002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@125378 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
Moves accessibility IPC definitions into content/common/accessibility_messages.h and renames them to be more clear.
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/9375019
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@121734 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=111316
TEST=run out/Debug/content_shell --dump-render-tree file://$(pwd)/third_party/WebKit/LayoutTests/fast/html/section-element.html > section-element-actual.txt - should be the same as section-element-expected.txt
Review URL: http://codereview.chromium.org/9289045
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@119642 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Part of larger patch here http://codereview.chromium.org/8345027/ which is
updated with remaining pieces.
BUG=79050
TEST=
Review URL: http://codereview.chromium.org/8417034
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@107765 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds JavaBridgeDispatcher, which handles injecting Java objects into
the main frame of a RenderView. It also adds the IPC messages that are sent
from browser to renderer to manage the injection of these Java objects.
BUG=96703
Review URL: http://codereview.chromium.org/8347005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@106614 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
With ANSI color if asked for.
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/8319023
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@106541 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
and Linux.
BUG=62079
TEST=Missing plug-in placeholder looks different
Review URL: http://codereview.chromium.org/7990005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@104144 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
geolocation_dispatcher.
Get return path serialization working.
R=groby@chromium.org
BUG=None
TEST=None
Review URL: http://codereview.chromium.org/7823002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@101536 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
chrome as the functionality
exposed by this extension is chrome specific. The IPCs used by this extension have all been moved to chrome
to a new header file benchmarking_messages.h in chrome\common.
Added a new message filter object in chrome\browser which filters the benchmarking IPCs.
Most of the changes in this CL are centered around ensuring that the benchmarking stuff gets initialized
in the same order as before.
Continuing changes to get rid of the pattern of IPC messags spanning across content and chrome.
BUG=87335
Review URL: http://codereview.chromium.org/7885013
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@101214 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
|