Name Description Size
android 2
cocoa 4
fallback 10
Hal.cpp 19500
Hal.h Hal.h contains the public Hal API. By default, this file defines its functions in the hal namespace, but if MOZ_HAL_NAMESPACE is defined, we'll define our functions in that namespace. This is used by HalImpl.h and HalSandbox.h, which define copies of all the functions here in the hal_impl and hal_sandbox namespaces. 11561
HalImpl.h 638
HalInternal.h This file is included by HalImpl.h and HalSandbox.h with a mechanism similar to Hal.h. That means those headers set MOZ_HAL_NAMESPACE to specify in which namespace the internal functions should appear. The difference between Hal.h and HalInternal.h is that methods declared in HalInternal.h don't appear in the hal namespace. That also means this file should not be included except by HalImpl.h and HalSandbox.h. 2304
HalLog.h HalLog.h contains internal macros and functions used for logging. This should be considered a private include and not used in non-HAL code. To enable logging in non-debug builds define the PR_FORCE_LOG macro here. 968
HalSandbox.h 582
HalScreenConfiguration.h 656
HalSensor.h Enumeration of sensor types. They are used to specify type while register or unregister an observer for a sensor of given type. If you add or change any here, do the same in GeckoHalDefines.java. 2047
HalTypes.h These constants specify special values for content process IDs. You can get a content process ID by calling ContentChild::GetID() or ContentParent::GetChildID(). 3430
HalWakeLock.cpp 7442
HalWakeLock.h Return the wake lock state according to the numbers. 690
linux 1
moz.build 3606
sandbox 3
WindowIdentifier.cpp 1679
WindowIdentifier.h This class serves two purposes. First, this class wraps a pointer to a window. Second, WindowIdentifier lets us uniquely identify a window across processes. A window exposes an ID which is unique only within its process. Thus to identify a window, we need to know the ID of the process which contains it. But the scope of a process's ID is its parent; that is, two processes with different parents might have the same ID. So to identify a window, we need its ID plus the IDs of all the processes in the path from the window's process to the root process. We throw in the IDs of the intermediate windows (a content window is contained in a window at each level of the process tree) for good measures. You can access this list of IDs by calling AsArray(). 3185
windows 2