serbeer wrote: ↑Fri May 03, 2019 7:44 pm
chivracq,
not related to the original question, but what is this Multi-Login Authentication "that became a bit of a hassle from FF51 also, hum, and maybe from FF50 already " you mentioned in your response? Search of the forum resulted in no hits.
I am planning to upgrade my setup to the latest FF that iMacros version 8.9.7 will work with, which, per my research appears to be 56.0.2 (I realize I will have to remove image filtering from my scripts, and that should be OK), but wanted to make sure I am not missing any other implications, even though this is unlikely to be an issue since I am currently on FF v52 anyway, which is beyond FF50/51 you mentioned.
Thanks!
Multi-Login:
OK, I remember after updating FF50 to FF51 that "stg" had changed in FF51 (was "vaguely" documented like always in the FF Change-Log), and I had to change/tweak/toggle 2 'about:config' Settings in FF to get some "OK-Acceptable" Config, took me less than 5min then...
Mini-search now, in my 'about:config' on "multi"/"logon"/"login"/"auth"/"log" for my FF55 and hum, I cannot locate which Settings I did modify at that time... So, hum-hum...!? I'm still at FF55, so FF didn't update (and is complaining often enough that my Version is "critically unsafe", ah-ah...!), so hum..., I don't know..., should be easy to find I would think, from the Change-Log for FF50 or FF51...
But yep indeed, if you were already at FF52, you were already "after" that Multi-Login Authentication Change and if you didn't notice anything when you had previously updated to FF52 (ESR I guess), then I guess you are already "immune"...
Hum-hum, was related to 'http'/'https' I think, and only for 'http'...
OK, YES, found them, "http" and "https" didn't find atg relevant, but "secure" did, youpidoo...!
=> OK, those are the 2 'about:config' Settings I had set to "false" after FF50 or FF51 around that time:
- security.insecure_password.ui.enabled
- security.insecure_field_warning.contextual.enabled
And I see I have another related Setting:
- security.insecure_field_warning.ignore_local_ip_address
=> but left at its Default (= "true") value...
My FF FCI is iMacros for FF v8.9.7 + FF v55.0.3 + Win10_x64.
I am planning to upgrade my setup to the latest FF that iMacros version 8.9.7 will work with, which, per my research appears to be 56.0.2
Not a "good" Idea is my "Advice"...
Yep, v8.9.7 still works on FF56, but hum..., had many Reports (on the Forum) that "many" Things didn't work anymore or correctly in FF56.
My Advice...:
Don't go any further than FF v55.0.3, which is the Version I use myself, and works correctly with v8.9.7 for FF. (apart from the 'FILTER' Command that got broken(*) from FF52 or FF53, I don't remember exactly..., I had quickly updated between 2 or 3 FF Versions in one day at that time as soon as I had found out that 'FILTER=ON' would "freeze" my Scripts for several Minutes..., and I was hoping that the next FF Version would "unbreak" it again...)
And "broken(*)" is only noticeable for "heavy" Pages with 1000++ 'IMG' Elements, most Users won't notice any Difference, I would think, would need to 'profile' iMacros before/after and/or to stopwatch-monitor it (or with '!NOW' at the ms Level) to check... Well, with 1000++ Images, we don't talk about ms (=Milliseconds) anymore, rather 10-Sec Unity, oops...!
A Page that would take 2-3-5 Sec to load with 1000++ Images on FF50 or FF51 with 'FILTER=ON', would then need between 3-5 Min to load on FF52 or FF53 (hum, or maybe FF54...(?)) (with 'FILTER=ON'), against about 45 Sec with 'FILTER=OFF' in both FF Versions..., meaning 'FILTER=ON' has no Use anymore from FF51+ as it actually drastically slows down the Loading Time of heavy Pages...
- (F)CI(M) = (Full) Config Info (Missing): iMacros + Browser + OS (+ all 3 Versions + 'Free'/'PE'/'Trial').
- FCI not mentioned: I don't even read the Qt...! (or only to catch Spam!)
- Script & URL help a lot for more "educated" Help...