Preview/session behavior in browser steps differs from runtime behavior

[Xcessiv]

Hello,

I am a delighted user of changedetection.io and would like to express my gratitude for your exceptional work.

My setup: changedetection.io v0.45.8.1 with browserless/chrome:1.60-chrome-stable.

I am encountering an issue while trying to log in to the following website through browser steps: https://gmfstlucsteugene.portail.medfarsolutions.com/en/login

Question 1: The site has a feature that disables the Login button if the username and/or password fields are empty. This works correctly in the browser steps' preview mode, but not during actual checks. The button remains inactive. Here's what I've tried:

• Adding delays.
• Pressing Enter multiple times with intervals.
• Clicking on the Login button directly.

However, screenshots indicate that I am unable to move past the login screen, even though I can log in successfully in the preview mode.

Question 2: To address this, I attempted to use JavaScript with document.getElementById('account_login').submit(), but this redirects me to a different page displaying a "Snapshot of Authenticate generated by ServiceStack" with my bearer token. Alternatively, the jQuery command $('#account_login').submit(); works perfectly in preview mode, taking me to the desired page in the browser steps' preview mode. Unfortunately, when running real-time checks, this jQuery command does not yield any results.

I appreciate any assistance you can provide.

[CrazyWolf13]

Hi, I'm running into the same issue and wanted to add some additional context that might help @dgtlmoon reproduce it.

My setup: changedetection.io (v0.55.7) with sockpuppetbrowser, monitoring a Kendo UI-based website.

The core problem is identical: browser steps work perfectly in preview mode but fail completely during actual fetches. Specifically:

• Login succeeds in preview, but during actual checks the page either shows the login screen again or throws a server-side error, suggesting the session/cookies are not being carried over correctly into the real fetch context.

Is there a fundamental difference in how the browser context/session is initialized between preview mode and actual fetch runs? It seems like cookies set during the login flow in preview don't persist into the fetch context.

Thanks for any info!