9 ms·
Don't forget Puppertino for OSX! https://github.com/codedgar/Puppertino https://github.com/codedgar/Puppertino https://github.com/codedgar/Puppertino https://g
by purgedreality 4y ago
Don't forget Puppertino for OSX! https://github.com/codedgar/Puppertino https://github.com/codedgar/Puppertino
https://github.com/codedgar/Puppertino https://github.com/codedgar/Puppertino
- dmitriid 4y ago"Based on MacOS HIG guidelines" ... uses links for buttons. Somehow this is even more aligned with Apple of today.
- o_m 4y agoWhat do you mean? There is nothing wrong with displaying a link with a button style as long as you treat it as a link with that navigates somewhere else. In the docs they are using buttons on interaction that does not navigate.
- dmitriid 4y ago> What do you mean? There is nothing wrong with displaying a link with a button style as long as you treat it as a link with that navigates somewhere else. Yup. This basically sums up current approach. There's a clear semantic distinction between a button and a link. For example, screen readers will treat them differently. And this is especially egregious when your example page is specifically about buttons: https://codedgar.github.io/Puppertino/examples/buttons.html https://codedgar.github.io/Puppertino/examples/buttons.html Edit: Segmented controls are also links: https://codedgar.github.io/Puppertino/examples/segmented_controls.html https://codedgar.github.io/Puppertino/examples/segmented_con... As are buttons like "close this sheet" in actions: https://codedgar.github.io/Puppertino/examples/segmented_controls.html https://codedgar.github.io/Puppertino/examples/segmented_con... etc. etc.