Project

Profile

Help

Actions
Send by e-mail Copy link

Bug #5464

closed

unparsed-text() with an empty file throws a TypeError

Added by John Lumley over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Low
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
2022-04-29
Due date:
% Done:

100%

Estimated time:
Applies to JS Branch:
2, Trunk
Fix Committed on JS Branch:
2, Trunk
Fixed in JS Release:
SaxonJS 2.4
SEF Generated with:
Platforms:
Company:
-
Contact person:
-
Additional contact persons:
-

Description

Running in the browser (on an older version of SaxonJS2, but I suspect not) when reading in (via an unparsed-text() call) an empty file, there is a TypeError thrown in Fetch.js:checkForNonXmlChars() . Rather than an empty string being processed as the argument contents , a structure

 {responseText: '', contentType: null}

is bound to contents and thus throws an error on executing contents.indexOf() .

A preliminary search suggests this may not have arisen before.

Actions
Copy link
 #1

Updated by Norm Tovey-Walsh over 2 years ago

  • Status changed from New to In Progress
Actions
Copy link
 #2

Updated by Norm Tovey-Walsh over 2 years ago

  • Status changed from In Progress to Resolved
  • Applies to JS Branch Trunk added
  • Fix Committed on JS Branch 2, Trunk added
Actions
Copy link
 #3

Updated by Debbie Lockett over 2 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 0 to 100
  • Fixed in JS Release set to SaxonJS 2.4

Bug fix applied in the SaxonJS 2.4 maintenance release.

Please register to edit this issue

Actions
Send by e-mail Copy link

Also available in: Atom PDF Tracking page