#211 invalid element with simple type misdiagnosed as mixed content error

[Peter A. Bigot]

The 1.2.2 test for #189 includes a second element which is not accepted by the content model, but the diagnostic generated says the reason is that there is mixed content present. This is because simple elements are implicitly converted to text to satisfy the content model if mixed or simple content is allowed.

[Peter A. Bigot]

• status changed from new to closed
• resolution set to fixed

Fixed in next branch:

commit 8edbd653bfeda2e25116aac6f968cb0cd1896501
Author: Peter A. Bigot <pab@pabigot.com>
Date:   Mon Sep 16 13:00:44 2013 -0500

    trac/211: invalid element with simple type misdiagnosed

    Add a new exception to diagnose cases where element content (or something
    that's supposed to be element content) shows up where it can't.  Use this
    for both saxer and DOM-based parsing, and in a situation where an
    element-bound value is used to initialize simple content.

    The test cases probe the boundaries of mixed content more than other tests
    have done.