3 ms·
yes, but you want to close frame, img, li, and p tags http://msdn.microsoft.com/en-us/library/ms533020(VS.85).aspx#Close_Your_Tags http://msdn.microsoft.com/en
by gtani 17y ago
yes, but you want to close frame, img, li, and p tags
http://msdn.microsoft.com/en-us/library/ms533020(VS.85).aspx#Close_Your_Tags http://msdn.microsoft.com/en-us/library/ms533020(VS.85).aspx...
- gojomo 17y agoTheoretically, perhaps. Practically, I doubt the close-tags proposed by this MSDN article would make any measurable difference. In fact, leaving tags out consistently in certain tag-heavy auto-generated layouts, by reducing network IO and fitting more content into memory buffers at a time, could be faster.
- dunham 17y agoUsing the close-tags proposed by the MSDN article would yield an invalid HTML document. Per the DTD and the SGML standard, the closing tag of IMG, an element with EMPTY content, MUST be omitted. The element is already closed before the parser gets to the closing tag - so, in essence, you would be trying to close it twice.
- mcav 17y ago> If you do close your tags, Internet Explorer will render your pages even faster. Whereby "even faster" still means much slower than standards-adherent browsers. I can't imagine that closing the tags improves the speed enough for it to make any real difference. Better to optimize a javascript algorithm or compress an image to squeeze out another millisecond or two.