Lines Matching full:sense
7512 This optimization doesn't make sense for some composite mode (e.g., 'copy' operation).
14668 It may make sense to harmonize these cases one day, but for now, I only made the minimal
16598 (it makes no sense to revalidate one that isn't).
26960 ASSERT(node) to the top of the function it made sense to move the rest of them there too.
27421 When hit-testing 3d-transformed layers, it doesn't make sense to project the hitTestRect
27632 It never makes sense to change the node and leave the offset.
29407 doesn't make sense to keep the anchor after programmatically changing the selection, and
32231 Bug 22790: [Transforms] MediaPlayer::setRect() makes no sense with transforms
32509 (WebCore::TypingCommand::deleteKeyPressed): Don't do any of the things that only make sense for Range selections, like
59615 (in the sense of inline caching) call to it, bypassing the check of whether or
61855 this didn't actually make that much sense.
65096 to fire. We can stop them all before firing onunload but it does not make a lot of sense.
67651 to terminate (this is not mentioned in draft spec, but makes sense anyway).
68402 in this case, and there is no sense in starting a thread and trying to parse document source
68945 but this does not make sense for scrollbars.
71203 to check editingIgnoresContent. It makes sense to use the associated DOM node for
87102 - introduce a TypeInfo class, for holding per-type (in the C++ class sense) date in StructureID
