Search existence of text doesn't work properly with Chrome engine

[Yann]

I am replacing firefox by chrome in some old templates and the search existence of text is not working properly.

For example, I am checking the localization on google. When I first go on google with proxy

Then I do a search with US proxy and it shows this:

But when the template checks for presence of text "unavailable" it finds it! I have checked by hand, the text is not displayed on the page.
It finds in a javascript function:

Here the box I am using:

I am using zennoposter 5.41.1.0

Am I missing something?

 

[Yann]

Did anyone else noticed bugs with chrome and text detection ?

 

[VladZen]

Text is checked in code of a page. not only in visible part of a page.

 

[Yann]

Yes that is the issue, it does not behave like firefox. We need to only search for visible text, otherwise any simple regex will do...

 

[VladZen]

Yes that is the issue, it does not behave like firefox. We need to only search for visible text, otherwise any simple regex will do...

I think logic in Chrome is the same as in FireFox. Mayve it makes sense if that script was previoously loaded or not.

 

[VladZen]

Would be nice if you attach the exacmple demonstrating this bug.

 

[morpheus93]

Did anyone else noticed bugs with chrome and text detection ?

Yes, I had and have the same problems with "search for text" in Chrome engine. Already reported this bug when ZP with Chrome was in beta, long time ago but it's still there. Just found your thread here as I'm facing this issues at the moment while giving the chrome engine another try and searched for it in the forum. One workaround that worked for me on some sites is not to search in "Text" but in "Source" (for the case that the text is NOT found but shown on the webpage). But it can then happen that it finds the text in some functions or not hidden html-elements, like you described.
That was one reason why I tried to avoid the Chrome engine, and it's of course not the only reason

 

[morpheus93]

I had a closer look and found that PM is not able to access the DOM and "Page Text" on the sites where there are problems with "Check for text". Attached screenshots. When I click "Examine DOM, source code and page text" in the browser window of PM, the tabs for DOM and page text are empty and only the source is shown!

 

[VladZen]

I had a closer look and found that PM is not able to access the DOM and "Page Text" on the sites where there are problems with "Check for text". Attached screenshots. When I click "Examine DOM, source code and page text" in the browser window of PM, the tabs for DOM and page text are empty and only the source is shown!

Can you tell these websites?
if you disable loading JS on a websites, then DOM and Text will be taken

 

[VladZen]

I am replacing firefox by chrome in some old templates and the search existence of text is not working properly.

For example, I am checking the localization on google. When I first go on google with proxy

Посмотреть вложение 53270

Then I do a search with US proxy and it shows this:
Посмотреть вложение 53272

But when the template checks for presence of text "unavailable" it finds it! I have checked by hand, the text is not displayed on the page.
It finds in a javascript function:
Посмотреть вложение 53273

Here the box I am using:
Посмотреть вложение 53275

I am using zennoposter 5.41.1.0

Am I missing something?

Where exactly do you face it? What webpage on?

 

[Yann]

@VladZen In my first message I gave the example of google.com

 

[VladZen]

@VladZen In my first message I gave the example of google.com

I just didn't see where is this location... at the botton of the page as far as I understand.

 

[Yann]

Here is a simple example of the issue on the zennolab website. With the firefox engine, the script does not find the word "google" and with the chrome engine the script finds it (from the google analytics tag).
This difference of behavior creates lots of issues with previous scripts

 

[Yann]

@VladZen did you have time to try the example I gave you to confirm the issue ?

 

[VladZen]

@VladZen did you have time to try the example I gave you to confirm the issue ?

I've forwarded it to developers. They should fix it in one of next versions.