re

[Astara]

RP: 5.28.1
Browser is palemoon, but this isn't a browser specific issue, but an issue
with 'translate.google.com'.

It's not easy to use RP w/that website. Only thing I have found that worked was disabling RP.

Problem is that when translating a remote page (I was using "https://www.ir2.vobilegroup.com/" but
any page needing translating should cause the same prob if it has resources to load from that remote page).

Google creates a temporary domainname (not really, but it acts like one on the HTTP/s level.

What ends up happening is their translated page comes from a subdomain under
'translate.goog' (goog as TLD). They prepend the real source, modified, to that domainname, so
for the website I was using, the requests come from:
"https://www-ir2-vobilegroup-com.translate.goog/"
I think they append page-specific elements to that.

Problem here is for RP to work, it needs some sort of wildcard support, like
*.translate.goog

I tried permitting all from translate.goog, (as well as translate.google.com). Even though RP
has special permit code to find a dom under 'www.example.com' as 'example.com', prepending
a whole made-up subdomain, seems a bit of a stretch.

I think I found the aboe out by using the RP-request log, and doing enough page replots and going through
the error message till I could get the bottom line displayed when the popup was still up and blocking.

Hard to see the last. line in the rqlog as window needed scrolling down, but focus of error-popup was preventing scrolling.
As soon as one hits ok in error-popup, more rq's come in and hide the original bottom line. Maybe detaching the log and stretching it out might have done the trick...not sure.

Comments? Questions? Clue-sticks? another white-overcoat for my trip to lunybin? :-)

Astara