ok since when did windows start keeping shit on the GPU it started on and not move execution across whatever gpu is driving taht display?

Tools | Translate does look to still work in SeaMonkey 2.49.5

though a useragent change (to 2.49.5) does not get things working in SM 2.53.xx

beta page download links are returning 404, seamonkey-project.org/releases/2.53.15b1

does an older 2.53 still work maybe 253.1^0 or so with translate?

Copy step for thew binaries were not doe it seems. They are still in tmp

frg: Ah, 2.53.1 does still work. that uses "60" (but then a UA change did not make any difference in current)

sample URL, uwe-sieber.de/deutsch.html (for a de to en)

works: seamonkey-2.53.11.en-US.win64.installer.exe

broken: seamonkey-2.53.12.en-US.win64.installer.exe

11:

Use of attributesí nodeValue attribute is deprecated. Use value instead.

m=el_main:368:329

12:

SyntaxError: An invalid or illegal string was specified

m=el_main:468

I had no luck toggling UA strings, even setting IE6 led to failure

perhaps I forgot to clear some cache?

I think it was visibly serving a different layout to "IE6", but it still failed with that message

well, in one case, 11, you get a warning, in the other, 12, there is an actual Error, so... ?

oh, I mean luck getting it to actually translate

the code seems to be calling performance.measure if it exists, or am I getting misled by the line and column numbers and the spaghetti

?

therube: that syntaxerror sounds like it happens when the page is initializing a "google translate" instance, setting window.performance=null and then doing window.google.translate.TranslateService(); unbreaks the translator

bug 1444150?

therube: setting dom.enable_performance_navigation_timing to false might work as a workaround too

now I had a... hiccup in google maps, I wonder if it's related to dom.enable_performance_navigation_timing=false, or if it was just a change on google's side

the hiccup itself was unrelated, but setting that to false does give me a slightly different UI, at least in incognito mode

how to "fix" Translate, forum.palemoon.org/viewtopic.php?p=234631#p234631

now, no idea what the Pref is for... but it works.

therube will break other sites. Not recommended

and, it doesn't seem to be working - always, anyhow.

i'm confused at this point, but gotta go now...

frg_Away: I wonder if what's needed here for translate is bug 1444150, or will that break things too? or not easy to apply?

therube: I think it's toggling certain kinds of measurements in the performance measurement code

therube: it's not hiding window.performance (although setting it to null allows google translate to initialize, because it will skip the code throwing the SyntaxError)

it does work here, welt.de, but not on uwe's page that i posted earlier

njsg thought it was in but it is not. Exported it and will see if it applies easy.

therube: there's «performance.getEntriesByType("navigation")» in the google translate code, so I wonder if that's what makes the preference "unbreak" google translate

njsg applies clean

15 minutes to get it in :)

put it in. Will be in the next pre build

therube: it's a bit... challenging to follow this code, but it operates on the first entry coming from that .getEntriesByType() call, and that will be empty if the page is loaded after the setting has been set to false. Given that the SyntaxError code is doing performance measurements, it's possible that that code runs on the result of getEntriesByType.

oh, after looking at the code in the bug: privacy.resistFingerprinting=true avoids the SyntaxError too, no idea if it causes issues elsewhere

njsg it broke other stuff including the reported version I think. You can't win with google and idiotic development apis in production code.

gitlab 2.53 updated. reshuffle for 2.53.15 patches and 2 py3 backports. No need to stop current builds. Just housekeeping.

Real Men Test In Production™

frg_Away: have you seen this: forums.mozillazine.org/viewtopic.php?p=14945555#p14945555

hardys yes. Mailed ewong. Have no rights. Should be fixed by tomorrow. If not I will backout the website changes.

no problem for me,I always the latest pre beta

always USE the latest pre beta :)

Bug 1444150 does not help with the traslate page problem.

^translate