frg_Away: where is this 2.53.10 for fedora with iso dates patch to be found?

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

SM 2.53.10 version

Guest1566: are you running adblockers or something?

Only within SM I think but no addons

OK, so basically a stock install

Yes, that is correct.

Hit F12, try to login, and check the console for errors

what do they use for captcha, ReCaptcha or something else?

recaptcha is used

ReCaptcha still works fine with SM last time I got inflicted with one (which was... last week?), so could be something else...

well, open the developer tools with F12 and let's check for any possible JavaScript and network errors

Is that shift f12 or ctrl f12?

just F12

and then select the Console tab

then try to login

Fn f12 worked, I think

hopefully is not Yet Another Bleeding-Edge JavaScript place

oh, a laptop then

Sorry, yet laptop, Lenovo T460p

tracking protection is enabled ... is the load failure message.

google tagservice

no SyntaxErrors or anything like that?

Try to login until you get stuck, then watch the console

Now it just loops back to sign in... no change in console messages... I will scroll through them now to be sure.

The resource at “googletagservices.com/tag/js/gpt.js” was blocked because tracking protection is enabled.

[Learn More]

12949-vegan-quick-biscuits

Loading failed for the <script> with source “googletagservices.com/tag/js/gpt.js”.

12949-vegan-quick-biscuits:1

The resource at “google-analytics.com/analytics.js” was blocked because tracking protection is enabled.

[Learn More]

12949-vegan-quick-biscuits

The resource at “5290727.fls.doubleclick.net/activit…cipes%2F12949-vegan-quick-biscuits?” was blocked because tracking protection is enabled.

[Learn More]

12949-vegan-quick-biscuits

The resource at “ad.doubleclick.net/activity;src=529…wgba1;auiddc=1381185018.1637372763?” was blocked because tracking protection is enabled.

[Learn More]

12949-vegan-quick-biscuits

The resource at “insight.adsrvr.org/track/pxl/?adv=b…5m7t&fmt=3&ttl=43200>mcb=1826788752” was blocked because tracking protection is enabled.

[Learn More]

12949-vegan-quick-biscuits

The resource at “static.chartbeat.com/js/chartbeat.js” was blocked because tracking protection is enabled.

[Learn More]

12949-vegan-quick-biscuits

Loading failed for the <script> with source “google-analytics.com/analytics.js”.

12949-vegan-quick-biscuits:1

Loading failed for the <script> with source “static.chartbeat.com/js/chartbeat.js”.

12949-vegan-quick-biscuits:1

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at abra.api.nytimes.com/v12/allocation…ment%2CCOOK_TP22_UserToolsInNavExpe

riment%2CCOOK_TP26_NoFreeTrial%2CCOOK_WEB_TP27_LpBypass%2C0_control&agent_id=95lG7fgVFWX8ZNr9_XtPPh. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).

These are normal, pure ad BS

Content Security Policy: Ignoring ‘x-frame-options’ because of ‘frame-ancestors’ directive.

Loading failed for the <script> with source “s.go-mpulse.net/boomerang/ATH8A-MAMN8-XPXCH-N5KAX-8D239”.

enter-email:1

Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified

Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified

Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified

Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified

Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified

Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified

Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified

Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified

Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified

Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified

Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified

Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified

XML Parsing Error: not well-formed

Location: geo.captcha-delivery.com/captcha/ch…NMUci84WiSBmvQ_URIuCDYv3pSWPlvPOjgV

mq33VgKd2sYG-IeNz0pzwkevo5aX7_rEWmLiMMFIFM3mAa5Z85L2IUc1IhXcdL4wuY2CJBxtQBB75kZzciDyfgUqvA0A8hnAogXcPutUbOpfqzzcBh94nMKmyaOlQDXv6qint75YaGiBGEgSyB_ZPolGY91E-VYg1e3Fc4IEH1LPLME_zlEeJOJCR45kbpgSaaqZtmZGrm5m4QbwtgfMYmCdC7BAdZ04avbW4dbwcNhfHyVnG6tq_QTGRSYlfRVMQADMurztB8yDxseese5RHfEcCd_ArOhTBRX_Mx1wnwY7uH2yuur4NTpeCXayIAi5tG8Dzh4kNNgSlGXr-RU9zzvqoEIcgwWCSP0WXmrst4YIwJns1OPXEoN0mAURVa4ZSNI5PdKb0zJHx4gv

-q6mDrRVDz5z9H2zvnR_18_yd4pOHaIvXNkWEJM_QkP98b9jaEcmxwS56IZIbJg0xQq1rBI_PLR4KWv4_jNeQnK5j5V9Fl6sCNLxGVX64dSdkpPZqrDau4Byx-g-MAjc7D-WCn_ivg4LTzvg0W35UcJxzBiZrjzh60Jgse78EjSJJLdYwzKUXqN9aGx1zCOwQM7Z0DQgO4wNMMeeIY3ZHkSBo4Zqm5Z8sz9mMgnTeYs3DmLBfl5P3JQqZ0vr4lZKHcJvOa9UFcPAeHXXvkGgjSGSo4Eci_583nXPop8Mfik4wzQwDGBPmCIh6SNMnvgNwjxWjPLyf3xAfmJNCAW3GBfkwgYod187DFifY8T83f6JbZEFRzNVtM05S9vRNdIasd3qnfam_IXQeLGv

miMvOj-c4KfY4j4bLCZBQWvIjR_Q2w8TJk5WtZb4qMfoKJ3nU9AMpx6LlA_NUMyO2zg_MDnaESNU_-XZXHP4KM6bb-dsLO7mV0qgBl5-Sl-ijNieM50DCWK0S3vKXAhkjBZJutVtdfRFX67W2uFELqwEPnB6kWO7vcP9722aGksYYBxXwJynMFYxSS4VL8n152omBBlicY8MNgXF8wZILPtreNyHdpiBBLnVJN1NIWWMRKK4soHSmunXZ1ynTVxrzyD4Ad0X_MTLQnLlOtrqd1PT9xSXacSQPBi50uaT3mMvsw7-v8_UK5ByqX2GrdOBw3I5PvrvL1dvXrVenxxrVGN3H2cTBfLXf_w2qKMUGU9KvTCyzG5-bU8fYbdi6O8th2zWXskYCVn8x3JM

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-

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

2Frecipes%252F12949-vegan-quick-biscuits%26display%3Ddefault%26application%3DCooking%26preloaded%3Dfalse&x-forwarded-for=&captchaChallenge=13090466&s=9648

Line Number 1, Column 1:

ooooh, an XML error!

check:1:1

Content Security Policy: Ignoring ‘x-frame-options’ because of ‘frame-ancestors’ directive.

Loading failed for the <script> with source “s.go-mpulse.net/boomerang/ATH8A-MAMN8-XPXCH-N5KAX-8D239”.

interesting

enter-email:1

Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified

Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified

Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified

Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified

Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified

Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified

Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified

Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified

Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified

Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified

Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified

Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified

Aside of the tracker blocking and Content Security Policy warnings, the only noteworthy error would be that "XML Parsing Error: not well-formed"

from that insanely long URL at geo.captcha-delivery.com

Is there a way to rectify XML Error?

that error happens because the server is sending corrupt/malformed XML to the browser

Yet, I have no issues using Chrome and presume they are sending the same XML to that browser, correct?

could be yet another case of botched user agent sniffing on their side

WTF

pasted your URL here

...and the server sends JSON, not XML!

Which means no work around, correct?

something on their scripts are expecting XML, or maybe SeaMonkey is assuming some document type wrongly

Using SM that is...

it needs more testing, indeed

that's definitely a weird error

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.

the server is definitely not sending the correct content type for their reply

which is causing SM to interpret it as XML somehow

Guest1566: worth testing that on Firefox, just to rule out a possible Chromeism

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?

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...)

nope, that's a SERVER-SIDE problem

why it's triggering SM? Dunno

Okay, nothing I can do at the moment.

NYTimes.com don't have free accounts, right?

Yes, they are limited in scope.

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

it's curious that this time it's not yet another unimplemented JavaScript feature (I hope)

I need to create a bug report for this error, correct?

would be nice

No, not to be nice but to be helpful... and helped.

What info do you think needs to be included in the report?

At the very least a sample URL, and the errors/warnings you're seeing at the console

Hmmm, curious

I just created a free account with a throwaway email

set a password

and logged in fine

no captcha at all

maybe I got lucky and didn't got punished with a captcha

I will give you my login info to see if you can login..

OK, managed to login just fine

didn't got a captcha

Without a captcha, this will be hard to debug...

could be IP address related?

I'm not even in the USA!

Hmmm, meaning that it does not like where I Am logging in from, correct?

maybe, maybe not

but then, you say your logon works fine from Chrome on the very same computer, right?

Try with a clean profile

Yes, that is correct.

You mean a SM clean profile, right?

you can rule out profile corruption or addon/extension interference by testing with a clean profile

yeah

In any case, ReCaptcha is Google, and when Google is involved, expect crazy

Okay, great.... thank you for your insight and recommendations

FYI, Gentoo has just lost his seamonkey package maintainer: gitweb.gentoo.org/repo/gentoo.git/c…ad78eea8b29a4754267c5c42fb8be9fe707

"due to unreasonable qa demands"

...what?

not familiar with Gentoo at all, what's the backstory there?

tomman He can be fould here accasionally and might answer.

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

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 :)

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...

...reponsive to user bug submissions.

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.

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.

a-865: The patch you are interesned in is here: src.fedoraproject.org/rpms/seamonke…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.

buc what regressions do you think are in 2.53.10 ?

frg_Away: buc just posted that and then left

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.

An example is the same: dw.com/de/spaniens-erster-lockdown-war-verfassungswidrig/a-58270280

 

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.

Something like the prio should be "high", but actually "normal". For the buttons (if any) should be "input", but actually "normal".

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.

Surely better find right now, while the site is not changed and the test case is not gone.

buc: stom cllaing me SHirley!

Bella, don't write on behalf of your biped - we'll guess it's you anyway. :)

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.

a-865: Well, this channel has two logbots... :)

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.

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.

frg: Firefox (built over SM tree) has the same issue when MOZ_FORCE_DISABLE_E10S set. And ProcessHangMonitor.jsm looks like for e10s only.

buc might be another issue mozilla introduced for non e10s. When I debugged I saw a deadlock.

so can maybe make it fail in firefox by seyting the ipc.processCount to 1 and then file a bug?

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.