Gitiles
Code Review
Sign In
gerrit-public.fairphone.software
/
platform
/
external
/
libchrome
/
10067d5aab96ad79dc238015f6eaebcfd7a2a9ac
/
base
/
supports_user_data.h
64f18ab
Assert SetUserData key non-null.
by Randy Smith
· 7 years ago
44a21b4
Remove the deprecated raw-pointer call from SupportsUserData
by avi
· 8 years ago
756b8ec
Update SupportsUserData API to accept std::unique_ptr<>.
by sdefresne
· 8 years ago
1ac6191
Make SupportsUserData sequence-affine instead of thread-affine.
by gab
· 8 years ago
cc8e4d8
Convert //base to use std::unique_ptr
by dcheng
· 9 years ago
e54cc5a
Remove linked_ptr usage in //base.
by dcheng
· 9 years ago
a6a6a68
Switch to standard integer types in base/.
by avi
· 9 years ago
7129367
[ServiceWorker] Make Stream support in ServiceWorkerURLRequestJob
by horo
· 10 years ago
8781fe4
Hook up WebRTC logging extension API to the underlying functionality.
by grunell@chromium.org
· 11 years ago
9592b54
Switch AutofillManager to be UserData on WebContents.
by avi@chromium.org
· 12 years ago
db2811b
SupportsUserData is not thread safe
by joth@chromium.org
· 12 years ago
09840d3
Attached data cleanup.
by avi@chromium.org
· 12 years ago
b2d507b
Unify and clean up system download notifications, add Mountain Lion support.
by avi@chromium.org
· 12 years ago
d55e9a4
RefCounted types should not have public destructors, base/ edition
by rsleevi@chromium.org
· 12 years ago
14eaa3f
Get rid of WebKitContext. Only two out of six HTML5 related objects were in it and it was just a glorified std::pair after the recent refactorings.
by jam@chromium.org
· 13 years ago
5c8ca51
Remove getters for HTML5 related objects from the ResourceContext interface. Half of them weren't used by chrome, so they can be hidden from chrome. The rest were accessed by chrome, but we don't need every embedder to store this data on their ResourceContext implementation. Instead have content associate the data itself to simplify the work for embedders.
by jam@chromium.org
· 13 years ago
533df72
Add extra data to BrowserContext so that content layer and other embedders can stash data with it that has the same lifetime. Converted SSLHostState to use it for now. I'll do the rest in a followup.
by jam@chromium.org
· 13 years ago