Bug 1923272 Comment 3 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Ah, so the overflowing side here (in both Chrome and Firefox) comes from `white-space: nowrap` on the span that's wrapping the `November 15, 2023` text, specifically this rule:
```css
.scSearchSearch_results_listSearch_resultYoutubepreviewlabel-container {
    white-space: nowrap;
}
```

In Chrome,  the min-content contribution for that element will be the width of that full date.  If I remove that, then Chrome doesn't overflow beyond the black border anymore.

In Firefox, something similar happens, but the interesting differnece is that Chrome sees a linebreak opportunity *between the view-count and the date*, whereas we do not, so we end up thinking the whole `335K views November 15, 2023` string is unbreakable.
Ah, so the overflowing side here (in both Chrome and Firefox) comes from `white-space: nowrap` on the span that's wrapping the `November 15, 2023` text, specifically this rule:
```css
.scSearchSearch_results_listSearch_resultYoutubepreviewlabel-container {
    white-space: nowrap;
}
```

In Chrome,  the min-content contribution for that element will be the width of that full date.  If I remove that, then Chrome doesn't overflow beyond the black border anymore.

In Firefox, something similar happens, but the interesting differnece is that Chrome sees a linebreak opportunity *between the view-count and the date*, whereas we do not, so we end up thinking the whole `335K views November 15, 2023` string is unbreakable, which gives us a much larger min-content intrinsic-width contribution.

Back to Bug 1923272 Comment 3