#23322 closed defect (bug) (fixed)
The lookup in text editor does nothing when I enter text in hebrew
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | normal | Milestone: | 3.6 |
| Component: | Editor | Version: | |
| Severity: | minor | Keywords: | has-patch commit |
| Cc: | mboynes, sobkowicz, jonbish@… |
Description
- In the text editor Click lookup
- In the window enter hebrew text and submit
- 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
- What is the purpose of that button?
- Why answers.com? It is hardcoded in JS
- If this is useful, why there is no such button in the visual editor?
Attachments (6)
Change History (17)
comment:3
nacin
— 5 months ago
- Milestone changed from Awaiting Review to 3.6
Have never noticed this.
comment:4
mboynes
— 4 months 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.
comment:5
jonbishop
— 4 months 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?
jonbishop
— 4 months ago
This removes all references to 'spell' in quicktags args and the javascript that triggers the lookup
comment:6
sobkowicz
— 4 months 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.
SergeyBiryukov
— 4 months ago
comment:7
SergeyBiryukov
— 4 months ago
- Keywords commit added; needs-testing removed
23322.patch looks good to me.
23322.2.patch removes a couple more references.
comment:8
follow-up:
↓ 9
jonbishop
— 4 months 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.
comment:9
in reply to:
↑ 8
SergeyBiryukov
— 4 months ago
I guess dictionaryLookup and lookup can be removed too.
comment:10
nacin
— 2 months ago
- Owner set to nacin
- Resolution set to fixed
- Status changed from new to closed
In 24052:
comment:11
nacin
— 2 months ago
I decided to leave qt.SpellButton = function() {]; in there, just to avoid potential JS errors with plugins.
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]).