Bugzilla – Bug 466
change some message strings in assertions.sch to harmonize with Assertions.java messages
Last modified: 2009-04-01 14:05:17 CEST
Because of differences in the constraint-checking logic in Assertions.java and assertions.sch, it's not very practical to try to have the Assertions.java match some of the original message output from assertion.sch for particular cases.
For example, there are a number of cases in assertions.sch where the message output is "The interactive element foo cannot appear as a descendant of the bar element." But the logic differences in Assertions.java don't make it very practical to have it emit the "interactive" qualifier for those cases (because Assertions.java uses the same code to handle both those interactive elements and also non-interactive elements that have descendant/ancestor constraints.
Similarly, assertions.sch outputs "The foo element cannot contain any nested foo elements." But Assertions.java uses the same code to handle both such "nesting" cases and also non-nesting cases, such that it outputs instead, "The foo element must not appear as a descendant of the foo element."
I'm OK with the messages not being exactly harmonized.
moving to invalid per comment from Henri