From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from ms.lwn.net (ms.lwn.net [45.79.88.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A2EEB2459EA; Wed, 25 Mar 2026 19:04:24 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=45.79.88.28 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774465465; cv=none; b=f6hpB1OlOBCTzBZlooX+79/nSCsIU5vnASe1Z+aX31FTtSTvEZpcxpJIWZl+f0ooGM7LUm7oBCh2SvGnhCiXHvJHN1qFFKi2U9EVsbQxNY8afO66nObUV9fdwqTrl3o93hrPnhM5VxnRBohk2Z+YePBfT+2lAkQsZv0/v+Q+ENM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774465465; c=relaxed/simple; bh=KzFjKZL5Y/xjnPsqDiVITklRAUuBd1vwFEo1W4NVk4o=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=nfqMr3EL8nFWXYFRU6T/hVGoTMIMx3xYA9fYxmLGKQKS99Z1oNqZg6NR/mqlh8+f4bhaWuFdjNsaVix7a4J6zzh2R3Kj0F527DyzUDmbM7TlG0+6gR8NgpH5QmeE1o8WWdnaPDpax2r03bZErk6xCVrhdmyNvhCQlQUDDEah+/4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lwn.net; spf=pass smtp.mailfrom=lwn.net; dkim=pass (2048-bit key) header.d=lwn.net header.i=@lwn.net header.b=oj0WUIJ+; arc=none smtp.client-ip=45.79.88.28 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lwn.net Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lwn.net Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=lwn.net header.i=@lwn.net header.b="oj0WUIJ+" DKIM-Filter: OpenDKIM Filter v2.11.0 ms.lwn.net 0C7AB40C6F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lwn.net; s=20201203; t=1774465464; bh=D4OaDQstftoam8u56Pjm1BcMbaptydxU9Nl59QxCmbw=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=oj0WUIJ+UC1BIlKc8vb+z0iUvEc88om89EBRjmfv7Rhe7TkNxhbeCaOHmfRZRpktp Tdbn6JjjREcdKK9jSnCZ0KS353cGNUkMLFI7I8eohHdmzQ3+wVTD92IfwXuLceqsM5 mYv/968T+5BHvJr5bn9mFZnOyhlmJJGldh/JGiUuuAG2NnTK1fx6x7Exw9KoF+pXwf XEma1U4yH0DlwwMW8NWKeK2XqNrEHs4WZeA3ozsm4hJS/pZiBaV54LlwnDGlO1F0Ni 0iO9sCmGNROR5tNlXdZJq+RWMJfzIDWzo1hicp2LZPR20+UO/qWnN/YYeY/J/cs41S 9Lbc8F3FM0Jmg== Received: from localhost (unknown [IPv6:2601:280:4600:27b::1fe]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id 0C7AB40C6F; Wed, 25 Mar 2026 19:04:23 +0000 (UTC) From: Jonathan Corbet To: Rito Rhymes , linux-doc@vger.kernel.org Cc: Shuah Khan , linux-kernel@vger.kernel.org, rdunlap@infradead.org, Rito Rhymes Subject: Re: [PATCH v3] docs: allow long unbroken headings to wrap and prevent overflow In-Reply-To: <20260323153024.32317-1-rito@ritovision.com> References: <20260321144855.30429-1-rito@ritovision.com> <20260323153024.32317-1-rito@ritovision.com> Date: Wed, 25 Mar 2026 13:04:23 -0600 Message-ID: <87h5q3g288.fsf@trenco.lwn.net> Precedence: bulk X-Mailing-List: linux-doc@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain Rito Rhymes writes: > Some documentation pages contain long headings with unbroken strings > that can exceed the content width and cause page-wide horizontal scroll > overflow. > > Allow headings to wrap when needed so they stay within the content > column and do not break page layout. > > Browsers do not treat underscores as natural wrap points, so some > code-style headings may still wrap awkwardly. That trade-off is > preferable to allowing horizontal scroll overflow, since headings > should remain immediately visible rather than partly hidden behind > horizontal scrolling. > > Examples: > https://docs.kernel.org/6.15/userspace-api/gpio/gpio-v2-line-get-values-ioctl.html > https://docs.kernel.org/6.15/userspace-api/sysfs-platform_profile.html > > Signed-off-by: Rito Rhymes > Assisted-by: Codex:GPT-5.4 I do not see the problem you are referring to here; headings wrap just fine for me using both Firefox and Chrome. (Firefox arguably does a little better since it wraps at "/", but that is what also make it turn "I/O into "I/ O." In what environment are you seeing this problem? Thanks, jon