Hacker News new | past | comments | ask | show | jobs | submit login

After getting tired of scrolling (which reminded me of this http://joshworth.com/dev/pixelspace/pixelspace_solarsystem.h... where you scroll through vast distances to appreciate how far apart things in our solar system are) and noticing the huge headings separated by large vertical whitespace, I had an idea: since the headings are so huge, I could just zoom way out and see and read all the headings!

Unfortunately, the page outsmarted me and as I zoomed out, it somehow figured out I was doing this and increased the font size so it's the same size it was at 72 points when I was at 100% zoom.

Well, all right web designer. You "win". The amount of effort you put into defeating my efforts to read your content is astounding.




The amount of work is simple:

h1 { font-size: 5vw; }

The `vw` units are relative to the page width.

You would rather have to press the right arrow key 50 times? I find it to be a whole lot faster to scroll quickly through content rather than forcing me to click through every single damn slide.

EDIT: It is interesting that the vw/vh units don't take zoom into effect, I hadn't thought of that. Interesting.


actually, yes. Compared to scrolling football fields to get to the next item, a one-push interaction would be better.


Scanning through the content (going from slide 5 to slide 20) is far faster with scrolling, at least with Apple's trackpad and OS X's scrolling inertia. Maybe it doesn't work as well on other devices.

But it is useful to walk through each slide with a keypress, so I'll probably add that feature as well. I want both.


no, I'd like the text to get smaller when I zoom out. Why else would I or anyone zoom out!


I hate to pile on, but I also find this incredibly hard to read. The problem is that the precision with scrolling one "slide" down is very hard to get the same every time. Clicking a right arrow guarantees one click, one slide, whereas with this UX I'm constantly scrolling, then reading, then scrolling, then reading, and it's enough to make me not want to read the content.

I'm normally not a UX pedant, either.



It's not actually figuring anything out. The header is specified in vw units, which are relative to the size of the viewport.


For a text article, that's just bad design.


I feel like this is a misbehavior in browsers' zoom function, though the effect is the same. Does anyone know if the standard actually requires this quirk?




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: