3px too narrow
-
-
@greybeard Unless this is another bug report on the 3px thing itself, I'm missing the issue here.
-
-
@pie_flavor I think it's the fact that the "next page" button on the bottom page nav area is shunted downwards...
Edit:
-
Also, half-mobile mode is great!
-
@Greybeard
: WHY DO YOU HAVE A THREAD THAT HAS FOUR DIGIT PAGE NUMBERS!? LOCKING... WHAT!? YOUR MINUSCULE SERVER CAN'T HANDLE THE AWESOME POWER OF LOCKING? NO DISCOURSE FOR YOU!
-
This will be fixed in CSS5
-
Honestly, I have no good ideas on how to fix this sensibly.
Maybe reducing the amount of buttons there when the widths gets too low, but that'd have to be a JS thing since you can't do a pure CSS solution that deals with elements that are dynamically sized as those buttons are (even if you just knock down the number of buttons regardless you'd still hit the problem with a different theme / over 10k pages (
)).Yes, you could force a horizontal scrollbar on the page, but that's a pain. Or you could just make the page buttons scrollable, but that's resorting to JS again because I don't think anyone wants a browser scrollbar there... You could argue that it's mobile mode that mostly never shows scrollbars until you start moving stuff, but still, I don't like it...
-
@onyx that's the general problem of HTML: it's designed for high-level description of static webpages, but almost every website requires low-level control of dynamic elements, so everyone hacks around until the rules that make already simple things even simpler, stop fucking up your complicated design too much.
-
@onyx said in 3px too narrow:
Honestly, I have no good ideas on how to fix this sensibly.
Not use HTML as your presentation layer? Not completely change the layout and functionality of the page based on how wide the browser window is?
Just two little ideas there.
-
@blakeyrat said in 3px too narrow:
Not use HTML as your presentation layer?
That would be nice, but it's still kinda required for a web app...
@blakeyrat said in 3px too narrow:
Not completely change the layout and functionality of the page based on how wide the browser window is?
The thing is, this can happen on any resolution. Also, that part of the layout looks the same on any resolution if you use pagination instead of infiniscrolling, AFAIK.
-
What I find depressing is that @pie_flavor couldn’t even see it.
-
@onyx said in 3px too narrow:
Not use HTML as your presentation layer?
That would be nice, but it's still kinda required for a web app...
We could have an entire UI based on canvas. I think nobody had the time and crazyness required to do that yet, but it's possible.
-
@greybeard said in 3px too narrow:
What I find depressing is that @pie_flavor couldn’t even see it.
He thinks Discourse is bug free, though, so...
-
@sockpuppet7 said in 3px too narrow:
@onyx said in 3px too narrow:
Not use HTML as your presentation layer?
That would be nice, but it's still kinda required for a web app...
We could have an entire UI based on canvas. I think nobody had the time and crazyness required to do that yet, but it's possible.
It would definitely require less craziness than getting it working in HTML.
-
@gÄ…ska I correct myself, somebody already did that:
-
@greybeard said in 3px too narrow:
What I find depressing is that @pie_flavor couldn’t even see it.
I barely even notice the
anymore. It's just become business as usual, especially on mobile.
-
@sockpuppet7 said in 3px too narrow:
@onyx said in 3px too narrow:
Not use HTML as your presentation layer?
That would be nice, but it's still kinda required for a web app...
We could have an entire UI based on canvas. I think nobody had the time and crazyness required to do that yet, but it's possible.
CanvasBB here we come
