View Single Post
Old 07-05-2025, 08:18 PM   #27
RbnJrg
Wizard
RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.
 
Posts: 1,806
Karma: 8700631
Join Date: Mar 2013
Location: Rosario - Santa Fe - Argentina
Device: Kindle 4 NT
Quote:
Originally Posted by ElMiko View Post
Sorry, I wasn't clear with my question: is that how ereaders will treat it? For example, I know that with words that are longer than the screen width, some e-readers will break them automatically. I'm assuming (perhaps erroneously) those e-readers might treat "nowrap" strings similarly.
It's a bit difficult to explain. With "white-space: nowrap" ereaders in one page should show only the portion of text that fits within the screen width. Anything beyond that is carried over to the next page and overlaps the text that might otherwise be there. To avoid this overlap, the string is usually truncated with the following properties (both must apply):

Code:
.nw {
  white-space: nowrap;
  overflow: hidden;
  text-overflow: ellipsis;
}
Of course, of this way the string is truncated. If you want to see the whole string, then employ "overflow: auto" and "text-overflow: clip".

Last edited by RbnJrg; 07-05-2025 at 08:35 PM.
RbnJrg is offline   Reply With Quote