scala-xml icon indicating copy to clipboard operation
scala-xml copied to clipboard

The standard Scala XML library

Results 32 scala-xml issues
Sort by recently updated
recently updated
newest added

Discussing https://github.com/scala/bug/issues/12632 I was reminded that the Mima plugin and the sbt-version-policy plugin was relaxed and put back and relaxed again a couple of times: * #551 * #598 *...

help wanted

Putting an unclosed character ref (`&#`) in XML causes an infinite loop. Example code: ``` import scala.io.Source import scala.xml.parsing.XhtmlParser val text = "test &# test " XhtmlParser(Source.fromString(text)) ```

bug
help wanted

I am trying to implement a Scalacheck XML generator that round trips through writing and parsing. I've run into a discrepancy between the character sets in scala-xml and the JVM...

I'm attempting to parse XML from a String in Scala.js and I get this compile-time error: ``` [error] Referring to non-existent class javax.xml.parsers.SAXParserFactory$ [error] called from scala.xml.factory.XMLLoader.parser()javax.xml.parsers.SAXParser [error] called from...

I've had to override this method of MarkupParser due to what I think is a bug: ``` def xCharData: NodeSeq = { xToken("[CDATA[") def mkResult(pos: Int, s: String): NodeSeq =...

We use the constructing parser so as to get file/line/column information added to parsed XML, as well as for proper handling of CDATA regions. However, we've encountered some things where...

When an XML file starts like this: ``` ``` since there is no xml declaration, it gives a warning: ``` :1:6: whitespace expectedstylesheet type='text/xsl' href='https://zzz.xsl' alternate='no' title='Default'?> ^ :1:6: '?'...

There's [a proposal to remove XML literals](https://contributors.scala-lang.org/t/proposal-to-remove-xml-literals-from-the-language/2146) in Scala 3 ("dotty") and replace them with an alternative interpolated string library. The library has macro code that makes sure the XML...

There is a fix related to apostrophes and `XMLEventReader` in #72 that is slated to appear in version 1.1.0. However, while fixing the defect there was not a change to...

good first issue