Lines Matching full:safe
4337 of this method was very simple and thread safe.
4408 safe to allow event an empty URL.
5990 is non-zero. We would return YES here when it wasn't safe and later crash with my modified layout tests.
8658 It's now safe to remove it from the header.
10706 to match the logic that's in the derived classes. This makes it safe for
11016 mostly safe levels.
16379 means it is safe to use our FontPlatformData -> FontData cache.
19902 safe way to manage the lifetime of objects that inherit from Shared.
24666 into CFNetwork functions, which are not null-safe.
34093 dependency on originRootObject, but I wanted to be safe.
39789 that _imp is no longer GC protected, so it's not safe to use.
42397 These are small changes that are either safe to do first, or unrelated to the main
44993 Document::completeURL, since FrameLoader::completeURL is safe against a
47513 the idea behind it was that there are times when it is safe for
47517 immediately when it was not safe. Mitz and I discussed this online
49497 method was never really safe to call unless it was AppKit that called your
51647 app should use the older, less safe, behavior.
54289 <rdar://problem/4900579> WebKit -finalize methods are not thread-safe; design change needed
55066 thing that will ever call us, but lets play it safe
57933 So, the page destructor has to cancel keepAlive for all frames. This is safe
63204 before dispatching the event. It is safe to remove the check for
