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

Sam Whited <> Tue, 28 February 2017 20:41 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 08F471296D2 for <>; Tue, 28 Feb 2017 12:41:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.092
X-Spam-Status: No, score=-4.092 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=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] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)"
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id LN1FAWjB-_m1 for <>; Tue, 28 Feb 2017 12:41:01 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DDABC1296CB for <>; Tue, 28 Feb 2017 12:41:01 -0800 (PST)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 96DCFB81250; Tue, 28 Feb 2017 12:41:01 -0800 (PST)
Received: from localhost (localhost []) by (Postfix) with ESMTP id A76A9B81255 for <>; Tue, 28 Feb 2017 12:40:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id FQNE7BQ3mUuE for <>; Tue, 28 Feb 2017 12:40:54 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4002:c05::22f]) by (Postfix) with ESMTPS id 908E7B81250 for <>; Tue, 28 Feb 2017 12:40:54 -0800 (PST)
Received: by with SMTP id v200so17399609ywc.3 for <>; Tue, 28 Feb 2017 12:40:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=swgoo; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=wsTwA9B+AhoNx1oq1CtSFo0zsp34wphJyfU6Bqr+qcg=; b=Vh8gfoGk7h6RBgHo1xsTAOZbZ+EhAzjxwGzWMJkIdta+iiNEKU92wIppqGBTp9iAK/ bs8mTBs8s2ysDD55XQkdonlZaqQnnFavzL3bPcMiNRwa3akQltjYeidWQjveaoDGHO/a 1jYTr3n5SzPE7Y7JU9KESf08Y6rAVIz2FWhY0=
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:content-transfer-encoding; bh=wsTwA9B+AhoNx1oq1CtSFo0zsp34wphJyfU6Bqr+qcg=; b=pAeEHNUz+mfVGOUWuyDIGW79Ggd5xJyu02pekFhKO+tvSwmlWUcuYBLursGIjh8ZMq gf11+sKT9mSbSiJfOsq3hyrWHz1ZbczD0iCjhl1HrurlF8h76zs3Hlvpup7/8TuquJFa IkLXQNKsHA4+SbFvjimyeoJYApgjXL7W0tjT33KJ6UhJHUy+Nty8Z0lUuJ3UZSAaN/Dt QlIFVVY6thpiVhiyutxu97J+y9FkR3/vWsGIqvg8edhAAsQo2kbIoPfXJTNYaWMqWKKH N+PnwzDsTGrM94lsRe+4knaL4eXGP18Pj5slarLKD5Mulg9PwhpHdo1S5UVI2LCpw/E9 zS9w==
X-Gm-Message-State: AMke39mLZqpjT2eCL0V0VSrQzB+pkPIKQPIqEGTAhG7eJo/ey+1EVD5akcWjNRQgzGzkrMw+UKvg0zShGQcinA==
X-Received: by with SMTP id h39mr1637819ybj.110.1488314453464; Tue, 28 Feb 2017 12:40:53 -0800 (PST)
MIME-Version: 1.0
Received: by with HTTP; Tue, 28 Feb 2017 12:40:13 -0800 (PST)
X-Originating-IP: []
In-Reply-To: <>
References: <> <> <>
From: Sam Whited <>
Date: Tue, 28 Feb 2017 14:40:13 -0600
Message-ID: <>
To: "Andrew G. Malis" <>
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: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: "rfc-interest" <>

On Wed, Feb 22, 2017 at 7:19 AM, Andrew G. Malis <> wrote:
> I completely disagree regarding the TOC on small screens. I like that
> wherever I am in the document, I can open the TOC, refer to it, scroll it up
> and down, and then if I close it without clicking on a link, I’m back in the
> exact same place in the document.

Hi all,

I don't often comment on IETF related things, and I'm sure this has
been discussed to death, but I wanted to point out that this is
*always* a problem any time JavaScript based menues are used, and
though I agree that it's nice to be able to quickly get to the TOC
from anywhere, I don't think we should add this feature if JavaScript
has to be involved.

How many times have you gone to a site, moused over a menu, gotten a
JavaScript drop down, moved the mouse down onto it only to have the
menu dissapear before you could click anything? Or had it not work on
mobile? Or had it break on <your browser of choice> but not <your
friends browser of choice? With my XMPP Editor hat on: Even with the
tiny snippet of JavaScript we use at the XMPP Standards Foundation to
do syntax highlighting in XEPs is *constantly* broken due to small
edge cases; this can cause readability issues, but it's far less
important than a table of contents in documents used by people all
over the world in different contexts and environments.

I too love the idea of having a table of contents that doesn't require
me to scroll all the way up, and there very well may be a way to do
this in such a way that it will work everywhere, but in general I
suspect that it's going to be more trouble than it's worth for a
feature that isn't all that important in the end. Being able to see
the TOC is critical, being able to get to it quickly is just nice.
Since the usability of the TOC could be broken by this change (and
almots certainly will be for someone, no matter how many iterations we
do on the script), I really think we should ge rid of it (not that I'm
involved or really have any say; just my two cents).

Thanks for doing all this work on the new format; I'm really looking
forward to seeing it in the wild!


TL;DR — JavaScript menus always sound like a good idea, but then just
end up annoying half the people who want to read your document.
rfc-interest mailing list