Lines Matching refs:Grammar
1662 // FIXME: On Mac OS X, when use "learn" button on "Spelling and Grammar" panel, we don't call this function. It should remove misspelling markers around the learned word, see <rdar://problem/5396072>.
1765 // Search for bad grammar that occurs prior to the next misspelled word (if any)
1779 // If we found neither bad grammar nor a misspelled word, wrap and try again (but don't bother if we started at the beginning of the
1816 // We found bad grammar. Since we only searched for bad grammar up to the first misspelled word, the bad grammar
1817 // takes precedence and we ignore any potential misspelled word. Select the grammar detail, update the spelling
1829 frame()->document()->markers()->addMarker(badGrammarRange.get(), DocumentMarker::Grammar, grammarDetail.userDescription);
1831 // We found a misspelling, but not any earlier bad grammar. Select the misspelling, update the spelling panel, and store
1864 // or a grammar error.
1954 frame()->document()->markers()->removeMarkers(selectedRange.get(), DocumentMarker::Grammar);
2044 // Check grammar of entire sentence
2055 // grammar checking can only be on if spell checking is also on.
2206 grammarRange->startContainer(ec)->document()->markers()->addMarker(badGrammarRange.get(), DocumentMarker::Grammar, detail->userDescription);
3165 // Don't check spelling and grammar if the change of selection is triggered by spelling correction itself.
3190 m_frame->document()->markers()->removeMarkers(sentenceRange.get(), DocumentMarker::Grammar);
3197 m_frame->document()->markers()->removeMarkers(DocumentMarker::Grammar);
