Home | History | Annotate | Download | only in WebCore

Lines Matching full:fire

221           onClick event for TD element doesn't fire unless its contents are clicked
16354 - fixed <rdar://problem/3598589> onunload handler doesn't fire when a window is closed
18980 widget update causes the onload for the document to fire. Because you can be in the middle of a style
19571 for that relatively obscure case, which means the event handlers won't fire at all; might be incorrect
22656 - fixed <rdar://problem/4025088> window onblur and onfocus don't fire when text field has focus
24278 to ensure that the onload handler would fire. This is unnecessary for xml documents,
26914 (KHTMLPart::processObjectRequest): m_bComplete was never true for frames generated by Javascript due to our synchronous loading and as a result, scheduled redirects wouldn't fire in KHTMLPart::scheduleLocationChange(). By virtue of being an empty document, a document is complete. In this special case it's safe at this point to call checkCompleted() which sets m_bComplete true.
30288 (DocumentImpl::close): Don't fire the onload handler if there is a
31390 (QTimer::fire):
31449 - fixed <rdar://problem/3825966> 8A274 Safari crashes closing window: QTimer::fire() with MallocStackLogging and MallocScribble enabled
31451 * kwq/KWQTimer.mm: (QTimer::fire): Rearrange so we don't access the QTimer object after calling code
41629 (QTimer::fire): Use KWQRelease instead of release.
53275 loading and fire all the right signals.
55186 (KJS::XMLHttpRequest::send): Fire up a post or get job.
55225 page often causes a white flash. Fix for 3488827, XML/XHTML documents don't fire load events on bodies/framesets.