You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes, it's hard to read some articles, because easyrss seems to force the display of the text to fit exactly the screen width.
The issue appears often when an article contains a very long URL, like on this page:
Is it possible to apply CSS properties before displaying the articles ?
If yes, it could be interesting to use the hint given in this French speaking (sorry) article.
The idea is to ask the browser to display ellipsis when text is too large for the screen, with this CSS rule:
.contenta {
display: inline-block; /* Needed to be able to apply ellipsis method */overflow: hidden;
white-space: nowrap;
text-overflow: ellipsis;
vertical-align: bottom;
max-width:100%; /* Needed to rule that the text block can't be bigger than the parent container */
}
Do you think it is doable ?
It seems this issue come also when there's <pre> blocks:
Here I think we can't use this solution, because we'll loose some important information. What do you think ?
Hello,
Sometimes, it's hard to read some articles, because easyrss seems to force the display of the text to fit exactly the screen width.
The issue appears often when an article contains a very long URL, like on this page:
Is it possible to apply CSS properties before displaying the articles ?
If yes, it could be interesting to use the hint given in this French speaking (sorry) article.
The idea is to ask the browser to display ellipsis when text is too large for the screen, with this CSS rule:
Do you think it is doable ?
It seems this issue come also when there's
<pre>
blocks:Here I think we can't use this solution, because we'll loose some important information. What do you think ?
Best regards,
Trim
PS: For issue with urls, I think it happens often with this RSS feed: https://linuxfr.org/tags/agenda_du_libre/public.atom
For issue with
<pre>
it could happen often with this one (depending on the content of user requests): https://linuxfr.org/forums/programmation-c--2.atomThe text was updated successfully, but these errors were encountered: