text-overflow

This means not having a random floating ellipsis at the end of the div, and it means we can't use text-overflow.

Pair this with text-overflow and with ~ 50 lines of CSS and some very basic html you can achieve wonders.

At least with `text-overflow: ellipsis` if the user-generated label _doesn't_ overflow, it doesn't get clipped.

Or barring that, a max-width for the title with a text-overflow set to hidden?

Just like text-overflow:ellipsis (which was introduced with IE6) is now part of CSS3.

Good examples for that are things like JavaScript, XHR, or text-overflow:ellipsis.

So, it's kinda like applauding Microsoft for supporting text-overflow:ellipsis first.

The text-overflow one really gets me every time...

Man I never knew about text-overflow: ellipsis.

Many developers were achieving the same result in firefox 3.6 and earlier using an XUL hack - but in FF4, the ability to do that XUL hack was removed for (valid) security reasons - but without addressing the text-overflow: ellipsis issue for which they'd had an open bug tracker entry for about 5 years.

I recently made a component representing an attached file, where the flex items in its layout were: [icon] [filename] [button] To get long filenames to not force their container to the full length of the string, so they could be truncated by text-overflow: ellipsis, I needed to put min-width: 0; on the flex item containing the filename.

- `ems` as units relative to the parent instead of the root font size - making flex-box alignment props the most confusing thing ever - `display: none` to exclude elements, instead of an `exclude` prop, colliding with the display model - `position: fixed` not making sense - `text-overflow: ellipsis` not working in most cases where you'd want it to I could go on for a while.