Lines Matching full:sense
4916 we're navigating to a HistoryItem, it doesn't make sense to ask whether
24636 about needing to honor it if the textContent of the output doesn't make sense.
28603 (in the JS sense), but the C++ class doesn't, so properly
28964 so it doesn't make sense to include it as kjs/Profiler.h from WebCore.
32905 concept of "OriginStorage" as a "storage area", which makes more sense here.
47244 doesn't return NULL. This make sense, since we only need to protect the
52626 For SVGAElement - for example - it makes most sense to test scripting its parent
54177 sense, because widgets can't navigate their top-level frames, anyway.
56950 Post requests on files don't really make sense, but for
60634 I am not sure why this behaviour is desired, no comment given in spec - doesn't make much sense to me, ignoring it for now.
61116 more sense.
67887 transaction. Note that in this patch, the quota being set is wrong - it makes sense to fix that in a follow up patch
72942 (WebCore::HTMLSelectElement::defaultEventHandler): Nil check the renderer here. None of the default behavior makes sense if there's no renderer.
74114 (WebCore::SegmentedSubstring::SegmentedSubstring): Reversed the sense of m_excludeLineNumbers
74119 (WebCore::SegmentedString::advance): Use doNotExcludeLineNumbers to reverse the sense and fix
74522 Removed a comment mentioning removeRange(), as this method makes no sense without multiple
75206 this was true, but computed style has no concept of implicit. So false makes more sense
76906 FIXME that doesn't seem to make any sense. Note that append() behavior doesn't
79163 Since DatabaseTracker is a singleton, it makes much more sense to keep the database path as a member variable.
