Timeline for Interpretation of Time-limit for Editing Comments
Current License: CC BY-SA 3.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 11, 2014 at 13:31 | vote | accept | Manfred Weis | ||
| Jun 11, 2014 at 10:19 | comment | added | user9072 | @JoelDavidHamkins why are they 'lost'? They are still there and in fact not discarded on failed submission (this would be annoying). [Compare the answer and my comment on it.] | |
| Jun 11, 2014 at 10:16 | history | edited | user9072 |
edited tags
|
|
| Jun 11, 2014 at 1:04 | answer | added | Noam D. Elkies | timeline score: 8 | |
| May 29, 2014 at 7:01 | comment | added | S. Carnahan Mod | Another possibility is to have some visible indication of how much time you have left to submit your edit, while you are editing. | |
| May 28, 2014 at 21:15 | comment | added | user35354 | @EmilJeřábek The linked duplicate has a reply from an SE employee mentioning that the proper solution would be a lot of work. This kind of edge case in comment editing has not a high priority inside SE from what I can tell, which is why I mentioned a solution that likely would require no additional developer effort, even if it is an imperfect one. | |
| May 28, 2014 at 21:08 | comment | added | Emil Jeřábek | @MadScientist: I don’t quite see what this would achieve. The problem is that a user can start editing a comment before the timeout under the promise he is still allowed to do that, but the system tells him the game is over when he tries to actually save the comment. This is primarily a confusing UI issue. Increasing the overall timeout does not solve this problem, it only changes the relative time when it can manifest. | |
| May 28, 2014 at 17:39 | comment | added | user35354 | The simplest solution would probably be to ask SE to increase the limit to 10 minutes, no matter when you started editing. This would likely require no additional developer effort (many such settings are configurable per-site, though I don't know if this one is for sure). | |
| May 28, 2014 at 16:16 | comment | added | Emil Jeřábek | What I could imagine is that if the system detects you started editing and did not yet save the comment, the limit is temporarily raised to, say, 7 minutes, so that you stand a chance of finishing the edit even if you start close to the deadline. Or, if it’s technically feasible, the system could display an alert shortly before the limit expires so that you can at least save what edits you have already done. | |
| May 28, 2014 at 16:03 | comment | added | Emil Jeřábek | What if the edits never get saved because you change your mind and close the browser tab, or you lose network connection? What if you are interrupted by an hour-long discussion with your colleague while writing the comment? I agree that the current behaviour is sometimes annoying, but there still needs to be a (reasonably short) hard time limit even if you start editing. | |
| May 28, 2014 at 12:28 | comment | added | Joel David Hamkins | A point to make in support of this change is that the current system can be wastefully frustrating: one starts an edit in good faith, but in giving care and attention to make quality changes, one exceeds the time limit and then the carefully composed improvements are lost. A pointless and irritating frustration! | |
| May 28, 2014 at 10:16 | comment | added | Manfred Weis | @BjørnKjos-Hanssen no, my question is based on a different issue. I don't want to be able to edit after the 5 minute time frame, I rather don't want the clock keep running if I start editing within that time limit. | |
| May 28, 2014 at 6:33 | review | Close votes | |||
| May 29, 2014 at 7:02 | |||||
| May 28, 2014 at 6:04 | comment | added | Bjørn Kjos-Hanssen | possible duplicate of About the option of editing comments - a different algorithm? | |
| May 28, 2014 at 5:01 | history | asked | Manfred Weis | CC BY-SA 3.0 |