(Apologies if the threading on this gets messed up. I was not subscribed to
the list when the original message was sent.)
I want to paint Eric's scenario more strongly, because it seems like people
think if it would rarely blow up then it doesn't matter.
If you want to handle _any_ request sent
Peter,
On Sat, Apr 5, 2008 at 12:38 AM, Peter Kasting [EMAIL PROTECTED] wrote:
Or, if you like, take the position that the argument should stay optional,
and if someone for some reason doesn't have to care about security (?!),
they can avoid passing it. Although I'm not sure this is a
Should (or may) user agents display the content of the |title|
attribute of an |a| element in the GUI window caption (if the window
manager used supports such), when the user followed the link and the
retrieved resource is in a format that does not support specifying a
title by itself
The |listing| element is currently not defined in HTML5, but its
parsing is said to be the same as for |pre|. Will |listing| be
included some day or will it be left out, because |code| nested in |
pre| provides the same semantics already?
On Sat, 05 Apr 2008 16:37:42 +0200, Christoph Päper
[EMAIL PROTECTED] wrote:
The |listing| element is currently not defined in HTML5, but its parsing
is said to be the same as for |pre|. Will |listing| be included some day
or will it be left out, because |code| nested in |pre| provides the
Peter Kasting wrote:
It doesn't matter if the stack will not _commonly_ be
too deep, or if it isn't too deep for the callers that you know about
right now -- it might be too deep at some point (after someone else
changes the caller code, for example), and your sync handler will blow
up.
So
On Sat, 5 Apr 2008, Christoph P�per wrote:
Should (or may) user agents display the content of the |title| attribute
of an |a| element in the GUI window caption (if the window manager used
supports such), when the user followed the link and the retrieved
resource is in a format that does
On Sat, 5 Apr 2008, Christoph P�per wrote:
The |listing| element is currently not defined in HTML5, but its parsing
is said to be the same as for |pre|. Will |listing| be included some day
or will it be left out, because |code| nested in |pre| provides the same
semantics already?
I have
On Sat, Apr 5, 2008 at 2:19 PM, Jeff Walden
[EMAIL PROTECTED][EMAIL PROTECTED]
wrote:
Peter Kasting wrote:
It doesn't matter if the stack will not _commonly_ be too deep, or if it
isn't too deep for the callers that you know about right now -- it might be
too deep at some point (after
