On 10/26/07, Steve Bennett <stevagewp(a)gmail.com> wrote:
What if the fallback is "edit redirects by hand,
as is done
currently"? In other words, is it ok to add a new feature
that requires javascript, if it is effectively an optional feature?
I would say no: currently just about every MW feature that exists with
JavaScript exists without it as well, to the extent reasonably
possible, and that's good. JavaScript should only be required where
it absolutely must me, namely dynamic calculations or adjustments of
page elements, and things in that vein.
But it's not my decision. Ask Brion, if you want to know.
Is it ok to
write to a page
other than the one the user is looking at?
Sure, why not? I'm not sure you'd want to, though.
Well for instance, creating or updating a redirect would require
modifying a page to add the #REDIRECT text...
I suppose so, if that's the way you're going to implement it. It
would be the simplest, yes, in certain respects.
How would this work? Any ideas? I can't see that
dynamic disambiguation
pages could ever fully replace manual disambiguation pages, in the same way
that categories don't fully supplant lists. Do we want a mechanism whereby
both manual and dynamic disambiguation could take place for the same query?
Well, as with categories, we could allow arbitrary article text in an
introduction sort of thing. If, unlike with categories, we also
allowed arbitrary text to accompany each disambig item, and possibly
custom ordering of some kind, I see no reason at all why manual
disambig pages would need to exist.