And Carnival configured with a block_selector of .content > p, the alignment of the comments UI will be off by the distance between the article and the .content element. This can be partially corrected by setting a custom top on .carnival, but that's no robust in the presence of wrapping text (see #201).
A more robust workaround is to not configure the block_selector, but instead set article_selector to .content and set a top: 0 on .carnival.
In general, Carnival should be smarter about placing the comment UI in the presence of nested markup such as this.
Given something like:
And Carnival configured with a
block_selector
of.content > p
, the alignment of the comments UI will be off by the distance between thearticle
and the.content
element. This can be partially corrected by setting a customtop
on.carnival
, but that's no robust in the presence of wrapping text (see #201).A more robust workaround is to not configure the
block_selector
, but instead setarticle_selector
to.content
and set atop: 0
on.carnival
.In general, Carnival should be smarter about placing the comment UI in the presence of nested markup such as this.