Weirdest Internet Explorer issue I"ve ever seen.

It can't really be explained. Here's a demo.

http://toao.net/pub/widthtest.html

Re: Weirdest Internet Explorer issue I"ve ever seen.

Scripsit Mango:

> It can't really be explained.

I have an explanation, but it can't really be explained.

--
Jukka K. Korpela ("Yucca")
http://www.cs.tut.fi/~jkorpela/

Re: Weirdest Internet Explorer issue I"ve ever seen.

Well bust mah britches and call me cheeky, on Wed, 30 Jan 2008 07:42:26 GMT
Jukka K. Korpela scribed:

> Scripsit Mango:
>
>> It can't really be explained.
>
> I have an explanation, but it can't really be explained.

Hmm, that's inexplicable. Have you tried telepathy or Yiddish?

--
Neredbojias
Riches are their own reward.

Re: Weirdest Internet Explorer issue I"ve ever seen.

Mango wrote:
> It can't really be explained. Here's a demo.
>
> http://toao.net/pub/widthtest.html


Nobody really knows what you want to do, but I'd like to make these
observations. You have a table with no specified width and then you put
in a form element with a width of 100%. What do you expect? Give the
poor DOM a break.

Jeff

Re: Weirdest Internet Explorer issue I"ve ever seen.

Jeff wrote:
> Nobody really knows what you want to do, but I'd like to make these
> observations. You have a table with no specified width and then you put
> in a form element with a width of 100%. What do you expect? Give the
> poor DOM a break.

The issue also happens when I specify a width for the table.

I find it interesting that the table expands, even though the form
element stays its proper size.

-Mango

Re: Weirdest Internet Explorer issue I"ve ever seen.

Jukka K. Korpela wrote:
> Scripsit Mango:
>
>> It can't really be explained.
>
> I have an explanation, but it can't really be explained.
>

Okay, you got me. Explain :)

Re: Weirdest Internet Explorer issue I"ve ever seen.

Jeff wrote:
> Mango wrote:
>> It can't really be explained. Here's a demo.
>>
>> http://toao.net/pub/widthtest.html
>
> Nobody really knows what you want to do,

As far as I can tell, the gist of it is that the third link calls the
same function called by the first link followed by the same function
called by the second link. But it causes something else, something
weird, to happen that doesn't happen if you click the first link and
then the second link.

In both IE7 and Firefox, another strange thing is that when the input
field is created with width set to 100%, it slightly overlaps the right
border of its containing table cell. If I set overflow="hidden" for the
cell, it fixes this in Firefox but not in IE7.

> but I'd like to make these
> observations. You have a table with no specified width and then you put
> in a form element with a width of 100%. What do you expect? Give the
> poor DOM a break.