4 ms·
What was the problem? was it the unclosed <form> tag?
by salsayarroz 14y ago
What was the problem? was it the unclosed <form> tag?
- paulbjensen 14y agoWould love to know too, can't have been as ironic as the <input type="crash"> bug.
- Isofarro 14y agoIt was just: <input type crash> as I recall - not specifying a value for type.
- jarito 14y agoLooks like the crash doesn't happen if you provide the </form> tag, so that looks like it. Edit with more info: Looks like removing any of the markup prevents the crash. "Removing the CSS, the div, the table, etc all cause this code to not crash IE"
- acqq 14y agoThe minimal variant with which I repeated the crash was: <style type="text/css"> #a { margin: 0 10px 10px; } #b { width: 100%; } </style> <table> <tr> <td> <div id="a"> <form id="b"> <input type="text" name="test"/> </div> </td> <td width="1"> </td> </tr> </table> Removing the second td is enough to make the html not crashing on IE 9. The "crash" manifests itself in some kind of an infinite loop (one thread jumps to 100% CPU and stays so). Then the "recovery" mechanisms kick in, reloading the page, blocking again... :) Can anybody reduce it even more?
- itcmcgrath 14y agoRemoving the TR's produces the same results. Change div to p still results in the crash, but removing that level entirely doesn't.
- Fibrewire 14y agoit doesnt appear to be any single specific element, but rather the exact combination
- deleted 14y ago[deleted]