Deleting the only blip in the root thread is not handled well correctly
-----------------------------------------------------------------------
Key: WAVE-267
URL: https://issues.apache.org/jira/browse/WAVE-267
Project: Wave
Issue Type: Bug
Components: Web Client
Reporter: Michael MacFadden
When you create a wave the root thread contains a single blip by default. If
you delete this blip right off the bat several strange things start to happen.
First Case:
1) Create a new wave.
2) While still in edit mode click the delete link in the single blip.
3) The reply box is not shown.
At this point without refreshing the browser you can't create a new blip. If
you now click on another wave, you get a shinny. If on the other hand you
refresh the browser the reply box comes back.
Second Case:
1) Create a new wave.
2) Click edit to get out of edit mode.
3) Click the delete link.
4) Click the reply box.
We get a shinny.
I am not certain what the correct behavior is, but I am sure this is not it.
Should we prevent the user from deleting the blip if it is the only blip in the
root thread. I don't see a case where a conversation with no blips is useful.
If we do want to allow the user to delete this blip, the what is the UI
metaphor for creating a new blip in an empty thread. The reply box is probably
not correct since you aren't replying to anything.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
