You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Mr @Alex313031 , we know that you generousely added the possiblity to disable captive portal in Thorium after my request , thank you so much !
and recently, i discover special Chromium for windows 7 OS 32 bits ,
and i ask Mr E3kskoy7wqk the developer of Chromium-for-windows-7 to add option to disable captive portal and here his very interesting and instructive response ! :
"Hello, thank you so much for your suggestion! I reviewed the methods used in cromite, thorium and supermium, and it seems effective, but for now, I don't plan to adopt their methods.
I noticed that, many years ago, Chromium used the enable-captive-portal-detection switch to control the enabling and disabling of captive portal detection. However, after July 27, 2012, 17:15:16, this switch was removed, and captive portal detection became enabled by default. I think that by reversing the logic of this switch's removal, I could achieve the same result. Therefore, I've added this switch back, but due to limited testing environment, I'm unsure if it works as expected.
If this approach doesn't work, I might consider adopting the methods used in cromite, thorium and supermium."
The text was updated successfully, but these errors were encountered:
Hi Mr @Alex313031 , we know that you generousely added the possiblity to disable captive portal in Thorium after my request , thank you so much !
and recently, i discover special Chromium for windows 7 OS 32 bits ,
and i ask Mr E3kskoy7wqk the developer of Chromium-for-windows-7 to add option to disable captive portal and here his very interesting and instructive response ! :
"Hello, thank you so much for your suggestion! I reviewed the methods used in cromite, thorium and supermium, and it seems effective, but for now, I don't plan to adopt their methods.
I noticed that, many years ago, Chromium used the enable-captive-portal-detection switch to control the enabling and disabling of captive portal detection. However, after July 27, 2012, 17:15:16, this switch was removed, and captive portal detection became enabled by default. I think that by reversing the logic of this switch's removal, I could achieve the same result. Therefore, I've added this switch back, but due to limited testing environment, I'm unsure if it works as expected.
If this approach doesn't work, I might consider adopting the methods used in cromite, thorium and supermium."
The text was updated successfully, but these errors were encountered: