All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@amd.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2 2/2] doc: give full width to NIC overview page
Date: Wed, 31 Jul 2024 17:56:08 +0200	[thread overview]
Message-ID: <12218392.zAa99ISigo@thomas> (raw)
In-Reply-To: <1929151.GKX7oQKdZx@thomas>

31/07/2024 14:43, Thomas Monjalon:
> 31/07/2024 13:29, Ferruh Yigit:
> > On 7/31/2024 9:31 AM, Thomas Monjalon wrote:
> > > The wide tables in the NIC overview exceed the normal page width
> > > because of the large number of drivers.
> > > 
> > > A CSS trick is added to allow displaying this page in the full width
> > > of the browser window.
> > > 
> > > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> > >
> > 
> > This makes the feature table wider, so all table can fit, and scroll bar
> > below the table is gone, this is good.
> > 
> > But also it makes all paragraphs and 'Note' boxes in that page fill all
> > the screen, and with a wide screen this becomes a long box through end
> > of the screen and personally I think doesn't look nice.
> > 
> > Instead of making it full screen, is there are way to make it fixed
> > size, but larger than previous so that table still can expand fully?
> 
> We may try to restrict non-table containers, but then it will be less generic.
> I mean this solution could apply to any large page today.
> 
> We may try to force the width of <p> and <ul>.

I've found another trick to let only tables overflow.
I'll send a v3 and will apply quickly.




  reply	other threads:[~2024-07-31 15:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-21  9:15 [PATCH 0/2] custom doc styling Thomas Monjalon
2024-07-21  9:15 ` [PATCH 1/2] doc: copy custom CSS on guides build Thomas Monjalon
2024-07-21  9:15 ` [PATCH 2/2] doc: give full width to NIC overview page Thomas Monjalon
2024-07-31  8:31 ` [PATCH v2 0/2] custom doc styling Thomas Monjalon
2024-07-31  8:31   ` [PATCH v2 1/2] doc: copy custom CSS on guides build Thomas Monjalon
2024-07-31 11:25     ` Ferruh Yigit
2024-07-31  8:31   ` [PATCH v2 2/2] doc: give full width to NIC overview page Thomas Monjalon
2024-07-31 11:29     ` Ferruh Yigit
2024-07-31 12:43       ` Thomas Monjalon
2024-07-31 15:56         ` Thomas Monjalon [this message]
2024-07-31 15:57 ` [PATCH v3 0/2] custom doc styling Thomas Monjalon
2024-07-31 15:57   ` [PATCH v3 1/2] doc: copy custom CSS on guides build Thomas Monjalon
2024-07-31 15:57   ` [PATCH v3 2/2] doc: give full width to NIC overview page Thomas Monjalon
2024-07-31 16:17     ` Ferruh Yigit
2024-07-31 16:21       ` Thomas Monjalon
2024-07-31 16:22   ` [PATCH v3 0/2] custom doc styling Thomas Monjalon
2024-07-31 16:38     ` Ferruh Yigit

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=12218392.zAa99ISigo@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.