Comment 3 for bug 330550

2009/2/18 Karl Fogel <email address hidden>:
> +1 on just doing it. In the rare cases where a user wants to say "this
> affects me" but doesn't want to be subscribed, they can still
> unsubscribe manually (which would not change the "affects me" status).
>
> Funny UI notes:
>
> Since this bug affects me :-), I just clicked on both "Email me about
> changes to this bug report" and on the "change" button next to "this bug
> doesn't affect me". Well, sort of: first I got confused about how the
> email-me checkbox differs from subscribing. Then, after deciding they
> probably mean the same thing even though they have completely different
> UIs, I clicked the email-me button first followed by the affects-me
> button... unfortunately, the latter reloads the page, so I lost the
> comment I had just typed. Didn't see that coming. Did everything over
> again, except that now I didn't have to click the affects-me button
> because it was already checked.
>
> I wonder if there's already some bug filed for "Clicking on anything
> that doesn't look like it should navigate away from the page should also
> never reload the page, so that other (potentially unsaved) inputs on the
> page are not lost."

That's a good point, but this problem will go away when we move to
in-page, ajax controls. The implementation we currently have (which
reloads the page) is not a pattern we have anywhere else, and we
should avoid it in the future.