Is there a way compatible with IE that you can add a line break before or after a certain inline element?
eg:
<tag1>Text</tag1><tag2>More Text</tag2><br />
or
<br /><tag1>Text</tag1><tag2>More Text</tag2>
like this
<tag1>Text</tag1><tag2>More Text</tag2>
but with the same effectSet their "display" properties to "block".then they wouldn't be inline anymore...Also does anyone know if inline-block works?Well, I'm assuming these are two things of data you wish to divide? Foo bar. <div><tag1>Text</tag1><tag2>More Text</tag2></div> What's wrong with that?well then I might as well just stick <br /> at the endOriginally posted by IncaWarrior
well then I might as well just stick <br /> at the end <div> is more semantically meaningful than <br /> in this situation.well it would still be nicer to have something that would just make line break before or afterI don't get what you're trying to achieve. From my perspective (I'm probably wrong on this) it looks like a definition list. You know:
term - description
term - description
term - description
In which case
<dl>
<dt>Term</dt> <dd>Description</dd>
<dt>Term</dt> <dd>Description</dd>
<dt>Term</dt> <dd>Description</dd>
</dl>
May be betterHumm...I may have a solution, not sure how well it works, never tried it yet. This is also what I was looking for on one of my issues.
More info here, <!-- m --><a class="postlink" href="http://www.w3.org/TR/REC-CSS2/generate.html#content">http://www.w3.org/TR/REC-CSS2/generate.html#content</a><!-- m -->
tag:before { content: "<br />"; }Originally posted by rpanning
Humm...I may have a solution, not sure how well it works, never tried it yet. This is also what I was looking for on one of my issues.
More info here, <!-- m --><a class="postlink" href="http://www.w3.org/TR/REC-CSS2/generate.html#content">http://www.w3.org/TR/REC-CSS2/generate.html#content</a><!-- m -->
tag:before { content: "<br />"; }
Originally posted by IncaWarrior
Is there a way compatible with IE ...
No dice. Good-for-nothing IE doesn't understand the content property.Originally posted by Paul Jr
No dice. Good-for-nothing IE doesn't understand the content property.
Dang Microsoft again, not conforming to Web standards...lolOriginally posted by rpanning
Dang Microsoft again, not conforming to Web standards...lol Actually, you can't really blame M$. content, :after, and :before are CSS3. CSS3 isn't finished. Can you expect them to fully support something still being worked on?Originally posted by Ben R.
Actually, you can't really blame M$. content, :after, and :before are CSS3. CSS3 isn't finished. Can you expect them to fully support something still being worked on?
You mean CSS2? Which is out. It's in the documentation.
<!-- m --><a class="postlink" href="http://www.w3.org/TR/REC-CSS2/selector.html#before-and-after">http://www.w3.org/TR/REC-CSS2/selector. ... -and-after</a><!-- m --> (<!-- m --><a class="postlink" href="http://www.w3.org/TR/REC-CSS2/selector.html#before-and-after">http://www.w3.org/TR/REC-CSS2/selector. ... -and-after</a><!-- m -->)It's not for a definition list, and the code for that is basically the same as what I posted I have.
I think it's fair to blame microsoft for the faults of IE, all the other browsers support those elements.
eg:
<tag1>Text</tag1><tag2>More Text</tag2><br />
or
<br /><tag1>Text</tag1><tag2>More Text</tag2>
like this
<tag1>Text</tag1><tag2>More Text</tag2>
but with the same effectSet their "display" properties to "block".then they wouldn't be inline anymore...Also does anyone know if inline-block works?Well, I'm assuming these are two things of data you wish to divide? Foo bar. <div><tag1>Text</tag1><tag2>More Text</tag2></div> What's wrong with that?well then I might as well just stick <br /> at the endOriginally posted by IncaWarrior
well then I might as well just stick <br /> at the end <div> is more semantically meaningful than <br /> in this situation.well it would still be nicer to have something that would just make line break before or afterI don't get what you're trying to achieve. From my perspective (I'm probably wrong on this) it looks like a definition list. You know:
term - description
term - description
term - description
In which case
<dl>
<dt>Term</dt> <dd>Description</dd>
<dt>Term</dt> <dd>Description</dd>
<dt>Term</dt> <dd>Description</dd>
</dl>
May be betterHumm...I may have a solution, not sure how well it works, never tried it yet. This is also what I was looking for on one of my issues.
More info here, <!-- m --><a class="postlink" href="http://www.w3.org/TR/REC-CSS2/generate.html#content">http://www.w3.org/TR/REC-CSS2/generate.html#content</a><!-- m -->
tag:before { content: "<br />"; }Originally posted by rpanning
Humm...I may have a solution, not sure how well it works, never tried it yet. This is also what I was looking for on one of my issues.
More info here, <!-- m --><a class="postlink" href="http://www.w3.org/TR/REC-CSS2/generate.html#content">http://www.w3.org/TR/REC-CSS2/generate.html#content</a><!-- m -->
tag:before { content: "<br />"; }
Originally posted by IncaWarrior
Is there a way compatible with IE ...
No dice. Good-for-nothing IE doesn't understand the content property.Originally posted by Paul Jr
No dice. Good-for-nothing IE doesn't understand the content property.
Dang Microsoft again, not conforming to Web standards...lolOriginally posted by rpanning
Dang Microsoft again, not conforming to Web standards...lol Actually, you can't really blame M$. content, :after, and :before are CSS3. CSS3 isn't finished. Can you expect them to fully support something still being worked on?Originally posted by Ben R.
Actually, you can't really blame M$. content, :after, and :before are CSS3. CSS3 isn't finished. Can you expect them to fully support something still being worked on?
You mean CSS2? Which is out. It's in the documentation.
<!-- m --><a class="postlink" href="http://www.w3.org/TR/REC-CSS2/selector.html#before-and-after">http://www.w3.org/TR/REC-CSS2/selector. ... -and-after</a><!-- m --> (<!-- m --><a class="postlink" href="http://www.w3.org/TR/REC-CSS2/selector.html#before-and-after">http://www.w3.org/TR/REC-CSS2/selector. ... -and-after</a><!-- m -->)It's not for a definition list, and the code for that is basically the same as what I posted I have.
I think it's fair to blame microsoft for the faults of IE, all the other browsers support those elements.