Bug#808285: tracker.debian.org: Subscription keywords management is over-complex

[Christophe Siraut <d@tobald.eu.org>]

Hi,

Raphael Hertzog wrote:
> While I certainly love simplicity and better code, I don't think that
> it's good idea to drop the ajax + javascript on that page. Switching
> back and forth between different pages to change keywords on multiple
> packages is not very good UI.

Not ack, showing a form in a modal window or fullscreen makes no real UI
difference: both ways require the same number of clicks, the same number
of server requests, the same content is displayed, except the greyed
background in the case of a modal window.

Ajax is good for displaying a sandglass picture while content is
loading, it is not meant for replacing broader HTML requests management
because that requires implementing a javascript browser in a browser.

In this case, when a user change his/her keywords, a form is posted and
data is validated, why bother doing that asynchronously?

> But it certainly needs to be cleaned (some ajax request can be avoided)...
> and we need to ensure that the fallback when javascript is disabled do
> actually work.

Let's avoid duplication of processes, and not maintain 2 ways of
managing subscriptions keywords (javascript+fallback). What you call
fallback is the correct way IMO. The same content could enventually be
displayed in a modal window for javascript-augemented browsers using a
XMLHttpRequest. 

Cheers,
Christophe