I have been doing all of my development/testing on Linux/Mac OS X with Safari, Firefox, and Opera. Today I tried the site with IE8 and there were many problems:
1. On the login screen, I had tied both the enterPressed() of a WLineEdit and clicked() of WPushButton to the same slot. On IE8 only, pressing enter also triggered a click to happen so the event got called twice (causing an unanticipated problem). This did not happen on any other browser I tested. It was easy enough to workaround, but I wonder why only IE does this. 2. My layouts are a mess on IE8. The problems include: + I draw WGroupBox's with a css that draws a one pixel border. For some reason, at the top of the WGroupBox's is some odd extra row or two of pixels the color of the background color. + The contents of these WGroupBox is a WGridLayout that has three rows, with setRowStretch() of (-1, 1, -1) for the three rows. The WGroupBox also has a setMinimumSize() done on it. For some reason, even though there is plenty of room for the widget on row 1 to stretch, it always stretches too much and causes the bottom row to stretch beyond the edge of the minimum size and puts up a vertical scrollbar. Does not do this on any other browser. + Several of my WSelectionBox's which are initialized without content and filled in as the user clicks are sized very small width-wise in IE8 only before the contents are added. They stretch properly on the other browsers. There were several other visual glitches. I am going to debug this tomorrow, but before I do, does anyone have any general tips on what I might be doing to cause this behavior? Has anyone else dealt with this before? I know that all the wt examples look fine in IE8 so obviously I'm doing something either wrong or untested, but it looks so bad I'm not sure where to start. Thanks. -- Dan ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
