# Floating images

**URL:** <https://talk.commonmark.org/t/floating-images/266>\
**Category:** Spec\
**Created:** [September 4, 2014, 9:58am UTC](https://talk.commonmark.org/t/floating-images/266 "2014-09-04T09:58:24Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![mb21](https://talk.commonmark.org/user_avatar/talk.commonmark.org/mb21/32/162_2.png) [@mb21](https://talk.commonmark.org/u/mb21)\
**Post date:** [September 6, 2014, 4:52pm UTC](https://talk.commonmark.org/t/floating-images/266/18 "2014-09-06T16:52:30Z")

</div>

I think @chrisalley’s concern about the separation of content and presentation is valid. That’s why I think we should allow adding classes to images instead of specifying their floating behaviour directly (unfortunately he seems to be also against classes).

To add the `floatLeft` class, `![altText](image.png "title"){.floatLeft}` seems like a good syntax to me. Especially since it’s already [implemented in Markdown Extra](https://michelf.ca/projects/php-markdown/extra/#spe-attr) and in light of a [generic and consistent syntax for attributes](http://talk.commonmark.org/t/consistent-attribute-syntax/272).

---

_[View the full topic](https://talk.commonmark.org/t/floating-images/266)._