toolkit/components/antitracking/bouncetrackingprotection

firefox-main/toolkit/components/antitracking/bouncetrackingprotection

	Name	Description	Size	Coverage
	BounceTrackingAllowList.cpp		1560	100 %
	BounceTrackingAllowList.h		753	-
	BounceTrackingMapEntry.cpp		1342	86 %
	BounceTrackingMapEntry.h	Represents an entry in the global bounce tracker or user activation map.	2758	100 %
	BounceTrackingProtection.cpp		55138	85 %
	BounceTrackingProtection.h		8425	53 %
	BounceTrackingProtectionStorage.cpp		40434	90 %
	BounceTrackingProtectionStorage.h		10852	38 %
	BounceTrackingRecord.cpp		1923	100 %
	BounceTrackingRecord.h		3308	13 %
	BounceTrackingState.cpp		35218	80 %
	BounceTrackingState.h	This class manages the bounce tracking state for a given tab. It is attached to top-level CanonicalBrowsingContexts.	7356	14 %
	BounceTrackingStateGlobal.cpp		9659	86 %
	BounceTrackingStateGlobal.h	This class holds the global state maps which are used to keep track of potential bounce trackers and user activations. @see BounceTrackingState for the per browser / tab state. Updates to the state maps are persisted to storage.	6627	35 %
	BTPRemoteExceptionList.sys.mjs	Called for remote settings "sync" events.	2878	82 %
	ClearDataCallback.cpp		7618	91 %
	ClearDataCallback.h		2111	0 %
	components.conf		1537	-
	metrics.yaml		6397	-
	moz.build		1545	-
	nsIBounceTrackingMapEntry.idl	This interface represents an entry in the global bounce tracker or user activation map.	1443	-
	nsIBounceTrackingProtection.idl	Modes for Bounce Tracking Protection MODE_DISABLED - Feature fully disabled and not initialized at startup. No user activation signals are collected. Requires a restart to apply. MODE_ENABLED - Feature fully enabled. This includes: collection of user activation signals, classification of bounce trackers, periodic purging of bounce trackers. MODE_ENABLED_STANDBY - Tracker classification and purging is disabled. User activation signals are still collected and stored. MODE_ENABLED_DRY_RUN - Dry-run mode: The feature is fully enabled, but tracker purging is simulated. No site data is purged. Purge telemetry still gets collected. This mode is helpful for testing the feature without risking data loss. For toggling the feature in privacy settings UI switch between MODE_ENABLED and MODE_ENABLED_DRY_RUN. This is important so that user activation signals and telemetry are still collected even if the feature is "turned off" for the user. In the future when we're done collecting telemetry we may switch this to MODE_ENABLED_STANDBY where we still collect user activation signals but do not simulate purging. Fully enabling / disabling the feature (MODE_DISABLED -> x or x -> MODE_DISABLED) requires a restart to apply.	5472	-
	nsIBounceTrackingRecord.idl	This interface exposes the per-tab bounce tracking record that captures the redirect chain context for a navigation.	796	-
	nsIBTPRemoteExceptionList.idl	Helper for syncing remote settings exception list to BounceTrackingProtection.	852	-
	pings.yaml		817	-
	ProfileAfterChangeGate.cpp		842	100 %
	ProfileAfterChangeGate.h		699	-
<1%	test			-

Revision control

Other Tools