Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

: The Dialog Element

developer.mozilla.org

Post reply on HN
Print view View original

141–150 of 160 posts

Re: <dialog>: The Dialog Element

#141

Post by IgorPartola »

DaiPlusPlus wrote: post #46
ryandrake wrote: post #43

Earlier quoted context omitted.

I feel like every company's (different/contrasting) "design language" and their insistence on using it, ends up being yet another weird looking thing on my computer. I'd rather decide for myself the fonts, color scheme, look and feel, etc. for applications on my computer, and have applications be consistent and respect those preferences. Rather than have some artist I don't know 2,000 miles away from me simply decide…

"But we don't want to look like everyone else"

These are the same people who insist on having PDF copies of everything and sometimes PDF forms. Nobody ever designs custom PDF form styling to be different. I wonder why? /s

Re: <dialog>: The Dialog Element

#142

Post by ilius2 »

wongarsu wrote: post #123
dv_dt wrote: post #122

Earlier quoted context omitted.

Depends if you mean consistent to the os or browser or consistent to the js framework - I would suggest that most casual users don't notice and actually do better if its consistent to the os or browser they use Well some other comment mentioned audio/video and those are seemingly aways different

> Well some other comment mentioned audio/video and those are seemingly aways different Which is probably fine for your users. In every browser it plays video and has basic controls like a start/pause button, a timeline and a volume control. While the video is playing they even look identical: it's the video, playing; with controls only visible on hover. The differences aren't an issue for the actual user, they are a…

So it's industry's management problem, not a tech problem.

Re: <dialog>: The Dialog Element

#143

Post by mardifoufs »

xp84 wrote: post #97
ryandrake wrote: post #43

Earlier quoted context omitted.

I feel like every company's (different/contrasting) "design language" and their insistence on using it, ends up being yet another weird looking thing on my computer. I'd rather decide for myself the fonts, color scheme, look and feel, etc. for applications on my computer, and have applications be consistent and respect those preferences. Rather than have some artist I don't know 2,000 miles away from me simply decide…

I think most of us here who aren't self-important "UX designers" (or branding consultants) would agree with you, but the decision makers responsible for most of the sites on the Web disagree/don't care what we'd like. They want their site to look identical on all platforms and browsers, and to have their "signature" design language, to heck with what users might expect. It's why you see stupid things like pixel-perfe…

Idk, personally I completely disagree. I don't want to theme every single app. I want them to be distinctive and I don't actually care about native look. What I care about is that they have a nice design (which is as subjective as it gets, I know) but more importantly that they are distinctive enough in terms of design. Now I don't want every app to have different shortcuts or whatever, but I don't want slack to look like discord for example. And I don't want to theme anything ideally.

Re: <dialog>: The Dialog Element

#145

Post by dehrmann »

DaiPlusPlus wrote: post #4

I started using in 2019, even though Firefox and Safari wouldn't support it for another couple of years, but Google's own Polyfill (of which I am a very modest contributor) was top-notch quality and so I had no problems using it in production for my LoB SaaS day-job. But my biggest let-down with the element is that it's comnpletely unstyled, beyond a very basic (and very un-Chrome-like) thick black line pixel border…

> comnpletely unstyled

I haven't done any serious web development for a decade, but did they ever get around to adding sane styling for drop-down menus?

Re: <dialog>: The Dialog Element

#146

Post by BeFlatXIII »

mikae1 wrote: post #115
divbzero wrote: post #94

Other delightfully interactive HTML elements include… File pickers: Color pickers: Date/time pickers: Numeric sliders: Suggested options for text fields: Summaries with expandable details: FAQs Why are interactive HTML elements cool? They’re lightweight and semantic! Will the previous answer close when I open this one? Yes, because the &lt;details&gt; elements share the same name. Media players with controls:

> Media players with controls: > > Which look different in every single browser and can't be styled without JavaScript. Wish these were implemented better.

I wish more websites left things with default styling.

Re: <dialog>: The Dialog Element

#147

Post by simonw »

simonw wrote: post #85
DaiPlusPlus wrote: post #4

I started using in 2019, even though Firefox and Safari wouldn't support it for another couple of years, but Google's own Polyfill (of which I am a very modest contributor) was top-notch quality and so I had no problems using it in production for my LoB SaaS day-job. But my biggest let-down with the element is that it's comnpletely unstyled, beyond a very basic (and very un-Chrome-like) thick black line pixel border…

I've been playing around with the idea of alert() and prompt() and confirm() replacements that work like this: await Prompts.alert("This is an alert message!"); const resultBoolean = await Prompts.confirm("Do you want to proceed?"); const name = await Prompts.prompt("What is your name?"); Demo here: https://tools.simonwillison.net/prompts-js - code written by o1: https://chatgpt.com/share/67539c28-4df0-8006-b021-4f46…

I improved this (by porting it to the dialog.showModal() API, relevant to this post) and shipped it to NPM as a package called prompts-js.

Code here: https://github.com/simonw/prompts-js

Blog writeup: https://simonwillison.net/2024/Dec/7/prompts-js/

Re: <dialog>: The Dialog Element

#148

Post by dotancohen »

WD-42 wrote: post #45
thousand_nights wrote: post #42

Earlier quoted context omitted.

i don't know what context you're using it in, but imagine a company like airbnb or booking.com using the built in date picker on their front page you might as well cut their public valuation in half at that point. it's just not worth it to use the completely neglected and anemic components that are part of the browser, they are a joke

Weird. I think the built in date picker is actually pretty nice.

In which browser and OS?

Re: <dialog>: The Dialog Element

#150

Post by saagarjha »

porridgeraisin wrote: post #120
nikodotio wrote: post #119

Earlier quoted context omitted.

I use all of them pretty consistently! I try not to have them do magic, but using native date pickers and dropdowns and selects saves so much time and headache - and they work consistently.

How do you use audio/video consistently across browsers? It looks quite different across the browser/platform combination matrix.

You put one on the screen and the user controls it with the controls they are used to.
Post reply on HN