4 ms·
> Some devices just aren't suitable for some types of content I think that’s rather dismissive when said content is simple text in the browser. Easy solution:
by bradley_taunt 5y ago
> Some devices just aren't suitable for some types of content
I think that’s rather dismissive when said content is simple text in the browser. Easy solution: don’t use fixed navigation - it is a very bad UX pattern for content/informational websites. That’s why scrolling exists. I assure you that users don’t require access to your menu 24/7 when reading through your website.
- hypertele-Xii 5y ago> I think that’s rather dismissive when said content is simple text in the browser. Content is not simple text in this case. My site is designed for visual arts and experimental literature, including poetry.
- bradley_taunt 5y agoMy point is that if it is built out in HTML - it should work on any device that can render HTML. Many other art-based, photography focused and creative writing projects work fine in my browser. You seem to just be avoiding the removal of bad UX patterns (fixed elements) for personal reasons - which is fine. But you shouldn’t hint towards the fact that it’s “how things are” and they “can’t be fixed”. You’re hurting user experience for personal preference - not limitations.
- bradley_taunt 5y agoReplying to my own comment for additional content: I wrote about this "sticky" header problem back in 2019. Seems very relevant to this current discussion. https://tdarb.org/blog/sticky-elements.html https://tdarb.org/blog/sticky-elements.html