search

Debian / debiman

debiman generates a static manpage HTML repository out of a Debian archive
Apache License 2.0
186 stars 46 forks source link

Some manpages are incomplete / cut off #102

Open dosimple opened 6 years ago

dosimple commented 6 years ago

Like here: https://manpages.debian.org/stretch/dash/sh.1.en.html

The page only half covers until the section "Shell Patterns"and rest is missing.

stapelberg commented 6 years ago

We’ve had a similar report recently: https://github.com/Debian/debiman/issues/100

I still cannot reproduce the issue.

Which browser are you using? Can you enable the developer tools and tell me which IP address you’re hitting?

dosimple commented 6 years ago

Now the dash manpage works. But wget doesn't. My browser is firefox 59.0.1. But I seem to be getting the complete page content and it may just be a firefox bug.

The IP address I'm hitting is 128.31.0.62.

Screenshot

stapelberg commented 6 years ago

I can observe the following in Firefox 58: pressing C-l to get the page from cache makes it show up completely, and disabling the cache makes it not show up competely.

Seems like a Firefox bug to me. Can you report it in the Firefox bug tracker please?

dosimple commented 6 years ago

The issue is reported to mozilla.

Rondom commented 6 years ago

@dosimple Can you provide a link to their Bugzilla?

dosimple commented 6 years ago

Sorry, I can not find the link. I might have used their bug reporting tool outside of their Bugzilla. I followed "Report an issue with a web site that I use" at https://bugzilla.mozilla.org/enter_bug.cgi

stapelberg commented 2 years ago

I have recently been seeing this with Chrome as well.

The symptom is that the page is cut off in the browser, but interestingly enough the full page shows up in the developer tools network tab:

debiman-bug

Refreshing the page always seems to help.

This happens on two separate instances of debiman that use different static file serving stacks (one using Apache, the other one using nginx behind cloudflare), so I think the problem is client-side, not server-side.

Perhaps we’re triggering some sort of CSS bug? Not really sure how to go about this, or how to reliably reproduce it even :-/

stapelberg commented 2 years ago

Let’s see if perhaps https://salsa.debian.org/manpages-team/debian-assets/-/commit/6fd93402ad7b9acbb5a649be5b4570d2339d6b62 helps (removing JavaScript related to font loading). It’ll be a while before that will be live on manpages.debian.org.