I’ve noticed a small issue with my email client for quite some time now where composing a new email will have several blank lines by default.
It’s not too much of an issue to simply delete them but hey, maybe no one had pointed this out before! So I filed a bug report only to get this response… basically it’s not a bug, its a feature!
For context, this is the “feature”:
Not the end of the world if they trim messages before sending them?
It means you can click a line and type there, no need to press enter a few times first.
Not email, but if I’m taking notes in a text editor I will hold down enter at the start to ensure I can just click and type anywhere.
Now, if that pointless whitespace is being sent, I can imagine it annoying people in long email chains.
I’m not sure why you would need to start an email from halfway down the page? I’m not sure I’m understanding you but I feel like I’m on the verge of having my mind blown about how the other half write emails 🤣 Please explain further, I’m genuinely curious!
For me, I write things from top to bottom. If I want to do a later paragraph then I will simply write it in, then go back to the top and hit enter to create a new line
I have a free account and can’t turn off the mobile signature, which has two blank lines before it. I wonder if turning that setting off just deletes that string, but not the lines.
I have both signature settings turned off and there’s several blank lines.
It’s not a bug just because the software doesn’t conform to your personal preferences. You’re asking for what would be considered an enhancement - not a bug fix.
It’s not about preference. It’s about what every single other email client does, including their own on different platforms, and this is even fixed in their upcoming beta of this same app.
My point is that someone made the decision for it to do that and that the software works just fine as is. It’s not a bug, it’s just a weird quirk. The fact that they made the enhancement you requested doesn’t make the old behavior buggy. Your post title said “it’s not a bug, it’s a feature!”, but the behavior you reported is not accurately classified as a bug.
