Follow-up Comment #17, bug #60927 (group groff): At 2025-08-25T18:28:03-0400, Dave wrote: > Follow-up Comment #16, bug #60927 (group groff): > > [comment #14 comment #14:] >> the URL Savannah constructs uses HTTP GET is a particularly >> lunkheaded way: _all_ parameters are explicitly specified >> even if their values match the default. > > I don't see any way around that, because "the default" is a moving > target. That is, while you're logged in to savannah, if you specify > bug parameters, those parameters continue to apply to subsequent bug > displays until explicitly changed.
I was thinking of the "delta" relative to the default being the
accumulation of changes from the "bugs/?group=xxx" page default (as they
are when coming into the site "cold"), not relative to the most recent
page submission.
> That is, click on savannah's "Bugs -> Browse" menu item to see the
> full bug list, then view a shorter list by specifying a specific value
> for some field. After that, click "Bugs -> Browse" again. You're not
> taken back to the full list, but to the shorter one, even though the
> URL does not specify this restriction.
Yes. It appears that this web application is not designed as I would
design it.
> So for a URL intending to show a specific bug list, it has to specify
> all parameters, because it doesn't know what state your last search
> left you in.
I don't think it needs to, but it seems likely that any remedy to this
problem would demand some redesign of the applications state-tracking.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?60927>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
