[
https://issues.apache.org/jira/browse/WAVE-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033883#comment-13033883
]
Michael MacFadden commented on WAVE-267:
----------------------------------------
For clarification, I think there is a subtlety that I would like to discuss.
There is a difference between special handling of the "First Blip" vs special
handling for the "Sole Blip" in the root thread. When there is only one blip
in the root thread, the the "First Blip" is also the "Sole Blip" in the thread.
If there are other blips in the root thread aside from the "First Blip", then
the "First Blip" is not the "Sole Blip" in the thread. So the "Sole Blip" is
always the "First Blip", but the "First Blip" is not always the Sole Blip.
The ramifications of deleting in these two scenarios is a bit different.
"First Blip" (w/ other Blips):
This is hard to delete because as Dave mentions we use it for the wave title
and the wave ownership. However since there are other blips in the thread, if
you delete this blip you don't wind up with an empty root thread that is in a
very weird state. When you change the text of the first blip, the title of the
wave changes, if we delete the first blip, the next blip in the thread could
simply take on the role of the "first blip" and we can update the wave title to
reflect that. The ownership issue is not as easy to deal with, but possibly we
should consider an alternative model for this that avoids attaching special
meaning to this first blip.
The main point here is that if there are other blips in the root thread, than
deleting the "First Blip" still leaves you with blips to work with and reply
too.
"Sole Blip"
Everything applies as in the "First Blip" scenario, but you also have the
additional problem that the root thread now contains no blips. As discussed
this is probably not a desirable scenario.
In short, when talking about when to disallow deleting, we should consider
these two separately. We might want to disallow in both scenarios or just one.
We may disallow deleting in both scenarios for now as a workaround, but decide
that we should eventually allow deleting of the First Blip as long as there are
others.
> Deleting the only blip in the root thread is not handled well
> -------------------------------------------------------------
>
> 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
