Re: New web site

On Thu, May 21, 2026 at 2:42 PM Nicolas Giard <[email protected]> wrote:
>
> There is no rationale for blocking javascript on the rfc-editor.org website (or ietf websites in general).
> Absolutely zero third-party scripts or resources are being loaded. We even self-host our fonts instead of using Google Fonts.

My understanding of the issue is, some folks do not want to use
non-free software needed for Javascript nowadays.  I guess one of the
root causes is, there's no [high quality?] free software
implementation of a Javascript engine.  I don't think origins and
cross-origin workarounds make a difference to the folks who want to
use free software.

See, for example, "The Free JavaScript campaign ",
<https://www.fsf.org/campaigns/freejs/>.

> One of the main goals of the new site was to reduce reliance on serving content from the server.
> This is achieved using SPA (Single Page Application), prefetching / dynamic resource fetch and as-you-type search.
> All of these require javascript to work.
>
> We use server pre-rendering so that you can still access content without javascript / accessibility / SEO, but don't expect dynamic features like search to work.
>
> It's debatable whether disabling JavaScript on certain websites is the right thing to do, but assuming all websites will fully work without it in 2026 is an unrealistic and dated expectation.
> The same will apply to other IETF websites over time as they get upgraded to newer technologies.

Jeff