Dear Maintainer,
Although permanent certificate exceptions cannot be added from private
windows,
existing permanent certificate exceptions once added from normal mode
used to
be effective in private windows under the same profile in previous
version, but
that is not the case in the current version.
Now, even if a permanent certificate exceptions had been added for an HTTPS
site from normal mode, if one opens a private window and tries to access the
very same site with the private window, the warning for untrusted
certificate
will be generated. To suppress the warning, they should add the same
certificate in the private window as a temporary certificate exception
(because
only temporary certificate exceptions can be added in private windows)
over and
over, when they access the site from a private window for the first time
after
they launch firefox-esr.
At least, there should be an option (even in about:config) to control
whether
existing permanent certificate exceptions are effective in private windows,
rather than rejecting them unconditionally.