4 ms·
If your point is that the buttons don't behave the way they should on Windows, then clearly this is just a bug, and programs can be successful with bugs. I coul
by tolmasky 18y ago
If your point is that the buttons don't behave the way they should on Windows, then clearly this is just a bug, and programs can be successful with bugs. I could make the exact same argument about accessibility "such and such program has no support for accessibility and yet still sells really well, so why do we need accessibility?" The idea is to provide quality beyond the minimum which is necessary to get you to use the thing.
If you could make a toolkit that was non-native, but behaved as if native on all its target platforms then obviously that would be key. Also, Chrome currently only officially exists for Windows, a platform whose users are less picky about native look and feel. You would probably have a harder time getting away with this on Mac OS X. Similarly, you can have a java app that runs pretty well on most mobile phones, but a straight port that didn't include native widgets on the iPhone would probably not be well accepted.
- ComputerGuru 18y agoMy point is that you're using javascript pop-up boxes for the browser itself (like the save password prompt) that don't use the win32 code nor conform to its interface behavior.
- tolmasky 18y agoAgain, this is a matter of opinion and platform. Firefox had to do a lot of work to make their widgets much more Mac-like because this was one of the biggest gripes from Mac users, the fact that they just had some generic UI elements in their web pages that didn't conform to what they were used to. This is the sole reason the Mozilla Camino project was even started, and again, one of the main focuses of Firefox 3 for the Mac.