Control the number of questions per page - Meta

TopAnswers Meta

Top Answer

Jack Douglas

We've released an experimental control for this.

Please be aware that TopAnswers does quite a lot of rendering work client-side for the question list so YMMV at 100/page.

comments

transcript

Jack Douglas replying to GreenDragon

that's because we don't want to add a cookie until someone has logged on and seen our cookie notice. We could allow it to be changed and just not stick, but unregistered users aren't likely to be on the home page browsing often we think

GreenDragon

The control is only visible for logged user. Does it done for purpose?

Jack Douglas replying to FoggyFinder

good point, let's grey it out or something

FoggyFinder

I just didn't expect that "next" button is visible in case when there are no more pages ahead

FoggyFinder

oh, I got it

FoggyFinder

![_25P.png](/image?hash=e212a83f408287f3b198d5f60a98df17d2dde78e5da71d27d52d9e49cf14df7b)

FoggyFinder replying to Jack Douglas

![_100.jpg](/image?hash=322702cf29c6831bc7fac32f3283edb334434096730c23ee989bfa6f192336f2)

FoggyFinder

nope

Jack Douglas replying to FoggyFinder

You mean it is overlaying — are you on mobile?

FoggyFinder

Only `10 Q per page` option allows user see last page button

Jack Douglas

(at the cost of being less powerful of course)

Jack Douglas

but we are suing Katex rather than mathjax which can reduce the reflow problems

Jack Douglas replying to Anush

yes, both here and on SO

Anush

I may be out of date https://meta.mathoverflow.net/questions/2360/can-we-replace-client-side-mathjax-with-server-side-mathjax

Anush

the mathjax is all rendered client-side isn't it?

Anush

oh I see

Jack Douglas replying to Anush

SO render (mainly) server-side, we render 100% client-side, so the concern is putting too much burden on the client (especially mobile) device.

Anush

is this because on SO the rendering is done client side?

Jack Douglas

what with all the rendered markdown in answer summaries etc

Jack Douglas

though we do have to bear in mind that displaying questions isn't as cheap here as (say) on SO

Jack Douglas replying to Anush

we are pondering how to do the UI for this, feel free to make suggestions

Jack Douglas replying to Anush

of course we don't know how high your screen is, but I think 25 should cover most cases

Anush

In general, it makes sense to not load anything that the user can't see if you can avoid it.

samcarter replying to Jack Douglas

Cool, I'm looking forward to test this!

Jack Douglas replying to samcarter

this may be more to do with the number of chat messages — we will find out fairly soon as we are planning to reduce the number loaded with the page to 25 from 100 (and add a 'show more' button)

Monica replying to samcarter

That's a good point.  I hadn't realized the sight was heavyweight enough to affect load time on slower networks.

samcarter replying to Monica

I would prefre if a fixed number stays small, the site already takes a long time to load using a mobil  connection.

Anush

it's normally better to give options, such as 25, 50, 100

Monica

And/or maybe just increase that fixed number?

1 Answer