Re: [WSG] Last letter of a line appearing on next row (IE6...)

2006-12-14 Thread Nick Fitzsimons
On 13 Dec 2006, at 22:18:42, Rob O'Rourke wrote: I need to get control of what hasLayout and what doesn't before I can work out what's really going on. Use Microsoft's IE Developer Toolbar's DOM Inspector: http://www.microsoft.com/downloads/details.aspx?

Re: [WSG] Last letter of a line appearing on next row (IE6...)

2006-12-14 Thread Rob O'Rourke
Nick Fitzsimons wrote: On 13 Dec 2006, at 22:18:42, Rob O'Rourke wrote: I need to get control of what hasLayout and what doesn't before I can work out what's really going on. Use Microsoft's IE Developer Toolbar's DOM Inspector:

Re: [WSG] Last letter of a line appearing on next row (IE6...)

2006-12-14 Thread Nick Fitzsimons
On 14 Dec 2006, at 17:46:58, Rob O'Rourke wrote: Nick Fitzsimons wrote: On 13 Dec 2006, at 22:18:42, Rob O'Rourke wrote: I need to get control of what hasLayout and what doesn't before I can work out what's really going on. Use Microsoft's IE Developer Toolbar's DOM Inspector:

Re: [WSG] Last letter of a line appearing on next row (IE6...)

2006-12-13 Thread Gunlaug Sørtun
Rob O'Rourke wrote: I had the last letter of some floated form elements appearing on the next line. I've managed to get rid of the letter itself with position: relative; on the form input but there's still a 'phantom line' in IE adding a load of 'padding' to the bottom of the label or fieldset.

Re: [WSG] Last letter of a line appearing on next row (IE6...)

2006-12-13 Thread Rob O'Rourke
� wrote: Rob O'Rourke wrote: I had the last letter of some floated form elements appearing on the next line. I've managed to get rid of the letter itself with position: relative; on the form input but there's still a 'phantom line' in IE adding a load of 'padding' to the bottom of the label or

Re: [WSG] Last letter of a line appearing on next row (IE6...)

2006-12-13 Thread Rob O'Rourke
Nick Fitzsimons wrote: On 13 Dec 2006, at 19:39:17, Rob O'Rourke wrote: I found the PIE page i was looking for [1], it was the duplicate characters bug however none of the triggers mentioned on that page were present... as far as i could work out anyway. [1]