>AFAIK, typical browser resets don't muck with control sizing and display modes. These are vastly different on each machine (ie. textbox padding, line spacing in the select lists, button sizes and display and control fonts). Resets don't change this because the control chrome invariably is managed differently by all browsers.

I might have missed something in my test sequence but I did it twice. I am pretty sure that just by assigning one style to a control that is has affected the height of the control, even if it is not suppose to. This was replicated across the four browsers I tested with.

>These days if you want consistency and good starting point for styling I honestly would recommend looking into some base CSS framework like BootStrap to give you a consistent look across browsers along with some nice extended features like grid layout support, control support, custom buttons, menus etc. I've basically created my own framework for the longest time but eventually just gave up and settled on using Bootstrap as a base - the functionality it provides is just so rich and miles above what I came up with on my own. I still have many custom, common styles I use ontop of BootStrap but the core CSS is driven by Bootstrap. If nothing else it's an awesome starting point and if you're so inclined an amazing CSS learning tool.

I appreciate the information on what I could get with the CSS framework like BootStrap but I already have all that in my framework.

I do have a consistent look across four browsers at this point, still haven't had time to adjust a few things for Opera. This is the 5th one that I want to support. Firefox, IE, Chrome and Safari are all ok for now. This one pixel offset, which occurs at a few locations, is not a must but a nice to fix. This reminds me of a situation, a few years ago, on a desktop application, that dependingon the pixel in height where the line was, this was causing such reaction. I would then assume the same would happen in the browser. But, this is changing so fast. One version might have a fix for it, the next one falls back to the older situation. :)