Chromium is expecting [::1] in the bypass list, bracketed. ::1 would not work as expected.
However, in PAC scripts, the host should be unenclosed ::1.
Therefore, special transformation is needed for the chromium target that adds brackets before sending to chrome.proxy.
Changed initial bypass list for new profiles to be [::1] just to be on the safe side. cc/ @l2dy
But it should be able to parse both formats now anyway. After parsing, it will use the correct form depending on the situation. For URL matching and Chromium, the form with brackets is used. For all other situations, the form without the brackets is used.
I will do a release later.
The 2.4.0 release is on its way with the fix.
2.4.0 has been released.
Most helpful comment
The 2.4.0 release is on its way with the fix.