Are we agreeing to follow the prototype that I had made for this last year? Here are the demos once more:

• English
• Bengali
• Hebrew
• Hindi

It fills up the div word by word and it thus not very performant. @werdna and @AndyRussG could you please take a look at the code and tell me if its alright to migrate it to the extension.

@JKatzWMF @Jdlrobson, mind taking a look at this?

@Prtksxna can you confirm the user requirements that are guiding this? In T132522 I highlight that any sentence cut-off should result in an ellipse.

I am not sure how that is connected to the additional 2 requirements in this ticket. Can you point out areas where the current solution does not lead to awkward-use of the space or certain scripts look awkward?

Right now Hovercards does not have a character limit, it only has a geometric limit through CSS and it hides the extra text (lets it overflow, and doesn't display it). We do this because setting a character limit is hard when you are supporting multiple scripts. For example, in Devanagari 'चुंबक' is five characters, but 'चबक' is three, which makes it hard to set script specific character limits too.

This makes it non-trivial to add ellipses at the end of the sentence. I am not sure if I answered your question , but I hope the explanation helps .

@Prtksxna thanks for that extra info! I wasn't aware of the different script properties. Why aren't words cut-off mid word then? If we can identify a space, surely we can place ellipses at the end of that space?

Words aren't cut off mid sentence because we don't let the word wrap break the words. We don't exactly identify the space character, we just tell the browser that we have a certain amount of space and that it should fill it up, and then we cut vertically from that space and display it.

To see this in action, you can increase the height of .mwe-popups.mwe-popups-is-tall .mwe-popups-extract to lets say 155px. You'll be able to see the top half of the next sentence.

I believe @Nirzar would need to provide a mock, then it would be a matter of technical implementation. I believe multiline text block ellipsis is available in some browsers and will eventually be more generally available. It seems like that would require less work than building a clamping technique.

@dr0ptp4kt, @Nirzar - double-checking that this should still be open?

@ovasileva, yes.

Can we use :after with … (U+2026)

or we used a horizontal gradient in related pages. that technique is super nice in such cases.

Is this the same as T132522: Do not cut preview off mid sentence without ellipses ? We had discussed this task during grooming, but I re-discovered T132522: Do not cut preview off mid sentence without ellipses when looking at the previously identified critical blockers.