[luci] [BUG] LuCI checkbox parsing

[Jo-Philipp Wich]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Jouke.

> I think to have stumbled upon a bug in LuCI's parsing of checkboxes.
> As far as I can see it is introduced with the reparsing first found in
> Changeset 2696 (2008, July 30).

Thanks for tracking this down, I'll look into it asap.

> Since the commit before the reparsing changes the section names,
> subsequent calls to any formvalue function are deemed to return nil.
> For checkboxes this is a problem, because nil is also the value
> returned for unchecked checkboxes. The result is that Flag.parse
> cannot distinguish between unchecking and reparsing (strictly
> speaking: not in a stateless manner) and will raise an unckecking even
> (calling the write method) after it has been checked before!
> This situation occurs when the LuCI application also contains other
> fields that are changed in the submit.

This is obviously not the intended behaviour, need to investigate it later.

> 
> This report is sent to you personally because I do not have permission
> to open tickets in the LuCI track, nor am I a member of the
> mailinglist.

If you like you can sign up on
  https://lists.subsignal.org/mailman/listinfo/luci .

You can open tickets with the login "reporter", password "ticket".
The login became necessary because ticket spam increased a lot.

The login info is also on the Trac wiki page.



Regards,
~ JoW
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkpwkf4ACgkQdputYINPTPO3eACfcMACOq9vWaTvAYKEN/3hVPYh
208AoKF9uBHnK9MqaQun1Co1TF0vqaZ8
=BYhd
-----END PGP SIGNATURE-----