Uploaded image for project: 'Daffodil'
  1. Daffodil
  2. DAFFODIL-2457

xmlns="" incorrectly introduced due to prefixOrNull

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 3.0.0
    • 3.1.0
    • Back End
    • None

    Description

      When thisElementNamespacePrefix was replaced with prefixOrNull, we lost the functionality where namespaces prefixes are looked up. And instead relied only on the lexical prefix. There's plenty of times when there is no lexical prefix, but there is a namespace associated with the element, thus we can attempt to look up a prefix. We need to bring back this functionality, fixing the incorrect namespaces and incorrect prefixes.

      Attachments

        Activity

          People

            okilo@tresys.com Olabusayo Kilo
            okilo@tresys.com Olabusayo Kilo
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: