rustdoc: Long type names result in weird-looking documentation

[Andrewp2]

Crates with long type names result in a strange-looking error, see https://docs.rs/async-stripe/0.31.0/stripe/

I've tested this on Chrome and Firefox, and by building the docs locally from https://github.com/arlyon/async-stripe

I believe the text is rendering vertically due to long type names like https://docs.rs/async-stripe/0.31.0/stripe/enum.PaymentFlowsPrivatePaymentMethodsCardDetailsApiResourceEnterpriseFeaturesIncrementalAuthorizationIncrementalAuthorizationStatus.html which are auto-generated from OpenAPI.

Link to original issue arlyon/async-stripe#488

[Urgau]

The issue is related to the overflow-wrap: break-word rule which prevents breaking anywhere in the type name. Unfortunately using overflow-wrap: anywhere breaks core::arch.

We even have a comment about the weird behaviour in the code, not sure how to fix this.

rust/src/librustdoc/html/static/css/rustdoc.css

Lines 881 to 904 in befabbc

	/* In most contexts we use `overflow-wrap: anywhere` to ensure that we can wrap
	as much as needed on mobile (see
	tests/rustdoc-gui/type-declaration-overflow.goml for an example of why
	this matters). The `anywhere` value means:
	"Soft wrap opportunities introduced by the word break are considered when
	calculating min-content intrinsic sizes."
	https://developer.mozilla.org/en-US/docs/Web/CSS/overflow-wrap#values
	For table layouts, that becomes a problem: the browser tries to make each
	column as narrow as possible, and `overflow-wrap: anywhere` means it can do
	so by breaking words - even if some other column could be shrunk without
	breaking words! This shows up, for instance, in the `Structs` / `Modules` /
	`Functions` (etcetera) sections of a module page, and when a docblock
	contains a table.
	So, for table layouts, override the default with break-word, which does
	_not_ affect min-content intrinsic sizes.
	*/
	table,
	.item-table {
	overflow-wrap: break-word;
	}

[BradMarr]

@rustbot claim