Get rikaikun to work with text boxes.

[GoogleCodeExporter]

I'm not sure this is possible, but the lack of the ability is much worse than 
not being able to parse buttons so I'm going to try hard.

Might require a webkit patch.

Original issue reported on code.google.com by melin...@gmail.com on 7 Jan 2010 at 12:45

[GoogleCodeExporter]

Original comment by melin...@gmail.com on 7 Jan 2010 at 2:10

• Changed state: Started

[GoogleCodeExporter]

This is impossible in current chrome.  caretRangeFromPoint doesn't work with 
control 
elements at all.  I'll try to patch webkit in the future.

Original comment by melin...@gmail.com on 7 Jan 2010 at 3:10

• Changed state: Accepted
• Added labels: Priority-Low
• Removed labels: Priority-High

[GoogleCodeExporter]

Original comment by melin...@gmail.com on 8 Jan 2010 at 7:27

• Added labels: Milestone-ReleaseX.0

[GoogleCodeExporter]

I'm not sure it's the same issue, but pages like WWWJDIC
( http://www.csse.monash.edu.au/~jwb/cgi-bin/wwwjdic.cgi?1C )
have very buggy word detection and seem to choose randomly which words are 
detected by 
rikaikun. If not due to text boxes, it's probably a similar issue at least.

Original comment by pedroave...@gmail.com on 18 Jan 2010 at 1:47

[GoogleCodeExporter]

I noticed WWWJDIC working poorly before, and reported it in issue 26.  It's 
hopefully 
fixed in the source and will be made public in the next release this week I 
think.

I don't know if there's another problem with the site but it's been working 
good in my 
development version as far as I could tell.

Original comment by melin...@gmail.com on 18 Jan 2010 at 2:09

[GoogleCodeExporter]

Issue 32 has been merged into this issue.

Original comment by melin...@gmail.com on 22 Jan 2010 at 2:19

[GoogleCodeExporter]

Does somebody has a solution for this serious problem ? 
When writing mails in gmail, it s a big problem if we can't understand the 
kanji's we 
are using.

Please help rikaikun users :)

If somebody has a solution, i ll be happy to make the modification.

Original comment by mikaelle...@gmail.com on 3 Jun 2010 at 4:59

[GoogleCodeExporter]

Thanks for bringing this back up. I think I know how someone might be able to 
fix the 
problem. May I suggest you look at the following extension:
https://chrome.google.com/extensions/detail/kecaejkkcpijbbnnmnkpcpgiifdplcia

This extension allows you to select text, then hit a keyboard shortcut, and up 
pops the 
definition. It also works for selected text within a textbox. Why not try to 
mimic the 
abilities of that extension? I wish I could do it, but I have no experience 
with Chrome 
extensions. A keyboard shortcut method could be a nice work around.

Original comment by derekAthomas@gmail.com on 3 Jun 2010 at 5:09

[GoogleCodeExporter]

Issue 44 has been merged into this issue.

Original comment by melin...@gmail.com on 18 Jun 2010 at 7:03

[GoogleCodeExporter]

muito bom, mas poderia melhorar e traduzir nao somente para o ingles, mas para 
outros idiomas tambem. principalmente o portugues.....obrigado

Original comment by moskaf...@gmail.com on 26 Jun 2010 at 3:17

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I'm guessing this is related to the same text box issue... but I'll add my 
specific instance of it.

On the page http://excite.co.jp/world/english/ I enter in the following text in 
the textbox on the left (the text to be translated):

私はジャスティンです。

"僕は" or　" 俺は" etc. 

It doesn't matter where you place the mouse in the textbox, it always shows the 
same thing for the whole textbox. It seems like before I translate it it shows 
此方, and after I click translate, it then shows 私. Not sure if that 
matters.

Rikaichan works correctly on the exact same page and kana/kanji and shows the 
different information for 私, 僕, and 俺.

Original comment by jstress...@gmail.com on 19 Jul 2010 at 12:59

[GoogleCodeExporter]

I really think this should be a high priority issue. As of now 148 people have 
starred it, and I'm sure because most of them miss it from Rikaichan.

Original comment by erik...@gmail.com on 13 Nov 2010 at 11:40

[GoogleCodeExporter]

Right, I think this is an important issue as well.  The reason the priority is 
low is because the amount of work is immense.  I have to go through all the 
hoops of patching webkit and then getting the patch added up stream and then I 
can write something that works like rikaichan.

Maybe the Webkit/chrome people will decide the necessary change isn't what they 
want, in which case this will always be impossible.

In the mean time, what would be a suitable replacement?  What about if you had 
to select the text first and then hit a button/key stroke in order to bring up 
the definition?

Original comment by melin...@gmail.com on 14 Nov 2010 at 3:35

[GoogleCodeExporter]

I'd be okay with an extra key stroke or two for that functionality.

Original comment by crowb...@gmail.com on 14 Nov 2010 at 4:10

[GoogleCodeExporter]

Absolutely -- sounds like a good compromise...

Original comment by jmarklytle on 14 Nov 2010 at 4:13

[GoogleCodeExporter]

In my opinion that would be a great replacement for now.

Original comment by heavenne...@gmail.com on 14 Nov 2010 at 4:15

[GoogleCodeExporter]

I think so too. I would be happy with that.

Original comment by reedsinj...@gmail.com on 14 Nov 2010 at 4:33

[GoogleCodeExporter]

In the meantime, Firefox 4b7 is looking very good and gaining speed. I
need a fully functioning Rikaichan. I'm following this issue but
passing on Chrome until one exists.

I'd be happy with an extra keystroke for the text boxes but also miss
the names dictionary with rikaikun.

Original comment by d...@jwebinfo.com on 14 Nov 2010 at 4:45

[GoogleCodeExporter]

In the meantime, Firefox 4b7 is looking very good and gaining speed
and Rikaichan has already added support for it. I'm following this
issue but passing on Chrome until one exists.

I appreciate the efforts of the rikaikun developer. An extra keystroke
for the text box problem wouldn't bother me but I do really miss the
names dictionary.

Original comment by d...@jwebinfo.com on 14 Nov 2010 at 4:52

[GoogleCodeExporter]

One keystroke would be fine.  It's a lot less keystrokes/mouseclicks than 
highlighting, copying, then pasting into a separate translator.

Original comment by clump...@gmail.com on 14 Nov 2010 at 4:57

[GoogleCodeExporter]

To be honest, at this point, I'd actually *prefer* having to press a key as I 
only need it for a few words here and there, and I'd rather not have the pop-up 
constantly appearing. (This is how I use Stardict now.) 

Original comment by jasonbra...@gmail.com on 14 Nov 2010 at 4:53

[GoogleCodeExporter]

+1 for keystroke method for text boxes.

Original comment by generi...@gmail.com on 15 Nov 2010 at 4:12

[GoogleCodeExporter]

Keystroke option hands down beats opening a Firefox window just to use text box 
lookup for a few seconds in rikaichan. +1 for a keystroke workaround :)

Original comment by ricky...@gmail.com on 15 Nov 2010 at 4:38

[GoogleCodeExporter]

Keystroke method would be better than nothing, but having to manually highlight 
the text is messy and a bit of a pain.

Personally the reason I use the textbox method is so I can look up words 
quickly while reading from books. Having to not only type in (or look up) the 
individual kanji, then highlight the word, then press a button gets to the 
point where it's just as quick to use something like jisho.org

It's a shame, because this downside is the only thing that's keeping me from 
ditching Firefox forever.

Original comment by Tsur...@gmail.com on 15 Nov 2010 at 4:45

[GoogleCodeExporter]

> It's a shame, because this downside is the only thing that's keeping me from 
ditching Firefox forever.

Me too! This feature in Rikaichan is the *only* thing keeping me using Firefox 
(version 2, not even 3, as 2 is faster) on my Mac. Please implement this any 
way you can; a keystroke is fine for me as an interim measure.

Original comment by mhaz...@gmail.com on 15 Nov 2010 at 6:07

[GoogleCodeExporter]

> Personally the reason I use the textbox method is so I can look up words 
quickly while reading from books.

I must admit that while I do want Rikaikun to work in textboxes, the simplest 
workaround solution for you here may be to switch to Chrome and just open 
Firefox when you want to read a book.

Original comment by crowb...@gmail.com on 15 Nov 2010 at 8:40

[GoogleCodeExporter]

I agree with Tsuresu. This is the last thing I need done so I can switch 
completely to Chrome from FF. 

Original comment by ben...@gmail.com on 17 Nov 2010 at 6:58

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I always used a textbox and rikaichan for translation.  I discovered that when 
you entertext into a google docs spreadsheet,  rikaikun works in chrome. This 
workaround helped me, hope it helps a few others.

Original comment by puzzleb...@gmail.com on 12 Dec 2010 at 12:20

[GoogleCodeExporter]

I always used a textbox and rikaichan for translation.  I discovered that when 
you entertext into a google docs spreadsheet,  rikaikun works in chrome. This 
workaround helped me, hope it helps a few others.

Original comment by puzzleb...@gmail.com on 12 Dec 2010 at 12:20

[GoogleCodeExporter]

rikaikun would also need to work over dropdowns.

very useful when making choice on a webform.

I'm guessing this can be very well related to this same ticket.

thank you

Original comment by somek...@gmail.com on 18 Feb 2011 at 7:36

[GoogleCodeExporter]

Any updates on when this functionality will become available?

Original comment by mansk3de...@gmail.com on 27 Apr 2011 at 5:51

[GoogleCodeExporter]

This is the one single feature that still keeps me hooked to Firefox. 

Original comment by marco.pe...@gmail.com on 22 Jun 2011 at 10:05

[GoogleCodeExporter]

Yeah, just keep bumping this thread until the solution emerges.  :X

Original comment by Zhouster...@gmail.com on 15 Aug 2011 at 6:06

[GoogleCodeExporter]

another bump!  This feature will be so helpful!

Original comment by cloudl...@gmail.com on 17 Aug 2011 at 4:25

[GoogleCodeExporter]

another bump!  This feature will be so helpful!

Original comment by cloudl...@gmail.com on 17 Aug 2011 at 6:34

[GoogleCodeExporter]

BUMP

Original comment by pmgb...@gmail.com on 18 Aug 2011 at 4:44

[GoogleCodeExporter]

Agreed, I would love this feature.  I'm stuck using PeraperaKun in Firefox 
until this can be addressed.

Original comment by david.de...@gmail.com on 26 Aug 2011 at 4:36

[GoogleCodeExporter]

I'd like this feature as well. 
+1 vote from me.

Also much more on the impossible side, but it'd be nice if we could get it 
working on flash applets >_<

Original comment by Dell19...@gmail.com on 28 Aug 2011 at 12:34

[GoogleCodeExporter]

Just an idea: 

on hover:  
copy the contents of the textbox/textarea, create a div (invisible/position 
-100000 or something) with the same size/font settings/ etc... as the hovered 
textbox/textarea.
get relative mouse position in the textbox/textarea. 
use the mouse position on the created div and get the text on the position and 
use that text to create rikaikun popup

on blur: 
remove the div again

I hope u know what i mean.
I guess it'd be worth a try. If i find the time, i will try it myself.. if that 
happens.. i let u know :D

best regards ^^

Original comment by oO.p...@gmail.com on 4 Sep 2011 at 11:25

[GoogleCodeExporter]

tôi dùng chrome. vấn đề của tôi là. chrome không hiển thị chữ 
nhật bản.tôi phải làm thế nào?

Original comment by giongan...@gmail.com on 2 Jan 2012 at 12:28

[GoogleCodeExporter]

Any news on this feature?

Original comment by kcunning...@gmail.com on 11 Jan 2012 at 11:09

[GoogleCodeExporter]

Grad school is hard, so I haven't made changes in a long while.  If I do this 
will be the first thing I look at, at least some of the intermediate solutions 
are easy enough to implement.

Original comment by melin...@gmail.com on 11 Jan 2012 at 11:36

[GoogleCodeExporter]

Last related commit was r52.  I'll call this fixed for now.

Original comment by melin...@gmail.com on 18 Jan 2012 at 5:35

• Changed state: Fixed

[GoogleCodeExporter]

Awesome. Works well, had to uninstall and install the new one and restart
the browser before getting it working.

Original comment by markburn...@gmail.com on 18 Jan 2012 at 5:46

[GoogleCodeExporter]

This is awesome, but can you make it work inside the Gmail compose email text 
box as well? 

Original comment by marco.pe...@gmail.com on 18 Jan 2012 at 7:13

[GoogleCodeExporter]

been waiting quite a while for this. thank you.

Original comment by iam...@gmail.com on 18 Jan 2012 at 7:20

[GoogleCodeExporter]

marco, did you actually update to 0.8.5?  Gmail compose is working for me and 
at least someone else I asked.

Original comment by melin...@gmail.com on 18 Jan 2012 at 7:56

[GoogleCodeExporter]

doesn't work for me either - i reinstalled rikaikun, set 'highlight text inside 
text boxes' on 'yes' and restarted chrome - still it ain't working in gmail 
compose

Original comment by dark...@gmail.com on 18 Jan 2012 at 8:09