All the more reason I advocate for semantic class names or HTML microdata & CSS variables to help those that want or need to create userStyles. It is a shame so many folks moved to generated classes or purely utility classes to give us less selectors to grab onto for styling or scripting or scraping.
Eric points out that there is no way to make the text truncated by text-overflow: ellipsis visible. Once it’s gone, it’s gone (although screen readers seem to announce it). It’s practically lost data.
Apart from using a screen reader, there are two other ways a user can view the elided text:
selecting the whole paragraph (either by dragging or triple-clicking), copying the selected text, then pasting the text somewhere such as the URL bar where it is visible
inspecting the element using the browser’s dev tools
I have done both of these in the past. However, I agree with the basic ideas that having to do either of those makes for a bad experience and that most users will be unable to view the elided text.
I myself have a number of userstyles that don’t do anything except fix sites that behave poorly in limited screen space environments.
All the more reason I advocate for semantic class names or HTML microdata & CSS variables to help those that want or need to create userStyles. It is a shame so many folks moved to generated classes or purely utility classes to give us less selectors to grab onto for styling or scripting or scraping.
generated classes are the worst
expecially since you then end up having to use data- attributes to reinvent ids in order to do ui tests.
We still do this typically with an additional tooltip or HTML title attribute defined
Apart from using a screen reader, there are two other ways a user can view the elided text:
I have done both of these in the past. However, I agree with the basic ideas that having to do either of those makes for a bad experience and that most users will be unable to view the elided text.