What you are describing is definitely a bug. I'm not aware of an existing
bug of this nature (we have several where the wrong JSF tag is inserted
into a valid JSF page). Either way, feel free launch a new bug and we
will try to address. Worst case, it gets dup'ed and you'll get an e-mail
showing you the existing bug :).