Noah Kantrowitz wrote: > I am starting to add fallback behaviors to the triage interface, and it > is becoming clear that complete fallback isn't going to work well. The I > can very close, but some things, like resorting a query, will behave > differently in terms of saving pending changes (fields edited in the > triage view, but not yet saved to a ticket). How do people feel about > this? I am a staunch supporter of JS-less fallback, but at what point > should we cut it off? The current implementation does warn users of > this, but I have a feeling at least a few people won't understand the > warning. > It is also worth mentioning that the fallback behavior breaks the paradigm of always redirecting after a POST. It is also complicated by the fact that cgi.FieldStorage ignore QUERY_STRING parameters in a POST.
--Noah
signature.asc
Description: OpenPGP digital signature
