Mathwiz Posted March 16, 2019 Posted March 16, 2019 Should be; I don't know of an easy way to confirm that though. Anyway, I may have been wrong above: it could be a difference in how Javascript works after all. Some of the changes between the NM that doesn't work and the NM that does seem to be related to Javascript.
Mathwiz Posted March 16, 2019 Posted March 16, 2019 On 3/14/2019 at 2:05 PM, Mathwiz said: Also works in Serpent 52, so probably not JavaScript either. I don't think the PM team made any changes to JavaScript since they forked FF ESR 52. Well, yes and no; according to this somewhat cumbersome JavaScript test page I found, both FF ESR 52 (select "Show obsolete platforms" to see) and Serpent 52 ("current browser") and probably NM 28 too, support the ECMAScript 2017 standard for JavaScript. But Serpent & NM have a couple of fixes that FF ESR 52 doesn't: a couple of changes in the ECMAScript 2017 standard work on Serpent but not FF ESR 52. The features that differ on that page are very minor and probably unrelated to the Instagram video problem. But given what else I found ... On 3/14/2019 at 2:05 PM, Mathwiz said: I've narrowed it down; NM 28 from July 14 shows the same problem as FF ESR 52; NM 28 from July 21 onward works. ... I suspect there's another Javascript bug in FF 52.9.1 that was fixed in Serpent 52/NM 28/MyPal, which causes FF 52's Instagram video bug. If so, it probably isn't fixable on FF 52.9.1 without rebuilding FF from source after applying the fixes. (OT, but this probably also explains FF 52.9.1's problems with Github.com mentioned on another thread.)
heinoganda Posted March 16, 2019 Posted March 16, 2019 (edited) Perhaps the following CSS errors on Instagram can help narrow down the problem with Firefox 52.9.0 / 52.9.1 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:273 Unknown pseudo-class or pseudo-element ‘-webkit-full-screen’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:28 Unknown pseudo-class or pseudo-element ‘-ms-fullscreen’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:121 Unknown pseudo-class or pseudo-element ‘fullscreen’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:164 Error in parsing value for ‘-webkit-text-size-adjust’. Declaration dropped. Br-vL3OldQJ:1:228 Expected media feature name but found ‘-webkit-min-device-pixel-ratio’. Br-vL3OldQJ:1:2541 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:130 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:57 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:1038 Error in parsing value for ‘background-image’. Declaration dropped. Br-vL3OldQJ:1:2364 Unknown property ‘user-select’. Declaration dropped. Br-vL3OldQJ:1:261 Expected media feature name but found ‘min-device-pixel-ratio’. Br-vL3OldQJ:1:12541 Expected media feature name but found ‘-webkit-min-device-pixel-ratio’. Br-vL3OldQJ:1:12570 Unknown property ‘user-select’. Declaration dropped. Br-vL3OldQJ:1:302 Unknown property ‘appearance’. Declaration dropped. Br-vL3OldQJ:1:88 Unknown property ‘appearance’. Declaration dropped. Br-vL3OldQJ:1:62 Unknown property ‘user-select’. Declaration dropped. Br-vL3OldQJ:1:348 Unknown property ‘user-select’. Declaration dropped. Br-vL3OldQJ:1:1363 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:707 Unknown property ‘user-select’. Declaration dropped. Br-vL3OldQJ:1:811 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:267 Expected media feature name but found ‘-webkit-min-device-pixel-ratio’. Br-vL3OldQJ:1:570 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:188 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:521 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:438 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:88 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:494 Expected color but found ‘auto’. Expected color but found ‘-webkit-focus-ring-color’. Expected end of value but found ‘-webkit-focus-ring-color’. Error in parsing value for ‘outline’. Declaration dropped. Br-vL3OldQJ:1:311 Unknown pseudo-class or pseudo-element ‘-webkit-input-placeholder’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:478 Unknown pseudo-class or pseudo-element ‘-ms-input-placeholder’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:535 Unknown pseudo-class or pseudo-element ‘-ms-clear’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:663 Unknown pseudo-class or pseudo-element ‘-webkit-inner-spin-button’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:724 Unknown pseudo-class or pseudo-element ‘-webkit-search-cancel-button’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:850 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:1142 Unknown pseudo-class or pseudo-element ‘-webkit-input-placeholder’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:77 Unknown pseudo-class or pseudo-element ‘-ms-input-placeholder’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:121 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:413 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:56 Unknown pseudo-class or pseudo-element ‘-webkit-input-placeholder’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:171 Unknown pseudo-class or pseudo-element ‘-ms-input-placeholder’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:222 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:1326 Expected media feature name but found ‘min-device-pixel-ratio’. Br-vL3OldQJ:1:770 Expected media feature name but found ‘-webkit-min-device-pixel-ratio’. Br-vL3OldQJ:1:799 Expected media feature name but found ‘min-device-pixel-ratio’. Br-vL3OldQJ:1:2096 Expected media feature name but found ‘-webkit-min-device-pixel-ratio’. Br-vL3OldQJ:1:2125 Expected media feature name but found ‘min-device-pixel-ratio’. Br-vL3OldQJ:1:384 Expected media feature name but found ‘-webkit-min-device-pixel-ratio’. Br-vL3OldQJ:1:413 Expected media feature name but found ‘min-device-pixel-ratio’. Br-vL3OldQJ:1:535 Expected media feature name but found ‘-webkit-min-device-pixel-ratio’. Br-vL3OldQJ:1:564 Expected media feature name but found ‘min-device-pixel-ratio’. Br-vL3OldQJ:1:866 Expected media feature name but found ‘-webkit-min-device-pixel-ratio’. Br-vL3OldQJ:1:895 Expected media feature name but found ‘min-device-pixel-ratio’. Br-vL3OldQJ:1:12880 Expected media feature name but found ‘-webkit-min-device-pixel-ratio’. Br-vL3OldQJ:1:12909 Expected media feature name but found ‘min-device-pixel-ratio’. Br-vL3OldQJ:1:279 Expected media feature name but found ‘-webkit-min-device-pixel-ratio’. Br-vL3OldQJ:1:308 Unknown property ‘backdrop-filter’. Declaration dropped. Br-vL3OldQJ:1:161 Unknown property ‘appearance’. Declaration dropped. Br-vL3OldQJ:1:388 Unknown property ‘user-select’. Declaration dropped. Br-vL3OldQJ:1:738 Unknown property ‘backdrop-filter’. Declaration dropped. Br-vL3OldQJ:1:443 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:511 Error in parsing value for ‘background-image’. Declaration dropped. Br-vL3OldQJ:1:489 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:461 Unknown property ‘appearance’. Declaration dropped. Br-vL3OldQJ:1:153 Unknown property ‘user-select’. Declaration dropped. Br-vL3OldQJ:1:460 Expected media feature name but found ‘min-device-pixel-ratio’. Br-vL3OldQJ:1:437 Expected media feature name but found ‘-webkit-min-device-pixel-ratio’. Br-vL3OldQJ:1:466 Unknown pseudo-class or pseudo-element ‘-webkit-media-controls-start-playback-button’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:126 Unknown property ‘overflow-anchor’. Declaration dropped. Br-vL3OldQJ:1:124 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:761 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:963 Unknown property ‘user-select’. Declaration dropped. Br-vL3OldQJ:1:2290 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:397 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:1442 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:2133 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:2902 Expected media feature name but found ‘-webkit-min-device-pixel-ratio’. Br-vL3OldQJ:1:222 Unknown pseudo-class or pseudo-element ‘-webkit-input-placeholder’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:864 Unknown pseudo-class or pseudo-element ‘-ms-input-placeholder’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:948 Unknown pseudo-class or pseudo-element ‘-webkit-input-placeholder’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:54 Unknown pseudo-class or pseudo-element ‘-ms-input-placeholder’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:139 Unknown pseudo-class or pseudo-element ‘-ms-clear’. Ruleset ignored due to bad selector. Br-vL3OldQJ:1:323 Error in parsing value for ‘display’. Declaration dropped. Br-vL3OldQJ:1:392 Error in parsing value for ‘background’. Declaration dropped. Br-vL3OldQJ:2:2320 Error in parsing value for ‘background’. Declaration dropped. Br-vL3OldQJ:2:2946 A test with Google Chrome 44 was positive. Edited March 16, 2019 by heinoganda
wyxchari Posted March 17, 2019 Posted March 17, 2019 It's about time to switch to Mypal. I use it since last summer and it is updated monthly. I confirm that Instagram videos work perfectly with Mypal.
Mathwiz Posted March 17, 2019 Posted March 17, 2019 Mypal, NM, and Serpent are all confirmed working with Instagram videos (from 21 July 2018 forward). For those on FF 52.9, Serpent is probably the easiest upgrade since it's most similar to FF (same UI and supports the same add-ons & plug-ins). But Mypal and NM are fine too. All three are updated regularly.
sdfox7 Posted March 18, 2019 Posted March 18, 2019 On 3/13/2019 at 7:38 PM, Dave-H said: Yes, my normal installation of Google Chrome 49 (the last that works on XP of course) displays the Instagram videos fine, as it always did! Even more strangely, if I look at the Instagram "Page Info" on the right click in Firefox 52, on the media tab the videos are still listed there, and if I click on them they appear in the preview pane below, and can even be played there. They just no longer appear on the actual Instagram pages! This is very strange indeed, as they obviously aren't actually blocked, they are just not displaying any more on the pages as they should do. I can confirm the videos also load for me on Chrome 49 and Windows XP. For what it's worth, I can't think of a single website I use (banking, etc) that has blocked me in Chrome 49, even though it's three years old at this point. 1
caliber Posted March 18, 2019 Posted March 18, 2019 On 3/13/2019 at 2:15 PM, Mathwiz said: Have you tried setting general.useragent.override to "Mozilla/5.0 (Windows NT 6.1; rv:60.9) Gecko/20100101 Firefox/60.9"? I have tried this but google images site gets back to the old and ugly version. how is that possible ?
caliber Posted March 18, 2019 Posted March 18, 2019 13 hours ago, Mathwiz said: For those on FF 52.9, Serpent is probably the easiest upgrade since it's most similar to FF (same UI and supports the same add-ons & plug-ins). I'm not sure about this fact otherwise Basilisk 55 would had become my default browser for a long time now.
Mathwiz Posted March 18, 2019 Posted March 18, 2019 (edited) Basilisk Serpent 55 isn't as compatible with add-ons/plug-ins as Serpent 52. It was forked from a later FF version where most NPAPI plug-ins (except Flash) were disabled. Edit: That turned out to be totally wrong; sorry. Actually Serpent 55 does support NPAPI plug-ins, and at least a few add-ons that Serpent 52 doesn't support. Edited July 23, 2019 by Mathwiz
Guest Posted March 18, 2019 Posted March 18, 2019 (edited) General spoofing is not necessary. Set a specific rule for the problematic website. As I wrote elsewhere the website below is not accessible with Windows XP: https://app.agyo.io/ I entered a specific string for that website in NM28. If anyone is interested I can write the string in this 3D. With FF52ESR it is possible to do the same Edited March 18, 2019 by Sampei.Nihira
Josept Posted March 19, 2019 Posted March 19, 2019 On 3/18/2019 at 1:24 PM, Sampei.Nihira said: General spoofing is not necessary. Set a specific rule for the problematic website. As I wrote elsewhere the website below is not accessible with Windows XP: https://app.agyo.io/ I entered a specific string for that website in NM28. If anyone is interested I can write the string in this 3D. With FF52ESR it is possible to do the same spoofing not work for this problem
Dave-H Posted March 19, 2019 Author Posted March 19, 2019 I can vouch for that, and believe me I've tried! It worked to get Facebook videos back to HTML5 after they dropped back to Flash a while ago, but that's not the same problem as now with Instagram. The fact that the videos still appear in the Page Info dialogue, and will play there, but won't appear in the pages where they should be, would seem likely to be caused by a scripting change Instagram made a few days ago for some reason, which Firefox 52 ESR either can't cope with or doesn't understand at all. The fact that placeholders don't even appear where the videos should be would bear that out. I've seen several posts where there is both a video and a still which can be sideways scrolled between. In that case the still appears correctly, but the video just appears as a white box. In my experience this is the first major compatibility problem to surface after FF 52 ESR came out of support, and I don't think it will easily be fixed I'm afraid.
Mathwiz Posted March 19, 2019 Posted March 19, 2019 Spoofing doesn't work for Instagram videos on FF 52.9; that is correct. I suggested that about 20 posts ago and it was quickly proven not to work. However I think @Sampei.Nihira was addressing @caliber's comment about a global spoof (general.useragent.override) causing Google Images to look "ugly." They kind of drifted OT a bit. (I mean, it's OK. It happens.) Context is everything. As I tried to point out in the Adobe Primetime thread, the only way you're likely to get FF 52.9 working again is to try to apply to FF 52.9 source the patches that the PM team applied to Palemoon/Basilisk on 21 July 2018 (and which @roytam1 applied to NM/Serpent), which fixed the problem on those browsers; then recompile FF 52.9 from the patched source. You might need to apply a lot of earlier patches as well, since it's likely that some of the July 21 patches depend on earlier ones. Personally, I don't think it's worth the trouble. Much easier to just switch to one of the browsers known to work.
Guest Posted March 20, 2019 Posted March 20, 2019 (edited) @Mathwiz _________________________________________ I usually use NM28 with XP. But having multiple browsers installed is always advisable. For example with NM28 I cannot access the advanced configuration of some routers. For the model below: https://www.amazon.it/TP-Link-TL-MR6400-Monitoraggio-Traffico-Alternativa/dp/B017IGEPWW I have to access only with I.E.8 from my pc with XP. Sorry for the OT, Edited March 20, 2019 by Sampei.Nihira
Mathwiz Posted March 21, 2019 Posted March 21, 2019 You know, I never tried Instagram with IE8. Seems like a very long shot, with all that fancy JavaScript that Instagram uses, but you never know.... On the off-chance it works, all you'd need is the IE Tab add-on for Firefox.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now