Lines Matching full:child
763 (-[WebInspector outlineView:child:ofItem:]):
1184 I moved some logic down from Safari that dealt with finding the largest scrollable child frame in a frameset,
1194 if we don't have scroll bars, operate on our largest child with scroll bars instead
1207 child with scroll bars, and don't bail out if so
1213 new method, returns the child with the largest area that is showing at least one scroll bar
1494 seem directly relevant to adding a child.
1505 (-[WebFrame _childFramesMatchItem:]): Get child frame count in the new
1509 (-[WebFrame _generateFrameName]): Get child frame count in the new
1560 of looking in child arrays (duh)
1574 (-[WebFrame _deepLastChildFrame]): renamed from _lastChildFrame, rewrite to use child
5089 not available when child opened via target="_new"
6534 <rdar://problem/3584942> AX: Safari Accessibility parent-child mismatch
7985 <rdar://problem/3584942> AX: Safari Accessibility parent-child mismatch
9321 (-[WebFrame _addChild:]): Updates the previous frame and the next frame after this child
12339 Nasty problem. It turns out that these result pages are a parent frame with two child
12340 frames. One of the child frames is a 1 or 2 byte text document. When the text child
23524 Nil out the parent pointer in the removed child.
32711 the new child to self's group. This was a typo from the
33681 blank pages, and the WebHistoryItem manipulations we do for b/f and reload of child frames.
35275 should restore child frame content like reload does.
35415 The root of this problem was that we would detach child frames by calling detach
35418 entire frame tree. But if a previously detached child is still sitting in that
