Hi,

Saving an unaltered status should not resave it (and change the posted date).
It should be simply be left as is... well either that, or allow for a change to be cancelled when the user clicks outside of the text field...

Comments

icecreamyou’s picture

icecreamyou commented
Assigned: Unassigned » icecreamyou
Priority: Normal » Minor

Okay. I'll take care of that. Any opinion on whether users should not be allowed to save an identical status, or whether it should simply appear as if the status was saved even though it wasn't?

soraya_soch’s picture

soraya_soch commented

You know, I actually hadn't realised that FB resaves (and updates the timstamp) the status even if the new text is equal to the previous text.

My bad. It's actually handled the same way...

What do you think though? If a user enters the same text as it previously was, should it be considered a new status, or a user error?

icecreamyou’s picture

icecreamyou commented

Uh, that was the question I asked you....

If it's handled as an error, that means no page refresh, but it also means the user will have no idea what they did wrong. If it's handled as a new status, there will be a refresh, but that means that we can display a message explaining what happened.

I think it's always better to let the user know what's going on, so I'm going to code it as a new status. For those more technically minded, that means that this behavior will occur in the submit function rather than the validate function.

icecreamyou’s picture

icecreamyou commented
Status: Active » Fixed

Fixed locally. Will release a new dev sometime this week.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.