Translate often misdetects a language for base64-encoded data like PGP keys
Reported by
anowlcal...@gmail.com,
Nov 15
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3602.2 Safari/537.36 Steps to reproduce the problem: 1. Visit a webpage that consists of a PGP key, e.g. https://meta.sr.ht/privacy/pubkey 2. Observe that the "Translate this page?" bubble appears – in this case, offering to translate the key from Maltese. 3. Pressing the "Translate" button doesn't do anything useful. What is the expected behavior? Chrome shouldn't offer to translate pages that aren't in a human-readable language. Offering to turn ASCII-armoured PGP keys into something human-readable automatically would be awesome, but I suspect that's not in scope ;) What went wrong? Chrome frequently misdetects the language of pages with no (or little) human-readable text. Did this work before? N/A Chrome version: 72.0.3602.2 Channel: n/a OS Version: Ubuntu 18.04 Flash Version: I vaguely remember that at one point there was an option for "this page isn't in $language" – what happened to that?
,
Nov 16
,
Nov 19
Able to reproduce the issue on Win-10, mac 10.13.6 and Ubuntu 14.04 using chrome reported version #72.0.3602.2. This is a non-regression issue as it is observed from M60 old builds. Hence, marking it as untriaged to get more inputs from dev team. Thanks...!! |
|||
►
Sign in to add a comment |
|||
Comment 1 by anowlcal...@gmail.com
, Nov 151.9 KB
1.9 KB View Download