From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: UX Bug in Sphinx HTML Layout for Programming Guide
	(and maybe other guides?)
Date: Sat, 16 Jan 2016 09:19:27 +0100
Message-ID: <9629146.dpmWFHkhSD@xps13>
References: <20160113172629.GA9710@mhcomputing.net>
 <B27915DBBA3421428155699D51E4CFE202428FA9@IRSMSX103.ger.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: dev@dpdk.org
To: "Mcnamara, John" <john.mcnamara@intel.com>,
 Matthew Hall <mhall@mhcomputing.net>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-wm0-f44.google.com (mail-wm0-f44.google.com [74.125.82.44])
 by dpdk.org (Postfix) with ESMTP id 652188E6A
 for <dev@dpdk.org>; Sat, 16 Jan 2016 09:20:49 +0100 (CET)
Received: by mail-wm0-f44.google.com with SMTP id u188so48516520wmu.1
 for <dev@dpdk.org>; Sat, 16 Jan 2016 00:20:49 -0800 (PST)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE202428FA9@IRSMSX103.ger.corp.intel.com>
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

2016-01-15 16:23, Mcnamara, John:
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Matthew Hall
> > Sent: Wednesday, January 13, 2016 5:26 PM
> > To: dev@dpdk.org
> > Subject: [dpdk-dev] UX Bug in Sphinx HTML Layout for Programming Guide
> > (and maybe other guides?)
> > 
> > When you go to this link:
> > 
> > http://dpdk.org/doc/guides/prog_guide/perf_opt_guidelines.html
> > 
> > There is a bug in the Sphinx layout, where the subchapters of a chapter
> > are invisible even after the chapter is clicked.
> 
> Hi Thomas,
> 
> I found the issue causing this and I'll submit a patch shortly.
> 
> If possible could you apply it a copy of the 2.2 code and rebuild the online docs.

Yes, done.
Thanks guys