OE, mishandling improperly nested tags, quasi-freezes system
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
1) On Thu 02 Jul 2009 04:32:05 GMT, "Eric Caron" wrote:
« Which is why I prefaced the post with... »

I totally support you on this. You have all sorts of people:

- the most careful use to write properly AND to be fault-tolerant to
others; being careful takes a lot of time, so these people POST VERY
LITTLE; this is just what you are doing;
- the most reckless use to write casually hence improperly AND to be
intolerant to others' real OR SUPPOSED faults; being casual uses
little time, so these people POST A LOT;
- the most numerous are inbetween, more on the careful side but little
involved in the particular issue, which make them POST VERY LITTLE OR
NOT AT ALL.

The above thread perfectly illustrates this - and should NOT dilute
and slow down the efforts you are making to find solutions tolerant to
others' faults:
« I thought the IE dev team deserved to know a bug (not relying on JS
or ActiveX) that would cause the browser to break ».
I hope your report will be forwarded to the dev team and finally get
corrected.

2) I complete with my test, under Windows XP Pro 32bits (2GB RAM,
Pentium M760 2GHz) with the http://blogs.msdn.com/tonyschr/archi...25/421923.aspx
"Desktop Heap Limit" changed from 3,072 (default) to 8,192:

- the sample, automatically completed by OE (closing FORM added AFTER
the closing TABLE), still fails: IE6 slows *not all but a vast number
of* my open IE and OE windows; even Task Manager is slowed nearly to
freeze; after a moment the faulty IE window's Taskbar icon lets me
Right-Click it and close it, then after another delay it does close
and immediately everything is OK.
- that OE-completed sample, once corrected (just the "<FORM id=b>"
being moved BEFORE the OPENING "TABLE" tag), works OK.

I did no test in other browsers (lack time right now)

Versailles, Thu 2 Jul 2009 14:25:40 +0200