Bug#872944: www.debian.org: Debian Policy Manual not fully published

Samuel Bronson <[email protected]>
Newsgroups gmane.linux.debian.devel.www
Message-ID <87pmlr46wm.fsf__5123.38977293751$1649452526$gmane$org@DESKTOP-5JD7O8D.localdomain>
Russ Allbery <[email protected]> writes:

> That said, introducing Javascript for the first time does feel like a
> large-ish step, and the reluctance also makes sense.  I'm not sure the
> search functionality really adds much.  (I haven't checked to confirm that
> is the only thing in the Sphinx output that uses Javascript, and that it's
> not used for something more useful like responsive design on mobile
> browsers, but maybe Sean has.)

I would be more inclined to agree if there was actually a single-page
HTML version.

Also, it looks like sphinx upstream is refactoring their javascript so
that all references to third-party javascript (underscore.js and
jquery.js) will be confined to _sphinx_javascript_frameworks_compat.js
-- see <https://github.com/sphinx-doc/sphinx/pull/10028>, merged as
<https://github.com/sphinx-doc/sphinx/commit/3b01fbe2adf3077cad5c2cf345c6d000d429d7ac>
on the 5.x branch.

Once those changes hit sid and debian-policy gets rebuilt and deployed
on debian.org, we should just have:

  * 404s for underscore.js and jquery.js

  * an uncaught ReferenceError in
    _sphinx_javascript_frameworks_compat.js

but doctools.js and searchtools.js and the search box should be fully
functional.

(The cronscript seems to handle the files symlinked in from
libjs-sphinxdoc just fine -- it only seems to have trouble when the
files shipped in libjs-sphinxdoc are *also* symlinks.)
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.