Catsxp Forum

Hello, I already asked Mr. @Catsxp to disable the captive portal, and he generously added a commit to disable the captive portal months ago, and we should add in StartupParm setting : --disable-captive-portals

but now I'm discovering this new flag in chromum 132 and chromium 136 to enable/disable captive portal :

chrome://flags/#disable-captive-portals

Will this flag will cause any conflicts with the commit Catsxp added to disable the captive portal?

The chrome://flags/#disable-captive-portals flag in Chromium 132/136 should not conflict with Catsxp’s --disable-captive-portals commit, as both disable the same feature. You can safely enable the flag (if available in Catsxp’s Chromium version) or rely on the existing commit. For your proposed --disable-cache-and-cookies, implement it as described with --disk-cache-size=0, --media-cache-size=0, --disk-cache-dir=/dev/null (or NUL), and --clear-cookies-on-startup. Add it to StartupParm alongside --disable-captive-portals for a seamless solution to both reCAPTCHA loops and SSD wear.

Interesting, thanks for explanation