make inclusions inline again by default+discussion

no can do. this caused all sorts of problems. short version is that block inside inline is bad, and since many many cards have block elements (eg divs) inside their content, making the content view wrapper default to inline is bad.

 

However, with the recent updates, you can just put "display: inline" in the inclusion syntax. (gets added to the style attribute of the card-slot, which is now sufficient, as there is no inner content wrapper)

--Ethan McCutchen.....2013-10-12 15:26:40 +0000

could also experiment with "inline-block". to try this out you'd just add .content-view { display: inline-block } somewhere in the css.

--Ethan McCutchen.....2013-10-12 15:27:53 +0000

Thx for the quick reply.

 

Re your first comment, that does not seem to work. I updated http://test.dwagn.org/inclusions_no_longer_inline with display:inline but it still jumps down to the next line.

 

Re the second comment, if I get you right that CSS might make inclusions inline by default? If so, any reason not to put that in our default CSS? And not clear how that relates to "block inside inline is bad."

--John Abbe.....2013-10-12 23:02:06 +0000

it wasn't working in that example because the wrapping text was a p tag. It's always been the case that a div inside the p tag breaks the html.

 

the reason not to put it inline-block in the default CSS is that we haven't experimented with it yet :) I think there's a good chance that might be a good way to go.

 

inline-block is a blend of inline and block properties; block inside inline is bad, but I don't think block inside inline-block is.

--Ethan McCutchen.....2013-10-12 23:36:19 +0000