# Newline and IMG tags

**URL:** <https://talk.commonmark.org/t/newline-and-img-tags/2511>\
**Category:** Spec\
**Created:** [July 10, 2017, 2:15pm UTC](https://talk.commonmark.org/t/newline-and-img-tags/2511 "2017-07-10T14:15:38Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![sam](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/sam/32/71_2.png) [@sam](https://talk.commonmark.org/u/sam)\
**Post date:** [July 11, 2017, 12:36pm UTC](https://talk.commonmark.org/t/newline-and-img-tags/2511/9 "2017-07-11T12:36:32Z")

</div>

> [@tin-pot](#):
>
> Hmm—I still don’t quite get it what you mean:

We use a variant of CommonMark that renders

```plaintext
a
b
c

```

as

a  
b  
c

This is discussed in detail here: [Default line break handling is inconvenient](https://talk.commonmark.org/t/default-line-break-handling-is-inconvenient/280)

My expectation is that if this “option” is enabled any sequence of `inline` HTML elements on lines by themselves would behave the same way as the text.

@codinghorror for the record I did “fix” this in Discourse. But I feel that we got to glue some special semantics to HTML inlines if you have the “newline”=`<br>` option enabled.

---

_[View the full topic](https://talk.commonmark.org/t/newline-and-img-tags/2511)._