sophey@chromium.org chrome-sherlock@google.com Whether the webpage is a long-form article or not. This is logged when the user navigates away from the current page (via loading a different webpage or native page). It is only logged if the distillability of the page had been determined. sophey@chromium.org chrome-sherlock@google.com What the Open Graph Protocol classification of the page is. This is logged when the user navigates to the current page. It is only logged if there is an 'og:type' property in the HTML of the page. yyanagisawa@chromium.org content-owners@chromium.org Records whether the renderer-supplied creation context type matches the browser-derived secure context state for a SharedWorker connection. Recorded on each SharedWorker connection request. yyanagisawa@chromium.org chrome-worker@google.com Records the reason why a SharedWorkerHost is destroyed. This is to investigate why a shared worker is terminated unexpectedly. This is also used for understanding the ratio of destruction cases. annasato@chromium.org chrome-worker@google.com The time spent checking if a navigating page with a SharedWorker is the last active client. This is recorded whenever a page with a SharedWorker connection navigates away. yyanagisawa@chromium.org wanderview@chromium.org Records whether a WebSocket connection was initiated from a SharedWorker in a context that requires cross-site cookie restrictions (e.g. created via the Storage Access API (SAA) or in a third-party context). This helps measure the prevalence of workers that should have SameSite cookie restrictions. Recorded in SharedWorkerHost::CreateWebSocketConnector. peconn@google.com src/content/OWNERS The amount of time between StoragePartitionImpl::OnSSLCertificateError being called and the answer being received. This measures the latency introduced by the browser process and the embedder (including any app callbacks) for all platforms. Recorded on SSL error. elabadysayed@chromium.org src/third_party/blink/renderer/core/content_capture/OWNERS The time taken to capture the on-screen content and group them by document. Note that this metrics is only recorded on clients on which a high-resolution clock is available. elabadysayed@chromium.org src/third_party/blink/renderer/core/content_capture/OWNERS The total number of content captures sent for a document. scottyoder@google.com bling-pandamonium@google.com The status of the push notifications client toggle for Content. scottyoder@google.com bling-pandamonium@google.com The status of the push notifications client toggle for Sports. scottyoder@google.com bling-pandamonium@google.com The user has dismissed a content notification. scottyoder@google.com bling-pandamonium@google.com The Type of elegibility for a given user for the Content Notifications feature. Includes details about what UI entrypoint type the user is elegible for as well as whether they are in the control group for that entrypoint. scottyoder@google.com bling-pandamonium@google.com Reports what actions has the user taken on a notification. This metric matches NAUs sent. scottyoder@google.com bling-pandamonium@google.com After a notification action upload, whether the request succeeded or failed. scottyoder@google.com bling-pandamonium@google.com After a notification interaction, if the URL has successfully been parsed or if it has failed. scottyoder@google.com bling-pandamonium@google.com Provisional notifications were turned on from the Notifications Promo. scottyoder@google.com bling-pandamonium@google.com Log the Set Up List Content Notification confirmation snackbar events. scottyoder@google.com bling-pandamonium@google.com The action taken by the user in response to the Top of Feed Content Notifications promo. scottyoder@google.com bling-pandamonium@google.com An event from the the Top of Feed Content Notifications promo. scottyoder@google.com bling-pandamonium@google.com This logs if a SNo registration has not succeeded due to a BrowserState being unavailable at the time due to a Browser not being initialized. scottyoder@google.com bling-pandamonium@google.com The action taken by the user in the content notification settings view. sisidovski@chromium.org chrome-loading@google.com Measures how long a sync call to ContentSettingsManager::AllowStorageAccess blocks the renderer thread. Logged each time the renderer asks the browser for storage permission status synchronously. sisidovski@chromium.org chrome-loading@google.com Logged when the renderer checks storage permissions. True if the permission was already cached in ContentSettingsAgentImpl (e.g. via eager fetching), false if it required a synchronous Mojo IPC to the browser process. fsenra@chromium.org dullweber@chromium.org Logs actions within the StorageAccess bubble. engedy@chromium.org src/components/permissions/PERMISSIONS_OWNERS Count of how often a specific content setting is set for an embedded URL by an extension. Only counts settings when the secondary pattern is different to the primary pattern. Exactly one of this or ContentSettings.ExtensionNonEmbeddedSettingSet will be emitted per call to contentSettings.set(), if the arguments to the call are valid. engedy@chromium.org src/components/permissions/PERMISSIONS_OWNERS Count of how often a specific content setting is set when only a single pattern is specified. Exactly one of this or ContentSettings.ExtensionEmbeddedSettingSet will be emitted per call to contentSettings.set(), if the arguments to the call are valid. trishalfonso@google.com wanderview@chromium.org Measures how long a call to network::CookieSettings::GetContentSetting takes. Logged each time a call is made. Starting M135 sub-sampled with probability 0.001. Note that histogram samples for clients without high-resolution clocks are dropped. dullweber@chromium.org wanderview@chromium.org Measures how long a call to CookieSettingBase::GetCookieSettingInternal takes. Logged each time a call is made. Starting M135 sub-sampled with probability 0.1. Note that histogram samples for clients without high-resolution clocks are dropped. engedy@chromium.org src/components/permissions/PERMISSIONS_OWNERS The number of user defined hostname patterns for content settings at browser start. Warning: this histogram was expired from 2022-08-28 to 2022-09-21; data may be missing. engedy@chromium.org src/components/permissions/PERMISSIONS_OWNERS Number of times a given permission was requested by a website and the user has the permission set to prompt (i.e. not blocked or allowed). Note this is probably not the metric you want - it does not correspond to the total number of times websites request a permission. Also, because specific permissions have code that can automatically block or grant permissions based on things like incognito, installed extensions etc., this does also not correspond to the number of times users are prompted to allow permissions. For a better metric to track how often users are prompted, either use ContentSettings.PermissionsActions*, or Permissions.Prompt.*. See https://crbug.com/638076 for more details. Warning: this histogram was expired from 2022-06-19 to 2022-09-21; data may be missing. charleszhao@chromium.org lazzzis@google.com src/components/blocked_content/OWNERS Tracks whether the popup content blocked puzzle piece was shown in the Omnibox, and how the user interacted with it. csharrison@chromium.org lazzzis@google.com src/components/blocked_content/OWNERS Counts of various events related to the popup blocker. Including blocked popups and overridden (clicked through) popups. This is similar to the ContentSettings.Popups but is at the per-popup layer rather than at the UI layer. csharrison@chromium.org Counts of various events related to the strong popup blocker (aka abusive experience enforcement), that is triggered via safe browsing. ryankalla@google.com src/components/permissions/PERMISSIONS_OWNERS The default Auto-verify setting at profile open. This histogram is only recorded for regular profiles. tungnh@chromium.org src/components/permissions/PERMISSIONS_OWNERS The default permission setting for Background Sync at profile open. This histogram is only recorded for regular profiles. jacastro@chromium.org src/chrome/browser/site_protection/OWNERS Whether an operating system permission disables the javascript-optimizer. Recorded at profile open. This histogram is only recorded for regular profiles. jacastro@chromium.org src/chrome/browser/site_protection/OWNERS The default JavaScript optimization setting at profile open. Records the setting explicitly set by the user and ignores whether the permission is disabled by an operating system permission or enterprise policy. This histogram is only recorded for regular profiles. engedy@chromium.org src/components/permissions/PERMISSIONS_OWNERS The default sensors setting at profile open. This histogram is only recorded for regular profiles. dullweber@chromium.org src/components/permissions/PERMISSIONS_OWNERS The default storage access setting at profile open. This histogram is only recorded for regular profiles. lshang@chromium.org dullweber@chromium.org engedy@chromium.org The number of user defined content setting exceptions at browser start. Suffixed with the name of content setting types. Histogram content setting type: {ContentSettingsType} This histogram is only recorded for regular profiles as of M109. lshang@chromium.org dullweber@chromium.org engedy@chromium.org The number of user defined content setting exceptions at browser start. Suffixed with the name of content setting types and the content setting. Histogram content setting type: {ContentSettingsType} Histogram content setting: {ContentSetting} This histogram is only recorded for regular profiles as of M109. wenyufu@chromium.org src/components/permissions/PERMISSIONS_OWNERS The default auto dark web content setting at profile open. Recorded for Android only. This histogram is only recorded {RegularProfileFiltered}. engedy@chromium.org src/components/permissions/PERMISSIONS_OWNERS The default autoplay setting at profile open. This histogram is only recorded {RegularProfileFiltered}. engedy@chromium.org src/components/permissions/PERMISSIONS_OWNERS The default cookies setting at profile open. This histogram is only recorded {RegularProfileFiltered}. This histogram was allowed to expire between 2023-02-26 and 2024-01-23. engedy@chromium.org src/components/permissions/PERMISSIONS_OWNERS The default permission setting for idle detection at profile open. This histogram is only recorded {RegularProfileFiltered}. This histogram was allowed to expire between 2022-10-23 and 2023-08-03. engedy@chromium.org src/components/permissions/PERMISSIONS_OWNERS The default image setting at profile open. This histogram is only recorded {RegularProfileFiltered}. This histogram was allowed to expire between 2022-10-23 and 2023-08-03. engedy@chromium.org src/components/permissions/PERMISSIONS_OWNERS The default JavaScript setting at profile open. This histogram is only recorded {RegularProfileFiltered}. engedy@chromium.org src/components/permissions/PERMISSIONS_OWNERS The default location setting at profile open. This histogram is only recorded {RegularProfileFiltered}. engedy@chromium.org src/components/permissions/PERMISSIONS_OWNERS The default camera setting at profile open. This histogram is only recorded {RegularProfileFiltered}. engedy@chromium.org src/components/permissions/PERMISSIONS_OWNERS The default microphone setting at profile open. Warning: this histogram was expired from 2022-06-19 to 2022-09-21; data may be missing. This histogram is only recorded {RegularProfileFiltered}. engedy@chromium.org src/components/permissions/PERMISSIONS_OWNERS The default MIDI permission setting on sysex (system exclusive) messages at profile open. The default microphone setting at profile open. Warning: this histogram was expired from 2022-08-21 to 2022-09-21; data may be missing. This histogram is only recorded {RegularProfileFiltered}. engedy@chromium.org src/components/permissions/PERMISSIONS_OWNERS The default notification setting at profile open. This histogram is only recorded {RegularProfileFiltered}. engedy@chromium.org src/components/permissions/PERMISSIONS_OWNERS The default popups setting at profile open. Warning: this histogram was expired from 2022-08-21 to 2022-09-21; data may be missing. This histogram is only recorded {RegularProfileFiltered}. shuyng@google.com twellington@chromium.org The request desktop site content setting at profile open. Recorded for Android and iOS only. This histogram is only recorded {RegularProfileFiltered}. engedy@chromium.org src/components/permissions/PERMISSIONS_OWNERS The default sound setting at profile open. This histogram is only recorded {RegularProfileFiltered}. engedy@chromium.org src/components/permissions/PERMISSIONS_OWNERS The default subresource filter setting at profile open. Warning: this histogram was expired from 2022-06-19 to 2022-09-21; data may be missing. This histogram is only recorded {RegularProfileFiltered}. engedy@chromium.org src/components/permissions/PERMISSIONS_OWNERS The default permission setting for WebUSB at profile open. This histogram is only recorded {RegularProfileFiltered}. engedy@chromium.org src/components/permissions/PERMISSIONS_OWNERS The default permission setting for Web Bluetooth at profile open. Warning: this histogram was expired from 2022-08-21 to 2022-09-21; data may be missing. This histogram is only recorded {RegularProfileFiltered}. dewittj@chromium.org feed@chromium.org Whether the feed was fetched with activity logging enabled. This is logged on every feed fetch. guiperez@google.com feed@chromium.org Tracks user activity buckets for the filter. Reported every time a metric is reported through the MetricsProvider to allow filtering. The histogram used for analysis is ContentSuggestions.Feed.AllFeeds.Activity, whilst this one will only be used for the filter. Any changes to ContentSuggestions.Feed.AllFeeds.Activity will also change how this metric is reported. adamta@google.com feed@chromium.org When the NTP view hierarchy is fixed upon NTP creation, this hisotgram logs which part was broken. Temporary log used to gather info for crbug.com/1262536. carlosk@chromium.org harringtond@chromium.org feed@chromium.org Android: The time since locally stored content was fetched from the server. Reported when the feed surface is shown, and content is refreshed from the network. This typically only happens when content is stale, so this is a measurement of how stale content is before it's replaced by a blocking refresh. Feed v2 only. carlosk@chromium.org harringtond@chromium.org feed@chromium.org Android: The time since locally stored content was fetched from the server. Reported when the feed surface is shown, and the local persisted feed content is loaded instead of a direct network refresh. This provides a measure of how stale feed content is when the feed loads without a blocking network request. Feed v2 only. jianli@chromium.org feed@chromium.org Android: Reports whether the feed content at the specific position is duplicate to previous contents. The feed contents that are not viewed before are not counted towards the duplication even if they show up again. It is reported when the feed content is received from the server. jianli@chromium.org feed@chromium.org Android: Reports the percentage of the duplicate contents received for a range of cards. The feed contents that are not viewed before are not counted towards the duplication even if they show up again. It is reported when the feed contents are received from the server. jianli@chromium.org feed@chromium.org Android: The invalid age lifetime of content fetched from the server. Reported when new content is served to the feed from the server. This provides a measure of how stale feed content is from the client side. jianli@chromium.org feed@chromium.org Android: If the content lifetime of a feed response has a non zero invalid age when fetched from the server. Reported when new content is served to the feed from the server. This provides a measure of how stale feed content is from the client side. jianli@chromium.org feed@chromium.org Android: The stale age lifetime of content fetched from the server. Reported when new content is served to the feed from the server. This provides a measure of how stale feed content is from the client side. jianli@chromium.org feed@chromium.org Android: If the content lifetime of a feed response has a non zero stale age when fetched from the server. Reported when new content is served to the feed from the server. This provides a measure of how stale feed content is from the client side. jianli@chromium.org feed@chromium.org Android: The display status of the content suggestions when users open NTPs. Whether content suggestions are disabled by policy (e.g. enterprise or supervised users), enabled but collapsed, or enabled and expanded when a new NTP is created. harringtond@chromium.org feed@chromium.org Number of docids sent when loading the Feed from the network. Reported when the Feed is loaded from the network, when docview sending is allowed. This histogram has a maximum count of 1000. harringtond@chromium.org feed@chromium.org If too many document IDs are stored within a short time period, they are dropped rather than recorded in ContentSuggestions.Feed.DocumentViewSendCount. This histogram is recorded when document IDs must be dropped in this way, and reports the number of IDs dropped. tinazwang@chromium.org feed@chromium.org Recorded when a signed out user triggered a sign-in related UI from feed personalization control. iOS only. tinazwang@chromium.org feed@chromium.org Recorded when a user interacts with a Sync Promo inside the Feed, e.g.: accepting the bottom sync promo, or closing the top Sync promos. iOS only. harringtond@chromium.org feed@chromium.org Android: Status of image fetches for the feed. Recorded for each image fetch. Fetches happen when loading the feed or scrolling the feed. Fetched images are cached, so subsequent loads may not fetch again. Feed v2 only. harringtond@chromium.org feed@chromium.org Latencies for individual steps taken to load the feed. This is reported at most once per Chrome execution, and only reported for a Feed load operation that ends with the Feed showing up on the UI. All steps added together tally to the total time taken. Feed v2 only. {FeedLoadLatencyStep} jianli@chromium.org feed@chromium.org Status of loading additional Feed content onto the bottom of the stream. Feed v2 only. jianli@chromium.org feed@chromium.org The interval between current pull-to-refresh time and last time when the feed is refreshed (background refresh or pull-to-refresh), up to 1 day. This is reported when the pull-to-refresh occurs. jianli@chromium.org feed@chromium.org Android: The wire size (potentially compressed) of a {NetworkRequestType} network response received by the Feed's networking host. Recorded when a successful response is received. harringtond@chromium.org feed@chromium.org The amount of time a {NetworkEvent} network event took. harringtond@chromium.org feed@chromium.org Android: the approximate size in bytes of the FeedQuery GET request. Recorded when a FeedQuery is sent. jianli@chromium.org feed@chromium.org Android: the size in kb of gzip-compressed requests sent by the Feed's networking host. Recorded when a request is sent. jianli@chromium.org feed@chromium.org Android: The integer status code of network requests made by the feed library's networking host. This code includes both protocol(1xx-5xx) and non-protocol(-xxx) errors. Recorded when a request completes. jianli@chromium.org feed@chromium.org Android: the uncompressed size in KB of responses received by the Feed's networking host. Recorded when a successful response is received. jianli@chromium.org feed@chromium.org The HTTP response status for a network request made by the Feed component. jianli@chromium.org feed@chromium.org Android: failure reason when attempting to fetch an OAuth token for the feed. Recorded when a token fetch completes. vincb@google.com feed@chromium.org Android: Reports whether the notice card for feed action reporting has been fulfilled. Recorded when reading the response content of the feed query that is successful (includes both load stream and load more queries). vincb@google.com feed@chromium.org Android: Reports whether the notice card for feed action reporting has been fulfilled. Recorded when reading the response content of the load stream query that is successful. adamta@google.com feed@chromium.org Tracks triggers that ask the Discover engine to refresh the feed. However, a network call may or may not occur based on configuration thresholds. jianli@chromium.org feed@chromium.org Android: Status of resource fetches for the feed. Recorded for each resource fetch. Fetches happen when the specific resource is needed to enhance the feed content while the feed is being displayed. carlosk@chromium.org petewil@chromium.org feed@chromium.org Number of each type of feedback sent about the feed. jianli@chromium.org feed@chromium.org How long a user used the Feed in one day (local time midnight to midnight). Reported at most once per day. Usage reported is typically from the previous day, but could be from several days ago if the user is not active. Time is calculated starting with the first Feed interaction, until the Feed surface is closed, or the user is idle (no scrolling or other actions) for 30 seconds. ginnyhuang@chromium.org feed@chromium.org Records the value of Discover uniformity flag each time on app start up, when the Feed is initialized. iOS only. tbansal@chromium.org harringtond@chromium.org feed@chromium.org Records count of entries in the pref store after the store is initialized (which happens during the feed service intiialization). The metric is recorded after the store is cleaned up and conpacted (as part of store initialization). tbansal@chromium.org harringtond@chromium.org feed@chromium.org Recorded everytime when the user clicks a feed link article and an entry is recorded to the user actions collector. The entry may not be recorded in certain cases (not a complete list): the URL of the clicked link was not valid, the MIDs was missing etc. jianli@chromium.org feed@chromium.org Result of attempting to upload a batch of one or more actions. jianli@chromium.org feed@chromium.org Result of an UploadActionsTask run in which zero or more batches of user actions are uploaded. See ContentSuggestions.Feed.UploadActionsBatchStatus for the status of a particular batch upload. freedjm@google.com feed@chromium.org Android: Reports whether the visibility log was uploaded successfully. freedjm@google.com feed@chromium.org Android: Reports whether the {LogType} log was uploaded successfully. jianli@chromium.org feed@chromium.org Counts of Feed user actions. e.g. (Open a Card, Hide the Feed, etc.). Recorded when the user takes an explicit action related to the Feed. harringtond@chromium.org feed@chromium.org Recorded whenever an Elements commands has taken place which wasn't handled explicitly by ContentSuggestions.Feed.UserActions. e.g. A new command to added server side to "Report Content".(iOS only). harringtond@chromium.org carlosk@chromium.org feed@chromium.org Time between the UI requesting additional stream content and failure by either a 15 second timeout or a surface closure. harringtond@chromium.org carlosk@chromium.org feed@chromium.org Time between the UI requesting additional stream content and the content being provided within 15 seconds. Providing content entails showing either a cached or newly fetched Feed card. harringtond@chromium.org carlosk@chromium.org feed@chromium.org Reported when a user taps on a {Surface} card and the page is not loaded successfully within 20 seconds. harringtond@chromium.org carlosk@chromium.org feed@chromium.org The time between a user tapping on a {Surface} card and the page finishes loading successfully. Only reported when loading takes less than 20 seconds. harringtond@chromium.org carlosk@chromium.org feed@chromium.org The time between a {Surface} opening and either providing user content, or failing to provide content. Providing content entails showing either a cached or newly fetched Feed card within 15 seconds. Success is reported upon view of the card. Failure is reported when either the surface is closed or a timeout of 15 seconds expires. carlosk@chromium.org harringtond@chromium.org feed@chromium.org The state of some account settings that affect Feed users. Reported once at startup (to a single bucket), for all users. Note that this histogram uses data cached from the last time the Feed was fetched. Android only. jianli@chromium.org feed@chromium.org Tracks the number of cards viewed at the time of pull-to-refresh. This is reported when the pull-to-refresh occurs. This is computed as the number of cards that are viewed (2/3rds of card is in the viewport) since last time when the feed is refreshed (background refresh or pull-to-refresh). jianli@chromium.org feed@chromium.org Tracks the percentage of cards viewed at the time of pull-to-refresh. This is reported when the pull-to-refresh occurs. This is computed as the percentage of cards that are viewed (2/3rds of card is in the viewport) since last time when the feed is refreshed (background refresh or pull-to-refresh). freedjm@google.com feed@chromium.org Android: Reports whether visibility logging is enabled when logging is attempted. harringtond@chromium.org freedjm@chromium.org feed@chromium.org Android: Time spent reading the page linked by an opened suggestion card. This is a lower-bound time. Does not include time after Chrome is closed and re-opened. Does not include time after the visited tab no longer has focus, or after the tab is navigated. For the 'open in new tab' action, time starts when the user switches to the new tab. If the user returns by tapping the suggestion again, it will be recorded as another entry in this histogram. Feed v2 only. jianli@chromium.org feed@chromium.org Android: records errors occurred during the video player initialization. The embedded video player needs to be initialized before it can be used to play a video in {PlayType} mode. In autoplay muted mode, the initialization may kick off even before the video view is scrolled to become visible. In normal unmuted mode, this happens when the user taps the video to launch the video in fullscreen playing mode. jianli@chromium.org feed@chromium.org Android: records errors occurred during the video playing, in {PlayType} mode. Upon the successful initialization of the embedded player, the video starts to play and any error occurs since then is reported here. jianli@chromium.org feed@chromium.org Android: records events triggered during the video playing, in {PlayType} mode. guiperez@google.com feed@chromium.org Tracks user activity buckets with {FeedType}. Each bucket composed of the user's activity level. Logs the for the first time 1 day after the metric is active (only on first time use), then logs an activity bucket after at least 24hrs from the last log have elapsed. When the "Engaged" metric is triggered we log one more day of activity during the past 28 days. jianli@chromium.org feed@chromium.org Tracks user behavior with {FeedType}. Each bucket is one of two types of metric. Per-visit metrics sample once per "visit", which is a cluster of user activities separated by less than 5 minutes of inactivity. Per-visit metrics record a sample at the moment that the visit's criteria are first met. Per-interaction metrics are not clustered and report samples immediately. In the UI, Bucket Proportion and Total Count are not meaningful as these metrics are not independent. All buckets of this metric can be moved by changes in the Discover service as well as by client changes. go/discover-oncall describes how to get in touch with Discover oncall engineers. jianli@chromium.org adamta@google.com feed@chromium.org Reports when {Action} has occurred for an info card. The type of the info card was reported. Available in iOS as of M126. harringtond@chromium.org feed@chromium.org Android: Reports the total number of cards when the {FeedType} data is successfully loaded to be presented to the user. Reported after an initial load. Not reported after a NextPage request. When loading data from local storage, previously fetched NextPage cards are counted though. dewittj@chromium.org feed@chromium.org The number of cards not yet scrolled into visibility at the moment the Feed decides to load more content. dewittj@chromium.org feed@chromium.org The total number of cards in the feed stream at the moment the Feed decides to load more content. jianli@chromium.org feed@chromium.org Android: Status of loading new {FeedType} data in the background. Reported any time Chrome attempts to fetch fresh Feed content in the background. This is either due to a background fetch schedule, or when fetching the Web-Feed while the For-You feed is active. jianli@chromium.org feed@chromium.org Android: Status of loading the initial {FeedType} stream, which happens when the {FeedType} surface is shown. Feed v2 only. jianli@chromium.org feed@chromium.org Android: The status of loading the Feed from the local store. Reported when loading the Feed for display. Recorded at the same time as ContentSuggestions.{FeedType}.LoadStreamStatus.Initial to differentiate between store errors and network fetch results. jianli@chromium.org feed@chromium.org Android: status of pulling-to-refresh the {FeedType} stream per the user request. Reported when the refresh completes. harringtond@chromium.org feed@chromium.org Android: Reports the number of cards in the {FeedType}. Reported when the last card of the {FeedType} is shown. Note that this is reported even if the Feed is attempting to load additional content (LoadMore), as long as the last card is 2/3rds shown before additional content loads. In this case, this histogram can be reported multiple times without leaving the Feed surface. harringtond@chromium.org feed@chromium.org Android: Reports the total size in KB of the shared state for the {FeedType}. Reported once when loading {FeedType} content for display, and once each time additional pages of content are added. jianli@chromium.org feed@chromium.org Android: Reports the total size in KB of all of the {FeedType} content (not including shared state, or dynamically fetched media). Reported once when loading {FeedType} content for display, and once each time additional pages of content are added.