Make WordPress Core

Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#23322 closed defect (bug) (fixed)

The lookup in text editor does nothing when I enter text in hebrew

Reported by: mark-k Owned by: nacin
Milestone: 3.6 Priority: normal
Severity: minor Version:
Component: Editor Keywords: has-patch commit
Focuses: Cc:


  1. In the text editor Click lookup
  2. In the window enter hebrew text and submit
  3. Window closes but nothing else happens

For english text a tab is opened with proper page from answers.com or a "can't find" page.

Several questions

  1. What is the purpose of that button?
  2. Why answers.com? It is hardcoded in JS
  3. If this is useful, why there is no such button in the visual editor?

Attachments (6)

remove-lookup-button.diff (523 bytes) - added by mboynes 5 years ago.
Removing lookup button from quicktags array
23322.patch (4.0 KB) - added by jonbishop 5 years ago.
This removes all references to 'spell' in quicktags args and the javascript that triggers the lookup
23322.2.patch (4.9 KB) - added by SergeyBiryukov 5 years ago.
23322.3 (5.5 KB) - added by jonbishop 5 years ago.
23322.3.patch (5.5 KB) - added by jonbishop 5 years ago.
23322.4.patch (5.6 KB) - added by jonbishop 5 years ago.
Removed dictionaryLookup and lookup

Download all attachments as: .zip

Change History (17)

#1 @dd32
5 years ago

This appears to be some kind of Spell button in Quicktags: http://core.trac.wordpress.org/browser/trunk/wp-includes/js/quicktags.js#L502

I would assume that Hebew text doesn't pass as "word" characters in Javascript regular expressions causing nothing to happen.

I uh, vote to remove the button myself, it doesn't appear to be anything of use, When it was added 9 years ago, answers.com may have actually been useful.

For reference, answers.com was added in [2476] (previously it was dictionary.reference.com, which was either present in b2, or added somewhere around WordPress changeset [300]).

#2 @mark-k
5 years ago

+1 for removal, looks totally useless.

#3 @nacin
5 years ago

  • Milestone changed from Awaiting Review to 3.6

Have never noticed this.

#4 @mboynes
5 years ago

  • Cc mboynes added
  • Keywords has-patch needs-testing added

I agree, this is pretty useless. Sorry answers.com, no more free traffic for you.

I just added a patch that removes the button from the toolbar, but doesn't remove the functionality (in the event that someone uses it, this will allow them to add it back very easily). I moved the "close" button up in the array as well from key 140 to key 130.

5 years ago

Removing lookup button from quicktags array

#5 @jonbishop
5 years ago

Do we want to leave the functionality in there? I feel like it's easy enough to add back in as a plugin and why leave something like that hidden in core.

Also, don't we need to remove 'spell' from the quicktag settings anywhere we manually call the editor?

5 years ago

This removes all references to 'spell' in quicktags args and the javascript that triggers the lookup

#6 @sobkowicz
5 years ago

  • Cc sobkowicz added

I tested this patch (by jonbishop) and it appears to work. I think taking out this functionality is fine as well.

#7 @SergeyBiryukov
5 years ago

  • Keywords commit added; needs-testing removed

23322.patch looks good to me.

23322.2.patch removes a couple more references.

5 years ago

5 years ago

#8 follow-up: @jonbishop
5 years ago

  • Cc jonbish@… added

Incorporated the fixes from 23322.2.patch into 23322.3.patch which removes wordLookup from the localized quicktagsL10n array that gets added to the header in the admin.

#9 in reply to: ↑ 8 @SergeyBiryukov
5 years ago

I guess dictionaryLookup and lookup can be removed too.

5 years ago

Removed dictionaryLookup and lookup

#10 @nacin
5 years ago

  • Owner set to nacin
  • Resolution set to fixed
  • Status changed from new to closed

In 24052:

Remove ancient 'lookup' quicktag from the text editor. This had called up answers.com.

props mboynes, jonbishop, SergeyBiryukov.
fixes #23322.

#11 @nacin
5 years ago

I decided to leave qt.SpellButton = function() {]; in there, just to avoid potential JS errors with plugins.

Note: See TracTickets for help on using tickets.