W3C home > Mailing lists > Public > public-qt-comments@w3.org > September 2006

[Bug 3690] The set of all possible modes is not clearly defined

From: <bugzilla@wiggum.w3.org>
Date: Sun, 10 Sep 2006 08:00:34 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1GMKF0-0006bM-2L@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=3690





------- Comment #1 from colin@colina.demon.co.uk  2006-09-10 08:00 -------
When I raised the bug, I was only concerned that the ambiuity was resolved one
way or the other.
But now having thought about it a bit more, it is clear to me that it should be
resolved in the direction of only allowing modes that are specifically defined
in the compiled stylesheet.

The only reason for supplying an initial mode is to override the default mode.
So it makes no sense to supply a mode that is not defined. And it is very
harmful, if the selected initial template (or some descendant of it in the
match/call chain) should then dispatch on the current mode.

The user is entitled to a good error message if (s)he mis-types the name of the
initial mode.

I can think of no use cases for the opposite interpretation.
Received on Sunday, 10 September 2006 08:01:01 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:30 UTC