The problem is.... Google's Chrome for Windows doesn't look native. And which app does? MS Office doesn't look native either. Neither does IE. In fact, very fe

The problem is.... Google's Chrome for Windows doesn't look native. And which app does? MS Office doesn't look native either. Neither does IE. In fact, very few MS apps actually use their guidelines and default widget sets. Office, for example, has a completely different widget set and even has a different toolbar (ribbon).... not to mention a completely different window chrome and that big round button in top left. And many other Windows apps don't follow the guidelines either. A non-native UI that looks the same on Mac, Windows, and Linux would be the answer to such a browser OS. It would indicate that Chrome is its own product - from the codebase to the user experience - and that to the end user it shouldn't matter what OS you're on. Except that people today do use different OSes and nativeness does matter! Inconveniencing and annoying your users with an intent to make them aware that your app is somehow different is opposite from what you should be doing: conforming to their learned patterns of how their UI works and making the transition to a new app painless and 'invisible.' I'm in complete agreement with Goodger on this one: none of the cross platform widget sets feel native on any of the OSes. Firefox still feels awkward on OS X and has a lot of deficiencies in the way the text boxes work, keyboard navigation for assistive devices. In-browser widgets like buttons and drop-down menus are just off when you compare them with native widgets (drop-down in particular) and feel weird. They invoke that 'the uncanny' feeling: http://en.wikipedia.org/wiki/The_Uncanny http://en.wikipedia.org/wiki/The_Uncanny They look like the real thing but aren't and give you that uncomfortable feeling.