What does the end user expect from a dropdown combo box with a button next to it?
The example I have is the one in the Chat tool which allows the end user to choose how many of the Chat Rooms past messages to display on the screen. It works in combination with the chat.max.messages= property, so that choices presented to the end user may include
"View 10 messages" "View 100 messages" or "View 1000 messages", as well as "View past 3 days".
To the right of the combo box is a submit button. The submit button has to be clicked for the view to be updated, but the expectation may be that the view will continuously display, for example, the last 10 messages only. However, that count continues to grow until the submit button is clicked again. I don't think that's what our users expect. They will expect the "Submit" button to behave more like "Apply Setting" , which, once applied, will always update to keep 10, 1000 or 3 days worth of messages on screen, while removing, allowing to fall off, the oldest, those outside that range.