3 ms·
If you're developing a half-way complex web application, you largely don't want to depend on OS default dialogs. They can be buggy, detract from the UX of the r
by vertex-four 10y ago
If you're developing a half-way complex web application, you largely don't want to depend on OS default dialogs. They can be buggy, detract from the UX of the rest of your application, require additional support as now you need to explain how to use the different dialogs on N different operating systems, and it's often the case that your application is the first time the user comes into contact with that dialog anyway - they're usually not nearly as commonly used as you'd think.
- taneq 10y agoI'm trying to think of a cross-platform framework that didn't eventually do away with native widgets, at least optionally. Java went from AWT to Swing, wxWidgets has wxUniversal, even the <button> tag got custom skinning. Is this becoming a pattern? "Cross Platform Requires Owner Drawn Widgets."