« Evidence suggesting more than half of web app UI code is reinventing results already achieved many times before | Main | Designing by Making: your process for arranging furniture can point toward a good process for UI design »

September 17, 2012


TrackBack URL for this entry:

Listed below are links to weblogs that reference An axiomatic approach to defining user interface elements: building complex elements from simple ones:



What do you mean by natively provided by the browser? What about input type checkbox and radio? How are those any less native than buttons?

Jan Miksovsky

BZ: By "native" to the browser, I mean all the interactive elements defined in HTML itself. This is basically the elements, and arguably some aspects of other elements with defined interactions. (E.g., an element with a title attribute will generally produce a tooltip). So a checkbox or radio button would count as native by that definition. My complaints are that this set of these native interactive components is very small, and that you can't build first-class components like those yourself (yet).


Hi BZ,
Unfortunately the comments for your article on web menus is already closed, so please allow me to float an idea here:
Why not use the browser menu bar for web applications? The browser itself should be allowed a "Firefox" or "Safari" menu for its settings (similar to the Apple menu on the Mac) while the application designer could build an application specific application menu structure. The browser could lend things like "Print" a hand (just like the OS does to the browser).
This way, menus would automatically blend into the host OS - Apple users could just push their mouse upward to hit the right one while Windows users could hang on to their target exercises.
I think that future versions of browsers should behave like that (at least offer an "application mode"). Is this wishful thinking or do you think this is already on the horizon?

The comments to this entry are closed.