Martin Marinschek schrieb:
We could optionally do that - don't know if that is practical.
I've discussed with Manfred some more, and he suggests to do the following:
give t:saveState an optional "bookmarkable"=true attribute, and with
that decide on some of the state to be saved even though the
tree-state is lost.
we could also log an error to the user when the maximum url-size is exceeded.
That error is definitely mandatory to avoid constant posts in the users
list why data gets lost ;-)
No in fact the size limitation is one of the reasons post usually is
preferred for form handling, such an error would help alot in a get
situation to track down problems.
