Open Bug 389351 Opened 17 years ago Updated 2 years ago

Spell-checking underlines can extend outside contenteditable element

Categories

(Core :: Spelling checker, defect)

x86
Windows XP
defect

Tracking

()

REOPENED

People

(Reporter: martijn.martijn, Unassigned)

References

Details

(Keywords: testcase)

Attachments

(1 file)

Attached file testcase
See testcase, I can see the dotted underline from the spellchecker outside the contenteditable element.
It seems to me that spellchecking should stop when the contenteditable boundaries of the element have been reached.
Assignee: mscott → nobody
Martijn, do you still see this?  I think I don't see what you are describing

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.3a3pre) Gecko/20100305 Minefield/3.7a3pre (.NET CLR 3.5.30729)

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.2pre) Gecko/20100302 Lanikai/3.1b1
It can still happen, it's just that the testcase doesn't show it anymore. That might be a new bug, in itself.
This problem shows up on the HTML5 showcase website.  http://html5demos.com/contenteditable  If you click into the contenteditable area the text above it shows spelling errors.
(In reply to comment #3)
> This problem shows up on the HTML5 showcase website. 
> http://html5demos.com/contenteditable  If you click into the contenteditable
> area the text above it shows spelling errors.

This test case is not valid, since it has this code:

addEvent(editable, 'focus', function () {
  document.designMode = 'on';
});

Which puts the document inside design mode when you focus the editable area, which causes ContentEditable to be highlighted as an invalid word.
(In reply to comment #4)
> (In reply to comment #3)
> > This problem shows up on the HTML5 showcase website. 
> > http://html5demos.com/contenteditable  If you click into the contenteditable
> > area the text above it shows spelling errors.
> 
> This test case is not valid, since it has this code:
> 
> addEvent(editable, 'focus', function () {
>   document.designMode = 'on';
> });
> 
> Which puts the document inside design mode when you focus the editable area,
> which causes ContentEditable to be highlighted as an invalid word.

Thanks did not notice that. I tried to recreate the error on my own and could not http://qw3n.com/bugzilla/editSpell.php.
OK.  Please reopen if you can reproduce.  Thanks!
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
New steps to reproduce:
- Load testcase
- Click on the start of the contenteditable div, before the 'f' in 'fire'.
- Press the spacebar key
- Click outside the contenteditable div.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Right.  Comment 7 has a valid STR.
Status: REOPENED → NEW
Status: NEW → RESOLVED
Closed: 13 years ago7 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---

I can still repro this per comment #7, and I wonder whether this is related to editor module. Masayuki, do you have some idea?

Flags: needinfo?(masayuki)

I think that it's because TextServiceDocument works with block elements like here.

Flags: needinfo?(masayuki)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: