Django documentation doesn't show correctly in any browser

[Some Developer]

I know this isn't strictly speaking a Django dev topic but since the
developers are the ones who changed the Django documentation theme /
appearance they should probably be made aware of the problem.

http://imgur.com/FtEpcdy
http://imgur.com/1ON8xxs
http://imgur.com/C6G0DfI

Above are some screenshots of what I see when I go to visit the Django
documentation. This happens on all browsers I have available (latest
Google Chrome, latest Firefox and Opera beta). I'm running on Arch Linux
and up until the recent documentation change I have never had a problem
with the Django docs or any other website for that matter.

I've checked the Google dev console and Firebug for information but
there are no errors, I completely cleared the cache and restarted the
browser which didn't help. I've completely disabled web fonts in Firefox
still no luck at all. Something must have been done in the recent
documentation overhaul which has broken something somewhere (have to
admit to being somewhat annoyed at the change - if it ain't broke don't
fix it).

As far as things stand at the moment the Django documentation is
completely and utterly unusable.

Any suggestions? I'm pretty sure I can't be the only one who is having
issues.

[Daniele Procida]

On Tue, Jan 13, 2015, Some Developer <someukd...@gmail.com> wrote:

>Any suggestions? I'm pretty sure I can't be the only one who is having
>issues.

It's not looking like that for me, no idea what's happening for you.

Daniele

[Aymeric Augustin]

Hi Some Developer,

On 13 janv. 2015, at 20:15, Some Developer <someukd...@gmail.com> wrote:

> Any suggestions?

Until this gets resolved, you can use http://django.readthedocs.org/en/latest/
which still has the previous CSS (for the time being).

> I'm pretty sure I can't be the only one who is having issues.

Well, there are 10k subscribers to this list. Who else is seing this?

--
Aymeric.

[patrick91]

On Tuesday, January 13, 2015 at 8:15:40 PM UTC+1, Some Developer wrote:

I know this isn't strictly speaking a Django dev topic but since the
developers are the ones who changed the Django documentation theme /
appearance they should probably be made aware of the problem.

http://imgur.com/FtEpcdy

http://imgur.com/1ON8xxs
http://imgur.com/C6G0DfI

I cannot see any of these on my mac, I'll see if I have any linux machine where I can see if I can reproduce.

Meanwhile, can you tell us if you have the same styles for the code tags? https://up.kibakoapp.com/AaFwwhccdE

Also try to play with font-family. Maybe it is a font issue, even if you have disabled webfonts, there can be something wrong with fonts in your system. 

[Raphael Michel]

Am Tue, 13 Jan 2015 20:36:45 +0100
schrieb Aymeric Augustin <aymeric....@polytechnique.org>:

> Well, there are 10k subscribers to this list. Who else is seing this?

I don't, and I run pretty much the same configuration (Chrome on Arch
Linux on multiple computers). I think it pretty obviously is an issue
with the Fira Mono webfont, so maybe some weird font cache
configuration issues. Does this web page work for you?
https://mozilla.github.io/Fira/

Best regards,
Raphael

[David Graves]

Doesn't look that way to me in Fedora or Chrome on Linux

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/324d9735-4569-485c-8d20-9f22194576cb%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Jannis Leidel]

Hi Some Developer,

This has probably something to do with me disabling ligatures for code snippets which I tested on various browsers on different platforms before deploying (using browserstack.com).

I've opened a ticket in the website's repo here: https://github.com/django/djangoproject.com/issues/310 to track the issue.

Jannis

[Jannis Leidel]

> On 13 Jan 2015, at 20:15, Some Developer <someukd...@gmail.com> wrote:
>

I just deployed a potential fix, can you try again?

Jannis

[Some Developer]

On 13/01/15 23:10, Jannis Leidel wrote:
>
> I just deployed a potential fix, can you try again?
>
> Jannis
>

Same issue I'm afraid.

[Some Developer]

Some of it works and some of it doesn't.

One of the sections in the Light category doesn't show anything. Nothing
in Medium, Bold or Regular works.

[Some Developer]

On 13/01/15 19:48, patrick91 wrote:

> I cannot see any of these on my mac, I'll see if I have any linux
> machine where I can see if I can reproduce.
>
> Meanwhile, can you tell us if you have the same styles for the code
> tags? https://up.kibakoapp.com/AaFwwhccdE
> Also try to play with font-family. Maybe it is a font issue, even if you
> have disabled webfonts, there can be something wrong with fonts in your
> system.
>

If I manually delete the "Fira Mono" font from the font-family using the
Google Chrome dev tools then the page works as expected. So yeah seems
to be a web font issue.

[Jannis Leidel]

Sigh, yeah, the package probably ships with an old version of the font that is somehow corrupted and is still favored by the browser. FWIW others have had the same problems: https://github.com/rust-lang/rust/issues/19257#issuecomment-66950412

The underlying problem is that we use Google's web fonts hosting for serving the Fira Mono font that has a local() statement for both styles (http://fonts.googleapis.com/css?family=Fira+Mono:400,700) which means it'll try the local version first, which kinda defeats the purpose with Fira Mono anyways, unless you're running Firefox OS for some reason :)

The font has also received quite a few updates since it was added to Google's hosting service, so I just deployed our own version to the site and hope that fixes your issue. Can you double-check if it works now?

Jannis

[Some Developer]

Working fine now. Thanks!

[Jannis Leidel]

> On 14 Jan 2015, at 02:11, Some Developer <someukd...@gmail.com> wrote:
>
> Working fine now. Thanks!

\o/

Jannis