oupula / ichm

Automatically exported from code.google.com/p/ichm
0 stars 0 forks source link

'Find in page' problem #94

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Platform:
Mac OS X 10.5.8 Leopard.

What steps will reproduce the problem?
1. Open any chm document.
2. Press command+F (or click find from view menu).
3. Type anything you see in the shown page.

What is the expected output? What do you see instead?
The program doesn't highlight anything in the shown page, even if you enter a 
word you see in 
the page.

What version of the product are you using? On what operating system?
iChm 1.4.1 (the same problem was in the previous version 1.4.0 before I 
upgrade).

Please provide any additional information below.
I tried both versions (1.4 and 1.4.1) on my MacBook Pro 15.4 under 10.5.8 OS, 
and it worked 
without any issues. The problem appears just in my mother MacBook Pro 13.3 
under the same 
version of OS.
There is no document specific issue here, because I tried so many document that 
all worked 
under my laptop.

Original issue reported on code.google.com by mamoun.d...@gmail.com on 8 Sep 2009 at 1:36

GoogleCodeExporter commented 9 years ago
Please check if you disabled javascript in Safari.

Original comment by iamawal...@gmail.com on 10 Sep 2009 at 5:45

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
It's already enabled. any other suggestion?

Original comment by mamoun.d...@gmail.com on 10 Sep 2009 at 7:23

GoogleCodeExporter commented 9 years ago
try to update your safari?

Original comment by iamawal...@gmail.com on 11 Sep 2009 at 12:37

GoogleCodeExporter commented 9 years ago
It's up-to-date.

By the way, Would it be useful to take  a 'sample' of what iChm executing at 
finding moment, through Activity 
Monitor utility?

Original comment by mamoun.d...@gmail.com on 12 Sep 2009 at 6:48

GoogleCodeExporter commented 9 years ago
it might not be very useful. The search is implemented by javascript which is 
totally depends on webkit (core of 
safari).

Maybe you can try to use different text encoding or language settings.

Original comment by iamawal...@gmail.com on 12 Sep 2009 at 12:24