Lines Matching full:safe
1562 Rewrite users of ImageDecoder.h to use "safe" API calls, Skia side.
6567 on Windows always thread safe. So use them in the cases where
7916 (WebCore::GraphicsContext::fillPath): Changed to call the safe variants
8840 messaging nil will return 0 (size of a pointer), so it's safe to message nil
11253 (WebCore::HTMLMediaElement::loadResource): ASSERT that the URL is safe to load as we now
11255 (WebCore::HTMLMediaElement::isSafeToLoadURL): New, checks to see if a url is safe to load, logs
23407 its node's wrapper was collected anyway, but it's nice to be safe.
26491 event listener in a type safe manner.
30390 that since internalAbort() can drop GC protection, it is not safe to use the object after
48852 This is a rather unstable situation, as it is often unclear whether a given string is safe
55795 this is code borrowed from ICU, this seems like a simple safe change to make.
59682 Bug 23006: Many Loader::Host member functions are not safe to use reentrantly
62718 simply ask the platform widget whether this is safe on platforms that
63604 Make networkStateNotifier() static constructor thread safe. The object is created on the
63606 onLine() from other threads are safe, because it is just loading a boolean.
66408 Made static initializations in XMLHttpRequest.cpp thread-safe in preparation for usage
67070 Made the PreflightResultCache thread-safe in preparation for usage of XMLHttpRequest by
69633 when posting a task - this operation is not thread safe. It is also not necessary any more,
69642 available. Also, it is now safe to unsetPendingActivity(), making the object collectable.
69664 execution context, making it safe to post messages to it remotely.
70555 one to worker. Since message port registration in ScriptExecutionContext is not thread safe,
70586 Assert being called from the correct thread, as active DOM object tracking is not thread safe.
72673 thread safe.
74115 work in worker contexts - we need to also make some its method thread safe for cross-thread
74116 messaging, and make event dispatching thread safe.
82038 The static domObjects map was not thread safe.
85651 Added a MessagePort implementation. Currently, it is not thread-safe at all, and only works
91807 names of JNI functions, and I will check if these are safe to change
94336 safe to execute.
