Live data from Hacker News

Chonky Menu Re-Creation

nathanmanousos.com

51–60 of 97 posts

Re: Chonky Menu Re-Creation

#51
post #49
post #36

Feature Policy: Skipping unsupported feature name “accelerometer”. chonky-menu Feature Policy: Skipping unsupported feature name “autoplay”. chonky-menu Feature Policy: Skipping unsupported feature name “clipboard-write”. chonky-menu Feature Policy: Skipping unsupported feature name “encrypted-media”. chonky-menu Feature Policy: Skipping unsupported feature name “gyroscope”. chonky-menu Feature Policy: Skipping unsup…

Is my demo trying to access all that stuff??

Why else would I paste that?

Re: Chonky Menu Re-Creation

#52

Earlier quoted context omitted.

> The usability on a laptop goes out the window On a non-Apple trackpad, I'm sure. Apple / macOS has had "3 finger drag" for a good few years now. With it, there's no clicking involved: you put 3 fingers on your trackpad and move them and it's a drag operation. There's even a timeout / grace period before the drag is actually "committed". You can also flick any one of your 3 fingers and it will drag + move your curso…

Interesting, it's an accessibility feature that is not enabled by default. https://support.apple.com/en-us/HT204609

For some reason Apple puts the most basic stuff behind an accessibility option. For example, tab to next button in a system dialog is disabled by default.

Re: Chonky Menu Re-Creation

#53
It looks cool as hell (I particularly love the springy demo I'm a sucker for spring physics in GUIs) but isn't usable in Android Firefox. The drag function doesn't work at all.

Re: Chonky Menu Re-Creation

#54

Earlier quoted context omitted.

Interesting, it's an accessibility feature that is not enabled by default. https://support.apple.com/en-us/HT204609

For some reason Apple puts the most basic stuff behind an accessibility option. For example, tab to next button in a system dialog is disabled by default.

And, because it’s not enabled by default any more, the implementation has regressed in various situations: I don’t use macOS normally, but I did briefly around six months ago, and I immediately found several bugs in keyboard navigation within the System Preferences app, such as where some fields weren’t accessible that way, or where Shift+Tab wasn’t the opposite of Tab (e.g. {1} ⇥ {2} ⇥ {3} ⇧⇥ {1}, rather than ending on {2}).

Re: Chonky Menu Re-Creation

#55
post #51
post #49

Earlier quoted context omitted.

Is my demo trying to access all that stuff??

Why else would I paste that?

I don't know, maybe by mistake?

I looked into it, it is the YouTube embed on the page that is triggering that, I suppose any YouTube embed will cause that.

Re: Chonky Menu Re-Creation

#56
post #48

This looks great, but it's using 50% of my CPU (i5-3320M) just for a menu and some visual flair. Not worth it.

Yeah, it would certainly need to be (and readily could be) optimized if used in production.

Thanks for the reply.

A quick comment on UX - my laptop is old (see: the aforementioned ancient processor), and these types of menus are extremely inefficient for screen real-estate. On a 1366x768 display, most modern webapps/applications simply need that full screen real estate. They become unusable if you try to split in either direction (which I want to do oh so often, using a tiling window manager). Even when given the full screen resolution, some things are simply unusable.

I think a design like this is at risk of falling into the "always unusable" category for hardware like mine. Of course, I know this is just a demo, and context matters a lot, but I still think it's something worth considering.

If each menu item is 65px in height - on a 1366x768 display, once you account for taskbars, titlebars, browser tab interfaces, menu bars, etc, you'd probably be lucky to have about 500px of vertical real estate left for the main content. So you'd barely be able to shove ~7.5 elements on screen with a list like this. Just food for thought.

Re: Chonky Menu Re-Creation

#57
post #43
post #35

Earlier quoted context omitted.

I'm on Android Chrome 116 and I scrolled all the way to the bottom and wow that was a responsive component! Super fast and buttery smooth animation. I'm impressed

Android 13 Chrome 117 here and it did not work for me. Menu popped open on the long press, but moving my thumb up or down resulted in the whole page scrolling. Ditto on Firefox 117. (Is that weird that both my browsers are on the same version number?)

There's some speculation that it's because of "trying to compete in the minds of users who actually think they can compare two totally different software applications by comparing their version numbers."

https://superuser.com/a/303531

Re: Chonky Menu Re-Creation

#58
post #16

Earlier quoted context omitted.

> The usability on a laptop goes out the window as you realize you can't accelerate past the edge of your touchpad. Getting to the top item in the menu -- maybe even the most important item -- is extremely hard. You rapidly become limited to the number of items you can have in this menu. Not really. Put a second finger at the bottom of the touchpad, then release the first finger (without dragging while both fingers a…

If you have to explain how to use it…

The simple version would be "finger crawling", like you're dragging a piece of paper. I think it is intuitive, it just seems to need more explicit instruction for people nowadays who never really did arts and crafts as kids, and built their understanding on new non-physical conventions instead (like three-finger gestures as in the other reply - I find those weird, not at all intuitive, and sometimes difficult to do because my fingers are different lengths - drag is mostly fine since I can just move my whole hand, but other gestures not so much).

Re: Chonky Menu Re-Creation

#59
post #55
post #51

Earlier quoted context omitted.

Why else would I paste that?

I don't know, maybe by mistake? I looked into it, it is the YouTube embed on the page that is triggering that, I suppose any YouTube embed will cause that.

I changed it to use lite-youtube-embed which doesn't request that stuff until after the user clicks to play the video

Re: Chonky Menu Re-Creation

#60
post #13

This is great -- all the way up to the point where you have to hold and drag. The usability on a laptop goes out the window as you realize you can't accelerate past the edge of your touchpad. Getting to the top item in the menu -- maybe even the most important item -- is extremely hard. You rapidly become limited to the number of items you can have in this menu. Tap-or-swipe-to-open, and tap-or-swipe-to-close have ra…

As always, "designers" are optimising for what looks cool and fancy subjectively to them, rather than optimising for usability. In their defence, the latter is much harder :)
Post reply on HN