Compiler looses name of entity references in XML attribute values

[scabug]

The name of the entity ("oacute" in this example) is lost:

scala> <input value="Adi&oacute;s" />
res0: scala.xml.Elem = <input value="Adi&;s"></input>

scala> <input value="Adi&oacute;s" />.attributes.value(1).asInstanceOf[scala.xml.EntityRef].text
res1: String = &;

Note this is different from behaviour in Element content:

scala> <p>Adi&oacute;s</p>.child(1).asInstanceOf[scala.xml.EntityRef].text
res2: String = &oacute;

[scabug]

Imported From: https://issues.scala-lang.org/browse/SI-5133?orig=1
Reporter: @jsalvata
Affected Versions: 2.9.0-1

[scabug]

@jsalvata said:
I've just noticed that such entity references, while legal in XML, are not acceptable in Scala according to the Scala Language Specification 2.9 (24 may 2011): section 10.1 of the SLR, unlike the XML specification, defines AttValue to include characters and character references, but not entity references.

If the SLR is considered correct, the expected result of the code above would be a compilation error. But then there would be no reason for an attribute value to be a NodeSeq -- a simple String would do, just like in SAX2. So I believe it is actually a documentation bug.

[scabug]

@SethTisue said:
The scala-xml library is now community-maintained. Issues with it are now tracked at https://github.com/scala/scala-xml/issues instead of here in the Scala JIRA.

Interested community members: if you consider this issue significant, feel free to open a new issue for it on GitHub, with links in both directions.