Ticket #6099 (assigned defect)

Opened 6 years ago

Last modified 19 months ago

browser's Spell Check does not offer alternatives

Reported by: skierpage Owned by: humitos
Priority: normal Milestone: Future Release
Component: browse-activity Version: Build 650
Keywords: Cc: erikos, manuq, gonzalo, humitos
Action Needed: never set Verified: no
Deployments affected: Blocked By:
Blocking:

Description

In Browse, go to a web site and enter mis-spelled words in any textarea (like this page).

The Gecko engine's spell checker underlines "badword" in red, but there's no access to corrections.

I don't know if this is simply lack of a right-button context menu in Browse, or a design issue. Apparently Write has the same issue (bug 5394).

Obviously, spell check should work identically in the Write, Browse, anything else using XULRunner, and any other program with text input.

Change History

Changed 6 years ago by marco

  • milestone changed from Never Assigned to Future Release

Changed 5 years ago by skierpage

  • next_action set to never set

It seems in 8.2.0 there's no spell check in Browse at all -- I don't see any red dots. Only the Firefox activity has spell checking.

Changed 19 months ago by humitos

  • cc erikos, manuq, gonzalo, humitos added
  • owner changed from erikos to humitos
  • status changed from new to assigned

The current version of Browse (using WebKit) does not have spell checking at all.

Is this feature a regression? Should we give priority to it?

Note: See TracTickets for help on using tickets.