Yes, where is the solution? There are several things like this that are wasting my time because I first think I'm doing something wrong, or there's some hidden checkbox in the seemingly endless and confusing options provided in the "advanced" button of the widget's settings. I get to a forum like this, and find I have to implement a workaround. When it does get fixed by Sitefinity, I'll have to undo the workaround - everybody here will. Add this in with other overlooked content problems that require hacky workarounds (like not being able to predetermine margins on floated images on a blog
). I'm not surprised that bugs like this don't get fixed. It makes a better press release saying version 5.0 has new this and new that, rather than fixing bugs for the people already using it.
Here is the workaround I am using. It finds the last <br /> that is a direct child of .sfContentBlock and hides it. Someone replied with one before that would just hide the last <br /> tag, which you may not want to do in all cases.