A cert dialog happens before the tab content loads. An auth box would
seem like a form login if it was before content loads. Afterwards,
you're removing the content to display a login. The behavior is
standard in all browsers AFAIK.
Phoenix wrote:
> Dialog Boxes are evil - why can't the request be done like the one
> for invalid certificates?
>
> In older version of FF a dialogbox jumped when a certificate was
> invalid, meanwhile this is done within the tab - same could be done
> for basic auth requests - so a auth request wouldn't block the
> browser, nor would it be irritating in the event of multiple
> simultanous requests.
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
A cert dialog happens before the tab content loads. An auth box would
seem like a form login if it was before content loads. Afterwards,
you're removing the content to display a login. The behavior is
standard in all browsers AFAIK.
Phoenix wrote:
> Dialog Boxes are evil - why can't the request be done like the one
> for invalid certificates?
>
> In older version of FF a dialogbox jumped when a certificate was
> invalid, meanwhile this is done within the tab - same could be done
> for basic auth requests - so a auth request wouldn't block the
> browser, nor would it be irritating in the event of multiple
> simultanous requests.
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkp /CuoACgkQTniv4a qX/VnZlACfXih+ IhD2/DlLqEg6rb+ m1r3U 4RnkzyJR0qEW75b t6
D3oAnRjsJCL9ASV
=pLyn
-----END PGP SIGNATURE-----