Re: [rfc-i] Update on the CSS - second round

"Andrew G. Malis" <> Tue, 21 February 2017 22:34 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 48B2C129D6E for <>; Tue, 21 Feb 2017 14:34:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.087
X-Spam-Status: No, score=-4.087 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)"
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id zew7_O6SeC1n for <>; Tue, 21 Feb 2017 14:34:50 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8E7AB129D4B for <>; Tue, 21 Feb 2017 14:34:50 -0800 (PST)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 45F5AB81259; Tue, 21 Feb 2017 14:34:50 -0800 (PST)
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4FDCAB81253; Tue, 21 Feb 2017 14:34:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id pQUT7afQA_rI; Tue, 21 Feb 2017 14:34:45 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4003:c06::230]) by (Postfix) with ESMTPS id 2C6D0B81259; Tue, 21 Feb 2017 14:34:45 -0800 (PST)
Received: by with SMTP id 65so11893817oig.1; Tue, 21 Feb 2017 14:34:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=MuU3iP00AHNEN27poL8o4fxT6ZHZ9XgKAlPj88qLYc0=; b=NRItMvE6P/AgDOutWCrl1BmCxrR5i6XYN/hBvzfH5szjmfN2xIpLCPIDjgpfOxUBPr 6iEi+M7QR9QelJSxo0dCp+qKMJvEl03kLZMVh2Cge1far3iZQlLHNIYBcK06+PWeat6L oFMXLZQK+2sTzATyMsM2dY6XbghgfJOUq4Vxma7/QkjptYLkE+TQfNmnw6Fnn+oUAFnH goV056v7lLlchEUkzoUODEW5rR5YaN3hOwMW6Gu4xKCMlDHJRSl1yhkS1gJhsA+Ebhj4 f4QVySdUndSd4EmCkcQcnrvOh7pX5QOTJfQ025GEzqcxuaAP4Ln6XR7MsLsbloUqRE/G 191Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=MuU3iP00AHNEN27poL8o4fxT6ZHZ9XgKAlPj88qLYc0=; b=IlMehx0OJrRGd0xYlkbZzTSUd71fygqNE6w45hxF35RNIrr8jolSkRBxtwgha7tyyj UPFrgFQIzbJUePLlReXsSEdh0qCLMOyYwczpT3xXUl51StdfyGmGrVa7tRngbRGrX98z lKQEtn3t2tl2SU2Q3GOJD9CoySrOGm3cPcUknF2FtxVfMQgLXXxoCOgiahq1caCZWSL+ zJPWL9vsRO4U2T1YXs4s7uEQxB/Rbat7D0oMPNYJfNIaZ3X+bj8Up/qFLCTZ6kNvPqsQ edApsJi1YwuLjK0qMXyr6y19rErX+iOhma+eAnzg7zzVZ3O/Z9OTJEMTPEPvbwN8pBwL NJ9g==
X-Gm-Message-State: AMke39kVJuZHSKHZOuu659MA/vC/6ahsRXNThLhWW5ywCE1y6+f+K7S5hwehZEUEnnoJ0uOdCAj0NZ8ucpLPmQ==
X-Received: by with SMTP id e11mr15399853oif.57.1487716484619; Tue, 21 Feb 2017 14:34:44 -0800 (PST)
MIME-Version: 1.0
Received: by with HTTP; Tue, 21 Feb 2017 14:34:24 -0800 (PST)
In-Reply-To: <>
References: <> <>
From: "Andrew G. Malis" <>
Date: Tue, 21 Feb 2017 17:34:24 -0500
Message-ID: <>
To: Ted Lemon <>
Subject: Re: [rfc-i] Update on the CSS - second round
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
Cc: RFC Interest <>, "Heather Flanagan \(RFC Series Editor\)" <>
Content-Type: multipart/mixed; boundary="===============7798379382307791043=="
Sender: "rfc-interest" <>


The behavior may be browser-specific. In Firefox on a Mac, I found that
scrolling the TOC using the scroll bar or arrow keys would be completely
confined to the TOC. If I used two-finger scrolling, an initial scroll
would be confined to the TOC, even if I did a big flick to get to the end,
and I then had to do a completely separate scroll operation to start the
main text scrolling, with the cursor still in the TOC.


On Tue, Feb 21, 2017 at 10:21 AM, Ted Lemon <> wrote:

> One issue that I noticed when playing with sample 3 is that scrolling the
> table of contents starts scrolling the document when you get to the end.
>  This is a bit of a usability problem, but I don't know if there's a way to
> fix it in the CSS.   The reason it's a usability problem is that a single
> flick on the TOC gets you to the end, and the momentum carries over to the
> document, resulting in a substantial scroll of the document.   The two
> should be completely independent; otherwise, the utility of the TOC is
> limited, because I'm going to tend to shy away from using it for fear of
> losing my place in the document.
> _______________________________________________
> rfc-interest mailing list
rfc-interest mailing list