> Did you try some custom css to solve the problem just with span? Yeah. I couldn’t figure out any way to truncate a span.
> On Mar 15, 2018, at 2:59 PM, Carlos Rovira <[email protected]> wrote: > > Maybe in Basic have sense to be span, but in Express, Jewel can be other > thing. A div seems more like a "container" to me, but we're using divs to > handle textfields, so maybe it would be ok with labels. > Did you try some custom css to solve the problem just with span? > > 2018-03-15 13:34 GMT+01:00 Harbs <[email protected]>: > >> Gotcha. FWIW, we now have the HTML element component set which more thinly >> wraps HTML elements. >> >> I can’t think of any reason why Label would be better as a span than a >> div. It seems to me that simply using div instead of span would make Label >> more versatile. Am I missing something? >> >>> On Mar 15, 2018, at 2:30 PM, Peter Ent <[email protected]> wrote: >>> >>> Label was one of the very first components and the idea was minimalism. >>> Button was <button> and TextInput was <input type="text"> and Label was >>> <span>. >>> >>> I'm wondering if we should have NativeButton, NativeLabel, etc. which >>> would be these minimal elements and have others that are <div> wrapping. >>> For instance, ImageAndTextButton is a <button><img src="goo.jpg">Label >>> Here</button> which works but the alignment is weird so maybe >>> ImageAndTextButton should be a <div><img>Text</div> which can be aligned >>> and styled better. >>> >>> Anyway, that's the reason: simplicity. >>> >>> ‹peter >>> >>> On 3/15/18, 7:51 AM, "Harbs" <[email protected]> wrote: >>> >>>> Is there a reason that the element type of Basic Label is span? >>>> >>>> I tried adding a łTextOverflow˛ bead to a Label and it does not seem to >>>> work because spans donąt really have a working width. Switching the >>>> element type to div seems to make it work. >>>> >>>> Harbs >>> >> >> > > > -- > Carlos Rovira > http://about.me/carlosrovira
