Live data from Hacker News

Accessible hamburger buttons without JavaScript

pausly.app

141–150 of 154 posts

Re: Accessible hamburger buttons without JavaScript

#141
post #120

Earlier quoted context omitted.

PDAs and the Nokia phone, mp3 player generation had icons. 90s-2010s

PDA's where niche. No one used hamburger buttons prior to 2007-2010. No. One. Period.

The wikipedia article linked elsewhere disproves that.

However I misread the thread in my previous post.

Re: Accessible hamburger buttons without JavaScript

#142

Not sure if you're the author, but I'm having an issue signing up for Pausly. After connecting an auth provider, there's a screen that asks for your name, and it's not possible to check the ToS checkbox. The error in the console is: > Cannot destructure property 'supabaseUrl' of 'Re(...)' as it is undefined.

Thanks! Could you please tell me if this is still happening (make sure to reload first) and if so, would you mind sending me the email address you used for signup to support@pausly.app?

Re: Accessible hamburger buttons without JavaScript

#143
post #95
post #59

Earlier quoted context omitted.

Unfortunately there are still plenty of issues with the details element, especially around accessibility. Read more here: https://cloudfour.com/thinks/a-details-element-as-a-burger-m... Hopefully this will change soon. I’ll amend the article when this will be the case.

Referenced in that article is: https://adrianroselli.com/2019/04/details-summary-are-not-in... Which says JavaScript is required and simplest solution for building this menu. It also states to try to avoid them when possible.

> Which says JavaScript is required

Only if you want to polyfill for pre-2019 browsers

https://caniuse.com/?search=details

Re: Accessible hamburger buttons without JavaScript

#144

Earlier quoted context omitted.

> What's more, suckling is a hardwired reflex , not something that's intuited The fact that suckling is a hardwired reflex is what makes using the nipple intuitive. You use it by doing the same thing you think you should do.

> The fact that suckling is a hardwired reflex is what makes using the nipple intuitive. You use it by doing the same thing you think you should do. In this case it gets used automatically without choice or thought. Anything shoved into a baby's mouth triggers it. It's not intuition, just reflex. Intuition implies understanding. It's the difference between "I know that what this is for and how to use it" vs "I have n…

> Intuition implies understanding.

No, if anything it's the opposite. If you understand something, you'll find it easy to use. Intuition is what you rely on in the absence of understanding.

Re: Accessible hamburger buttons without JavaScript

#145

Earlier quoted context omitted.

> The fact that suckling is a hardwired reflex is what makes using the nipple intuitive. You use it by doing the same thing you think you should do. In this case it gets used automatically without choice or thought. Anything shoved into a baby's mouth triggers it. It's not intuition, just reflex. Intuition implies understanding. It's the difference between "I know that what this is for and how to use it" vs "I have n…

> Intuition implies understanding. No, if anything it's the opposite. If you understand something, you'll find it easy to use. Intuition is what you rely on in the absence of understanding.

I'd say intuition is understanding in the absence of instruction or prior experience. Something intuitive should be something you find easy to use.

Re: Accessible hamburger buttons without JavaScript

#146
post #121

Earlier quoted context omitted.

This. These younger users thinking the 00's and the 90's where like their child years are pretty much deluded. And it's odd because you can emulate W98, W2k, WXP and old GNU/Linux distros with damn ease in order to understand that no wm or desktop environment offerred a hamburger menu. And, trust me, lots of people tried zillions on WM's, tons of FVWM2 setups with bizarre configs highly divergent between themselves a…

I think the (OS name here) start menu is the hamburger menu. Except on mac, they have several icons that are hamburger menus =/ It's common, just different icon.

No, not all. The start menu is a launcher icon with the most common software. Fvwm had a similar root menu, but with no icon for it, you just clicked anywhere. The hamburguer menu today it's used as a application menu replacement.

Back in the day it wasn't used, period. Any software, either Win32, Motif, Delphi, Athena or such used a menu to access the most common items, the settings and a toolbar for functions. There was no icon replacing all of it.

The same with Macs. Mac OS 8, 9, and then, X. No hamburguer menu. The uberknown Mac menu and a set of Cocoa icons. That it.

Re: Accessible hamburger buttons without JavaScript

#147
post #49

Earlier quoted context omitted.

likely a case of wanting "one design to fit all devices".

And "one design to fit not maximized windows on not high-dpi screens." The new design vs the old design. https://imgur.com/a/rV1UXc4

Thanks for that great perspective, I can absolutely see the benefit of the new design in a cramped display or at lower resolutions. OTOH, the comparison at 4k is strikingly different.

Re: Accessible hamburger buttons without JavaScript

#148
post #95

Earlier quoted context omitted.

Referenced in that article is: https://adrianroselli.com/2019/04/details-summary-are-not-in... Which says JavaScript is required and simplest solution for building this menu. It also states to try to avoid them when possible.

> Which says JavaScript is required Only if you want to polyfill for pre-2019 browsers https://caniuse.com/?search=details

You missed the point then. You're probably going to need to use ARIA to attach and toggle the appropriate states in real time and that is only going to work with JavaScript.

Re: Accessible hamburger buttons without JavaScript

#149
post #120

Earlier quoted context omitted.

PDA's where niche. No one used hamburger buttons prior to 2007-2010. No. One. Period.

The wikipedia article linked elsewhere disproves that. However I misread the thread in my previous post.

Our actual experience say otherwise instead of your review of 90's history on Wikipedia and alikes.

PDA's where a CEO/mid-boss/rich guy tools and nothing more, ditto with cell phones until late 90's.

The 99% of the people using software was doing that thru PC's and with a mouse and menu based WIMP interfaces, and not a smartphone based UI.

Re: Accessible hamburger buttons without JavaScript

#150
post #49

Earlier quoted context omitted.

And "one design to fit not maximized windows on not high-dpi screens." The new design vs the old design. https://imgur.com/a/rV1UXc4

Thanks for that great perspective, I can absolutely see the benefit of the new design in a cramped display or at lower resolutions. OTOH, the comparison at 4k is strikingly different.

The old wikipedia design predates consumer access to 4K monitors though.

The reason the text wasn't wider is because long lines of text are hard to read. It's why newspapers typically arrange their text into columns, rather than having one article being 2-3 lines long stretching across the entire page.

Post reply on HN