Quoting Ian Hickson <[EMAIL PROTECTED]>:
Another problem (which I just noticed on CNN.com) is that if we say that
<noframes> creates nodes, browsers will be creating nodes for <img>
elements that previously they were not creating, which will cause a
different set of images to be fetched from the server.

This would be a problem for statistics programms which rely on this mechanism
more or less to detect who browses without scripting. (This is very common so
it would break a lot of pages.)

As the specification is currently defined it seems fine. The only "problem" is
that a page would have to be reparsed when the user disables scripting or
frames.


--
Anne van Kesteren
<http://annevankesteren.nl/>

Reply via email to