parser Reader + Translate compatibility

A user emailed us about an issue. I haven't verified this yet, but I'm logging it here so we can investigate it:

Hi, I have being using Mercury Reader for several years now and find it great. I tried to use it with Google translate chrome extension but would not translate when i used your extension first to remove ads etc. I force installed and pinned the updated Postlight reader extension yesterday to the work Organisation but it will not appear now on my chrome extension. I had prior to force installing removed the older mercury reader. I aslo updated my chrome extension and removed cookies. I dont know if others are exeriencing the same behaviour.

Oct 07 '22 15:10 johnholdun

I'll take a look at this and see if I experience the same behavior.

Oct 20 '22 18:10 danielamuniz367

I'm also experiencing the same behavior as this user when I try to use google translate after using the Postlight Reader extension. It overall seems that this is due to a limitation with Google translate. The iframe content, which is what the parsed content is in, can't be rewritten (as far as I know, but if anyone knows how to do this for this case then that would be awesome).

Here's one of the links that led me to this conclusion

Oct 21 '22 15:10 danielamuniz367