I'll add that the spans offer a little nice extra benefit such as in the
case of:
<h1><span>More of this.</span> <span>More of that.</span> <span>And some of
the other.</span></h1>
where:
span{display:inline-block} is keeping the three points in this statement
together nicely and on their own line on narrow screens,
span{display:inline}will get this on one line when width allows
*but* for widths in between where it can get odd, I can do this:
span:nth-child(2){display:inline} and let it wrap better.
On Sun, Sep 9, 2018 at 12:45 PM Tom Livingston <tom...@gmail.com> wrote:
>
>
> On Sun, Sep 9, 2018 at 12:27 PM Rod Castello <rodcastel...@gmail.com>
> wrote:
>
>> I haven't done it lately, but on some occasions I've used <br
>> class="br1"> and <br class="br2"> and so forth. Then as needed for
>> responsive design I would turn these on or off as needed. It worked okay
>> for specific device widths but was tedious like you say.
>>
>>
>>
> For now, I'm currently doing something similar with spans...
>
--
Tom Livingston | Senior Front End Developer | Media Logic |
ph: 518.456.3015x231 | fx: 518.456.4279 | medialogic.com
#663399
______________________________________________________________________
css-discuss [css-d@css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
