This markup:
{F60 width=160, float} {F62 width=160, float} {F63 width=160, float} {F66 size=full} --- ==Test
Incorrectly renders as:
swisspol | |
Jan 9 2016, 8:38 PM |
F1058060: sockshibe.jpg | |
Jan 9 2016, 11:49 PM |
F1058053: pasted_file | |
Jan 9 2016, 11:43 PM |
F1057989: Screen Shot 2016-01-09 at 1.46.17 PM.png | |
Jan 9 2016, 9:58 PM |
F1057980: sockshibe.jpg | |
Jan 9 2016, 9:51 PM |
F1057939: pasted_file | |
Jan 9 2016, 8:38 PM |
This markup:
{F60 width=160, float} {F62 width=160, float} {F63 width=160, float} {F66 size=full} --- ==Test
Incorrectly renders as:
My expectation would be this floats forever given current syntax. The only solution I can think of is a new Remarkup rule for clearing, which you can place anywhere down the line, which is what it sounds like you're suggesting.
Can you place them in a table in the meantime?
Yeah. I think:
I do think we could reasonably put clear: both on hr and probably headers. I think it used to run into some problems with tables of contents, but we never (I think?) put them inline anymore (maybe in readmes in Diffusion?) so we should be in the clear, now.
But I think the fix to the root problem here is basically "use inline, not float".
@epriestley Are you sure inline works?
{F60 width=160, layout=inline} {F60 width=160, layout=inline} {F60 width=160, layout=inline}
Renders as:
PS: We are on the hyper instance on Phacility.
Doing a bit more digging here... layout=inline doesn't work if coupled with size=xx.
Just trying to have it all :-)
D14983 fixes the interaction between inline and width. I'll push it to this server and wipe the cache now, and the comment above should start working.
(This will hit Phacility SAAS in about a week.)
Do you have a case in mind where not clearing h1 (or h3 .. h6, for that matter) is useful offhand?
The most interesting thing I can come up with is that you might want to do this, maybe:
BIG HEADER XXXX ------------ XXXX xt text text XXXX text text te text text text text text.
But that seems like it's probably OK as this, instead, with the header clearing both?
BIG HEADER ------------------ text text te XXXX xt text text XXXX text text te XXXX text text te xt text text text.
I'll clear hr in the meantime, I think that's unambiguous.
Oh! Well that would make perfect sense, then. I'll update D14984 to just clear all the headers that remarkup can emit.
At HEAD:
These changes will likely be pushed to the Phacility cluster next Saturday morning (January 16).
Please add the triple dash to the documentation page, I couldn't find it clicking on the main life-saver icon link.