nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JS Issue with Forms (sarissa.js)

Matias

Hello,
We are having a Javascript error in our forms that we are trying to trace back but cannot find what's causing it. The error happens on load, and we get the following error in the console:

setting a property that has only a getter
sarissa.js()(line 157)
XMLDocument.prototype.readyState = 0;

This happens in the sarissa.js. Anyone has seen this error

Find more posts tagged with

Comments

santosh013

Hello,
We are having a Javascript error in our forms that we are trying to trace back but cannot find what's causing it. The error happens on load, and we get the following error in the console:

setting a property that has only a getter
sarissa.js()(line 157)
XMLDocument.prototype.readyState = 0;

This happens in the sarissa.js. Anyone has seen this error

Hi,
Is this happening only in Mozilla?
Have you tried using some other browsers.
Also mention your TS environment.

Thanks.

nipper

Is this custom code with jquery or is it an OOTB form ?

Have you tried google ? I noticed a few jquery errors with answers like this:

My suggestion/guess would be to not try and set the style of the objects, but set the value of the style property you want to change. For example, fullwidth.style.marginLeft = '20px';. And rather than try and set the style to nothing, you can set marginLeft to 'auto' or something innocuous like that.

Adam Stoller

Hello,
We are having a Javascript error in our forms that we are trying to trace back but cannot find what's causing it. The error happens on load, and we get the following error in the console:

setting a property that has only a getter
sarissa.js()(line 157)
XMLDocument.prototype.readyState = 0;

This happens in the sarissa.js. Anyone has seen this error

Please see this thread

0min.png

Thanks for all your answers! Ghoti is right, that's the exact issue we are seeing.
I was wondering if this may be causing other issues as well, since we are encountering another issue with Sarissa but when we use DataStores. I'll open another topic about it.

Adam Stoller

Thanks for all your answers! Ghoti is right, that's the exact issue we are seeing.
I was wondering if this may be causing other issues as well, since we are encountering another issue with Sarissa but when we use DataStores. I'll open another topic about it.

I suggest you make the fixes (for all three files) first - and then see if that resolves your other problem(s).

No use chasing down a issue which is potentially a side-effect of another [known] issue without fixing [known] issue first.