After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 501876 - Alternatives for misspelled words inside the right click popup menu
Alternatives for misspelled words inside the right click popup menu
Status: RESOLVED DUPLICATE of bug 637021
Product: epiphany
Classification: Core
Component: General
git master
Other All
: Normal normal
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks: 523868
 
 
Reported: 2007-12-05 19:53 UTC by Christoph Langner
Modified: 2010-12-15 19:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Christoph Langner 2007-12-05 19:53:47 UTC
Please describe the problem:
When i set the key "layout.spellcheckDefault" to "1" inside about:config Epiphany marks misspelled words with a red line, like Firefox, gedit etc. Usually you can click with the right mouse button onto those words and inside the popup menu you can select alternatives which might correct your spelling mistakes. But Epiphany doesn't show anything. Just the usual copy and paste actions.

Steps to reproduce:
1. Activate spellchecking with "layout.spellcheckDefault=1" inside about:config
2. Type "teest" inside a textbox, e.g. at bugzilla.gnome.org
3. Click with the right mouse button onto the marked text


Actual results:
Nothing, no alternatives visible

Expected results:
Epiphany should give me a list of possible alternatives like e.g. gedit

Does this happen every time?
Yes

Other information:
Comment 1 Reinout van Schouwen 2007-12-06 17:57:50 UTC
I'd swear this was a duplicate of an existing bug, but I can't find it right now.
In any case, the problem is known, it's simply waiting for someone to pick it up...
Comment 2 Diego Escalante Urrelo (not reading bugmail) 2010-12-15 19:41:46 UTC
To be done in bug #637021

*** This bug has been marked as a duplicate of bug 637021 ***