![]() ![]() Other issues with complex and international text that occur to me: ![]() However, this won't necessarily Just Work if any string can be specified for the ellipsis, as in earlier versions of CSS3 Text. the ellipsis will always appear at the end of the line (right for left-to-right or left for right-to-left) just as end-of-paragraph punctuation does even when the last line ends in text in the other direction. That's the most important thing someone can do to move this along.įor bidi I think it's reasonable to follow the natural bidi reordering of the ellipsed text, i.e. It will help get text-overflow added to CSS3 too. This information needs to be gathered for different browsers and the most sensible common behaviour agreed on. what happens if there's replaced content near the end of the line, say an image? Do you get the ellipsis or does the image overflow? If an ellipsis, where does the ellipsis go?Īnd more things that I haven't thought of yet :-). Where only "english HEB" fits, where should the ellipsis go? English followed by Hebrew? Can bidi text make the ellipsis appear at the beginning of the line? I'm particuarly interested in the case of an LTR word followed by an RTL word that doesn't fit, e.g. ![]() a line of Hebrew? What about mixed bidi text e.g. how does it work with text-align:right, does the ellipsis go on the left? does text-overflow inherit by default or not? does it come from the text or does it come from the element with text-overflow on it? what style the ellipsis has (font, color, etc). Among other things, it needs to describe: And I don't think anyone could seriously complain, if it's implemented as -moz-text-overflow while CSS3-Text is still a Working Draft.Ĭould a developer who's more familiar with the inner workings of take a look and see if it'd be possible to directly transfer its behavior onto HTML elements with -moz-text-overflow: ellipsis? I'm sure you'd have a lot of grateful developers if this could be done and patched for Firefox 2. However, at least until a proper implementation can be developed, it could serve as a functional hack to fill in the gap, and I'm certain it would fulfill the needs of most developers who need a workaround for Gecko. I'm not sure how accurately the behavior of follows that of the CSS3 text-overflow proposal. (menus, bookmarks, tabs, etc.) I've tried to force this behavior upon HTML elements, via Mozilla-specific CSS selectors, with no success to date. I'd like to point out that Gecko already has this ability built into XUL, through crop="right" or crop="end" for XUL elements that serve a purpose identical to that of. I've run into this several times in development, particularly concerning displaying longer messages within tables where the message has an action (mouseover, click) that will display the full text as a tooltip or in a popup window. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |