Trevor Parscal <> changed:

           What    |Removed                     |Added
                 CC|                            |

--- Comment #4 from Trevor Parscal <> ---
What if the article "Abc" has a DEFAULTSORT set to "Alphabet", but is then
renamed to "Alphabet", making the DEFAULTSORT and article title the same. Then
someone opens the category editor, upon save we see that DEFAULTSORT and the
article title are the same and remove it. Now you have a dirty diff.

So, we see that separating the default value of the actual value is... well,

The UX issue is that we force the user to start from scratch when editing the
field. The real cause of all this is that we are using the value of text input
widget to not only detect a change, but also whether to set or not.

We may consider doing something else, like having a tick to explicitly override
the sorting key, and separately have a text input widget which, as requested,
is populated with the default or current value.

There are a few things I'm not happy with here, however.

* What happens when DEFAULTSORT is set to empty string?
* It feels like we are adding too much complexity
* If the user unticks override, does the text input widget's value get set to
the deafult value, or just get grayed out (either has it's downfalls)

You are receiving this mail because:
You are on the CC list for the bug.
Wikibugs-l mailing list

Reply via email to