01:02:48 <a-865> frg_Away: where is this 2.53.10 for fedora with iso dates patch to be found?
02:13:35 <Guest1566> Evening all... I Am having a challenge with logging into NYTimes.com as I cannot get beyond the "Prove that you are human" screen before it gets stuck. suggestions
02:14:35 <Guest1566> SM 2.53.10 version
02:14:43 <tomman> Guest1566: are you running adblockers or something?
02:15:11 <Guest1566> Only within SM I think but no addons
02:15:49 <tomman> OK, so basically a stock install
02:16:12 <Guest1566> Yes, that is correct.
02:16:19 <tomman> Hit F12, try to login, and check the console for errors
02:16:50 <tomman> what do they use for captcha, ReCaptcha or something else?
02:17:22 <Guest1566> recaptcha is used
02:18:42 <tomman> ReCaptcha still works fine with SM last time I got inflicted with one (which was... last week?), so could be something else...
02:19:02 <tomman> well, open the developer tools with F12 and let's check for any possible JavaScript and network errors
02:19:22 <Guest1566> Is that shift f12 or ctrl f12?
02:19:28 <tomman> just F12
02:19:42 <tomman> and then select the Console tab
02:19:53 <tomman> then try to login
02:20:12 <Guest1566> Fn f12 worked, I think
02:20:29 <tomman> hopefully is not Yet Another Bleeding-Edge JavaScript place
02:20:35 <tomman> oh, a laptop then
02:20:55 <Guest1566> Sorry, yet laptop, Lenovo T460p
02:22:01 <Guest1566> tracking protection is enabled ... is the load failure message.
02:22:28 <Guest1566> google tagservice
02:22:48 <tomman> no SyntaxErrors or anything like that?
02:23:05 <tomman> Try to login until you get stuck, then watch the console
02:28:07 <Guest1566> Now it just loops back to sign in... no change in console messages... I will scroll through them now to be sure.
02:28:31 <Guest1566> The resource at “https://www.googletagservices.com/tag/js/gpt.js” was blocked because tracking protection is enabled.
02:28:33 <Guest1566> [Learn More]
02:28:34 <Guest1566> 12949-vegan-quick-biscuits
02:28:36 <Guest1566> Loading failed for the <script> with source “https://www.googletagservices.com/tag/js/gpt.js”.
02:28:37 <Guest1566> 12949-vegan-quick-biscuits:1
02:28:39 <Guest1566> The resource at “https://www.google-analytics.com/analytics.js” was blocked because tracking protection is enabled.
02:28:40 <Guest1566> [Learn More]
02:28:42 <Guest1566> 12949-vegan-quick-biscuits
02:28:43 <Guest1566> The resource at “https://5290727.fls.doubleclick.net/activityi;src=5290727;type=allpa0;cat=nyti-0;ord=1;num=1748847656283;gtm=2wgba1;auiddc=1381185018.1637372763;u17=https%3A%2F%2Fcooking.nytimes.com%2Frecipes%2F12949-vegan-quick-biscuits;~oref=https%3A%2F%2Fcooking.nytimes.com%2Frecipes%2F12949-vegan-quick-biscuits?” was blocked because tracking protection is enabled.
02:28:45 <Guest1566> [Learn More]
02:28:46 <Guest1566> 12949-vegan-quick-biscuits
02:28:48 <Guest1566> The resource at “https://ad.doubleclick.net/activity;src=5290727;type=allpa0;cat=cooki0;ord=6446319882157;gtm=2wgba1;auiddc=1381185018.1637372763?” was blocked because tracking protection is enabled.
02:28:49 <Guest1566> [Learn More]
02:28:51 <Guest1566> 12949-vegan-quick-biscuits
02:28:52 <Guest1566> The resource at “https://insight.adsrvr.org/track/pxl/?adv=bomn82o&ct=0:4dq5m7t&fmt=3&ttl=43200&gtmcb=1826788752” was blocked because tracking protection is enabled.
02:28:54 <Guest1566> [Learn More]
02:28:55 <Guest1566> 12949-vegan-quick-biscuits
02:28:57 <Guest1566> The resource at “https://static.chartbeat.com/js/chartbeat.js” was blocked because tracking protection is enabled.
02:28:58 <Guest1566> [Learn More]
02:29:00 <Guest1566> 12949-vegan-quick-biscuits
02:29:02 <Guest1566> Loading failed for the <script> with source “https://www.google-analytics.com/analytics.js”.
02:29:03 <Guest1566> 12949-vegan-quick-biscuits:1
02:29:05 <Guest1566> Loading failed for the <script> with source “https://static.chartbeat.com/js/chartbeat.js”.
02:29:06 <Guest1566> 12949-vegan-quick-biscuits:1
02:29:08 <Guest1566> Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://abra.api.nytimes.com/v12/allocations.json?integration=cooking-web-prd&tests=COOK_TP2_regiwallsubscribebutton%2CCOOK_TP5_ProductSurvey%2CCOOK_TP7_BoomerangHoldout%2CCOOK_TP19_NewsletterExperiment%2CCOOK_TP20_SaveReminderExperiment%2CCOOK_TP21_RecircExpansionExperiment%2CCOOK_TP22_UserToolsInNavExpe
02:29:09 <Guest1566> riment%2CCOOK_TP26_NoFreeTrial%2CCOOK_WEB_TP27_LpBypass%2C0_control&agent_id=95lG7fgVFWX8ZNr9_XtPPh. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).
02:29:10 <tomman> These are normal, pure ad BS
02:29:11 <Guest1566> Content Security Policy: Ignoring ‘x-frame-options’ because of ‘frame-ancestors’ directive.
02:29:12 <Guest1566> Loading failed for the <script> with source “https://s.go-mpulse.net/boomerang/ATH8A-MAMN8-XPXCH-N5KAX-8D239”.
02:29:14 <Guest1566> enter-email:1
02:29:15 <Guest1566> Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
02:29:17 <Guest1566> Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
02:29:18 <Guest1566> Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
02:29:20 <Guest1566> Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
02:29:21 <Guest1566> Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
02:29:23 <Guest1566> Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
02:29:24 <Guest1566> Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
02:29:26 <Guest1566> Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
02:29:27 <Guest1566> Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
02:29:29 <Guest1566> Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
02:29:30 <Guest1566> Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
02:29:32 <Guest1566> Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
02:29:33 <Guest1566> XML Parsing Error: not well-formed
02:29:35 <Guest1566> Location: https://geo.captcha-delivery.com/captcha/check?cid=USkPd-gP-Xu8DUThmDUZz1PPIl5l83culxFr38KnFnFPTv2Mn572acNlr6p8u33-BfIbjNb_qzxk_pehXUIC_G_V8Lj7tkkghlFd2CmlQ0&icid=AHrlqAAAAAMATxyw75v9kc8AYm4zyA%3D%3D&ccid=null&g-recaptcha-response=03AGdBq26Y-QB8WryTvYLfMm-bDQkOMyZIq2cSa6VNu2vMHVx-oBd8qdhAcS1rYT3hMilYQ7qHx1JC-DybvaIyLO8hb6vb4aZpXfJIPiY4TU8CnCJQegXIYpmKHiNMUci84WiSBmvQ_URIuCDYv3pSWPlvPOjgV
02:29:36 <Guest1566> mq33VgKd2sYG-IeNz0pzwkevo5aX7_rEWmLiMMFIFM3mAa5Z85L2IUc1IhXcdL4wuY2CJBxtQBB75kZzciDyfgUqvA0A8hnAogXcPutUbOpfqzzcBh94nMKmyaOlQDXv6qint75YaGiBGEgSyB_ZPolGY91E-VYg1e3Fc4IEH1LPLME_zlEeJOJCR45kbpgSaaqZtmZGrm5m4QbwtgfMYmCdC7BAdZ04avbW4dbwcNhfHyVnG6tq_QTGRSYlfRVMQADMurztB8yDxseese5RHfEcCd_ArOhTBRX_Mx1wnwY7uH2yuur4NTpeCXayIAi5tG8Dzh4kNNgSlGXr-RU9zzvqoEIcgwWCSP0WXmrst4YIwJns1OPXEoN0mAURVa4ZSNI5PdKb0zJHx4gv
02:29:38 <Guest1566> -q6mDrRVDz5z9H2zvnR_18_yd4pOHaIvXNkWEJM_QkP98b9jaEcmxwS56IZIbJg0xQq1rBI_PLR4KWv4_jNeQnK5j5V9Fl6sCNLxGVX64dSdkpPZqrDau4Byx-g-MAjc7D-WCn_ivg4LTzvg0W35UcJxzBiZrjzh60Jgse78EjSJJLdYwzKUXqN9aGx1zCOwQM7Z0DQgO4wNMMeeIY3ZHkSBo4Zqm5Z8sz9mMgnTeYs3DmLBfl5P3JQqZ0vr4lZKHcJvOa9UFcPAeHXXvkGgjSGSo4Eci_583nXPop8Mfik4wzQwDGBPmCIh6SNMnvgNwjxWjPLyf3xAfmJNCAW3GBfkwgYod187DFifY8T83f6JbZEFRzNVtM05S9vRNdIasd3qnfam_IXQeLGv
02:29:39 <Guest1566> miMvOj-c4KfY4j4bLCZBQWvIjR_Q2w8TJk5WtZb4qMfoKJ3nU9AMpx6LlA_NUMyO2zg_MDnaESNU_-XZXHP4KM6bb-dsLO7mV0qgBl5-Sl-ijNieM50DCWK0S3vKXAhkjBZJutVtdfRFX67W2uFELqwEPnB6kWO7vcP9722aGksYYBxXwJynMFYxSS4VL8n152omBBlicY8MNgXF8wZILPtreNyHdpiBBLnVJN1NIWWMRKK4soHSmunXZ1ynTVxrzyD4Ad0X_MTLQnLlOtrqd1PT9xSXacSQPBi50uaT3mMvsw7-v8_UK5ByqX2GrdOBw3I5PvrvL1dvXrVenxxrVGN3H2cTBfLXf_w2qKMUGU9KvTCyzG5-bU8fYbdi6O8th2zWXskYCVn8x3JM
02:29:41 <Guest1566> zxaRbZW4jGBOrz0k78AddxqDVZVh2UB5AOODT_n2jWMjAbZc0Y3aGNk96Od3C--Jzf74o2dKOgwN-shRaGSfx10rkgvyTT6Z9XAL1S8ofyMBL0focr5uglTRe0Ca1iB3e7nMPJyj7KriSr4Gv2rjLN7DyIhxq685V4CtA_ISNY&hash=5F35800FA2155BC5833193CFCB9E4D&ua=Mozilla%2F5.0%20(Windows%20NT%2010.0%3B%20WOW64%3B%20rv%3A68.0)%20Gecko%2F20100101%20Firefox%2F68.0%20SeaMonkey%2F2.53.10&referer=https%3A%2F%2Fmyaccount.nytimes.com%2Fauth%2Fiframe%2Fenter-
02:29:42 <Guest1566> email%3Fresponse_type%3Dcookie%26client_id%3Dcooking%26redirect_uri%3Dhttps%253A%252F%252Fcooking.nytimes.com%252Frecipes%252F12949-vegan-quick-biscuits%26display%3Ddefault%26application%3DCooking%26preloaded%3Dfalse&parent_url=https%3A%2F%2Fmyaccount.nytimes.com%2Fauth%2Fiframe%2Fenter-email%3Fresponse_type%3Dcookie%26client_id%3Dcooking%26redirect_uri%3Dhttps%253A%252F%252Fcooking.nytimes.com%25
02:29:44 <Guest1566> 2Frecipes%252F12949-vegan-quick-biscuits%26display%3Ddefault%26application%3DCooking%26preloaded%3Dfalse&x-forwarded-for=&captchaChallenge=13090466&s=9648
02:29:45 <Guest1566> Line Number 1, Column 1:
02:29:46 <tomman> ooooh, an XML error!
02:29:47 <Guest1566> check:1:1
02:29:48 <Guest1566> Content Security Policy: Ignoring ‘x-frame-options’ because of ‘frame-ancestors’ directive.
02:29:50 <Guest1566> Loading failed for the <script> with source “https://s.go-mpulse.net/boomerang/ATH8A-MAMN8-XPXCH-N5KAX-8D239”.
02:29:51 <tomman> interesting
02:29:51 <Guest1566> enter-email:1
02:29:53 <Guest1566> Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
02:29:54 <Guest1566> Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
02:29:56 <Guest1566> Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
02:29:57 <Guest1566> Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
02:29:59 <Guest1566> Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
02:30:00 <Guest1566> Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
02:30:02 <Guest1566> Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
02:30:03 <Guest1566> Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
02:30:05 <Guest1566> Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
02:30:07 <Guest1566> Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
02:30:08 <Guest1566> Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
02:30:10 <Guest1566> Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
02:30:45 <tomman> Aside of the tracker blocking and Content Security Policy warnings, the only noteworthy error would be that "XML Parsing Error: not well-formed"
02:31:08 <tomman> from that insanely long URL at  https://geo.captcha-delivery.com/
02:31:12 <Guest1566> Is there a way to rectify XML Error?
02:31:50 <tomman> that error happens because the server is sending corrupt/malformed XML to the browser
02:32:46 <Guest1566> Yet, I have no issues using Chrome and presume they are sending the same XML to that browser, correct?
02:33:19 <tomman> could be yet another case of botched user agent sniffing on their side
02:33:50 <tomman> WTF
02:33:55 <tomman> pasted your URL here
02:34:03 <tomman> ...and the server sends JSON, not XML!
02:35:00 <Guest1566> Which means no work around, correct?
02:35:06 <tomman> something on their scripts are expecting XML, or maybe SeaMonkey is assuming some document type wrongly
02:35:13 <Guest1566> Using SM that is...
02:35:45 <tomman> it needs more testing, indeed
02:35:55 <tomman> that's definitely a weird error
02:37:04 <tomman> https://stackoverflow.com/questions/51347771/got-xml-parsing-error-not-well-formed-when-i-expect-json
02:37:16 <Guest1566> This would be the same when trying to access Chase.com and FB, too? Well, thank you very much for your insight on this. Much appreciated.
02:37:26 <tomman> the server is definitely not sending the correct content type for their reply
02:37:34 <tomman> which is causing SM to interpret it as XML somehow
02:37:55 <tomman> Guest1566: worth testing that on Firefox, just to rule out a possible Chromeism
02:39:27 <Guest1566> Okay, there is a solution, possibly at the link you provided. I can do the change in the console and it will not cause other login issues on other websites, possibly?
02:39:31 <tomman> In fact, the server is not even setting a content type at all for that reply (it's JSON, so it should be set to application/json...)
02:39:39 <tomman> nope, that's a SERVER-SIDE problem
02:39:45 <tomman> why it's triggering SM? Dunno
02:40:09 <Guest1566> Okay, nothing I can do at the moment.
02:40:49 <tomman> NYTimes.com don't have free accounts, right?
02:41:04 <Guest1566> Yes, they are limited in scope.
02:42:10 <tomman> OK, as long as someone can create a test throwaway account for testing, would be nice for having a reproducible testcase.... and eventually having a fix
02:42:39 <tomman> it's curious that this time it's not yet another unimplemented JavaScript feature (I hope)
02:43:38 <Guest1566> I need to create a bug report for this error, correct?
02:44:01 <tomman> would be nice
02:44:24 <Guest1566> No, not to be nice but to be helpful... and helped.
02:44:40 <Guest1566> What info do you think needs to be included in the report?
02:45:42 <tomman> At the very least a sample URL, and the errors/warnings you're seeing at the console
02:46:15 <tomman> Hmmm, curious
02:46:30 <tomman> I just created a free account with a throwaway email
02:46:33 <tomman> set a password
02:46:37 <tomman> and logged in fine
02:46:43 <tomman> no captcha at all
02:47:12 <tomman> maybe I got lucky and didn't got punished with a captcha
02:47:20 <Guest1566> I will give you my login info to see if you can login..
02:50:14 <tomman> OK, managed to login just fine
02:50:29 <tomman> didn't got a captcha
02:52:29 <tomman> Without a captcha, this will be hard to debug...
02:52:35 <tomman> could be IP address related?
02:52:41 <tomman> I'm not even in the USA!
02:53:23 <Guest1566> Hmmm, meaning that it does not like where I Am logging in from, correct?
02:53:32 <tomman> maybe, maybe not
02:53:51 <tomman> but then, you say your logon works fine from Chrome on the very same computer, right?
02:53:57 <tomman> Try with a clean profile
02:54:24 <Guest1566> Yes, that is correct.
02:54:45 <Guest1566> You mean a SM clean profile, right?
02:54:58 <tomman> you can rule out profile corruption or addon/extension interference by testing with a clean profile
02:55:01 <tomman> yeah
02:55:51 <tomman> In any case, ReCaptcha is Google, and when Google is involved, expect crazy
02:55:55 <Guest1566> Okay, great.... thank you for your insight and recommendations
15:39:10 <JamminUnit> FYI, Gentoo has just lost his seamonkey package maintainer: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=59ceead78eea8b29a4754267c5c42fb8be9fe707
15:44:47 <tomman> "due to unreasonable qa demands"
15:44:51 <tomman> ...what?
15:45:15 <tomman> not familiar with Gentoo at all, what's the backstory there?
15:49:47 <frg_Away> tomman He can be fould here accasionally and might answer.
15:56:48 <WG9s> This sounds like the I am only going to get the code to build and it is up to the QA pople to run any tests onit atitude
16:05:52 <frg_Away> WG9s probably more of you need to use package x and y and z and drop Python 2 and and and. But all speculation. Automatic tests are broken for ages so no qa from there :)
16:05:54 <WG9s> I am not trying to take sides here just you shuld not either.  it seems to be a common occurance lately that people supposedly responsible for supporting packages they no longer use pesonally want to keep being the responsible person becuase that gives them status but unwilling to actully support the package and just make sure it builds but unwilling to make sure it passes any tests or be...
16:05:55 <WG9s> ...reponsive to user bug submissions.
16:06:24 <WG9s> not sure if that is what ahppened here or not but don;t be too quick to jump to one side or the other withoug getting all the facts.
18:02:34 <buc> a-865: Sorry, Fedora is still on 2.53.8.1, as there are still no noticeable new functionality in the recent ones, and at the same time there are a number of hidden regressions that I do not have time to fix yet.
18:06:09 <buc> a-865: The patch you are interesned in is here:  https://src.fedoraproject.org/rpms/seamonkey/blob/rawhide/f/seamonkey-2.53.8.1-dateformat.patch (against 2.53.8.1 code, but not included since was created after that release). Feel free to use if you can perform own build.
20:38:00 <frg_Away> buc what regressions do you think are in 2.53.10 ?
20:46:36 <WG9s_> frg_Away: buc just posted that and then left
20:50:55 <buc> frg: It seems that after backporting changes related to threads/events/priority (since 2.53.9), "show slow script" dialog no more appears in a case of a heavy loaded scripts. And someone else complained (in the news channel) about non-worked buttons on websites.
20:52:34 <buc> An example is the same: https://www.dw.com/de/spaniens-erster-lockdown-war-verfassungswidrig/a-58270280
20:52:34 <buc>  
20:57:15 <buc> After 10 seconds (standard timeout), SM tries to launch the (modal) dialog. In the old version, after another 5 seconds, the window still appears, but since 2.53.9 it does not. Looks like "modal window appearing event" got lost in the garbage events generated by the site.
20:58:32 <buc> Something like the prio should be "high", but actually "normal". For the buttons (if any) should be "input", but actually "normal".
21:03:58 <buc> Since it is likely enough that some site will behave broken with SM nowadays with producing of heavy cpu load, it is better to find the reason and make sure user can stop the crap before the whole OS hangup.
21:08:31 <buc> Surely better find right now, while the site is not changed and the test case is not gone.
21:18:00 <WG9s> buc: stom cllaing me SHirley!
21:19:55 <buc> Bella, don't write on behalf of your biped - we'll guess it's you anyway. :)
21:26:18 <a-865> frg_Away: buc was responding to "frg_Away: where is this 2.53.10 for fedora with iso dates patch to be found?" sent about 20 hours ago.
21:29:16 <buc> a-865: Well, this channel has two logbots... :)
23:09:05 <frg_Away> vbuc mozilla changed the whole background monitor stuff. I ripped out what I think was only used for telemetry. Need to check how it it is in 2.57 but mostly the dialog comes up for me just a bit late.
23:35:24 <frg_Away> buc Backport of bug 1356334 maybe. 2.57 is affected. Looks like a deadlock related to mutilmedia not strictly script. Bug 1722225 is not in 2.57 so can't be this one. Firefox shows a notification but mulitprocess. Might need the browser/modules/ProcessHangMonitor.jsm stuff backported.
23:44:19 <buc> frg: Firefox (built over SM tree) has the same issue when MOZ_FORCE_DISABLE_E10S set. And ProcessHangMonitor.jsm looks like for e10s only.
23:47:14 <frg_Away> buc might be another issue mozilla introduced for non e10s. When I debugged I saw a deadlock.
23:54:54 <WG9s_> so can maybe make it fail in firefox by seyting the ipc.processCount to 1 and then file a bug?
23:59:56 <frg_Away> WG9s_ waste of time to report non e10s bugs these days. Last one with a crash did rot and was closed because no more crashes reported for Firefox.