I recently updated to 2.1.42 from a version installed just a few months earlier (I think it may have been 2.1.38). I am disappointed to find that line break handling has been changed in an unfortunately unhelpful way.
To be precise, I am talking about using the return key whilst typing in a field on a note, whether when adding a new note or when editing a note in the browse window. Formerly, typing a return closed the current
<div> and opened a new
<div>, but now it simply inserts a
<br>. This is a problem, because a
<br> does not start a new element, but rather it is akin to a forced line break rather than a carriage break in the publishing world.
The consequence of this change is that each next paragraph is not really a new paragraph, and so block-level CSS properties no longer work as intended, such as
padding. For example, if I type three paragraphs, separating each with the return key (as we are used to doing), only the first is indented, because under this new handling the three paragraphs are a single block element.
I beg you to reconsider this change. For the moment I must be more heavy-handed with customizing the HTML for each note, and that is a big time drain for basic note entry. I recognize there are times when a forced line break rather than carriage return would be desired, but the standard implementation is to use shift-return when a forced line break is desired. Please consider implementing a more standard approach. In this regard, the previous implementation was quite superior.
In the current Anki, I am not sure how to actually type distinct paragraphs without directly editing the HTML. Is there something I am missing?