This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 538 - nodegettextcontent19 relies on non-val parser not supporting ecw
Summary: nodegettextcontent19 relies on non-val parser not supporting ecw
Status: RESOLVED FIXED
Alias: None
Product: DOM TS
Classification: Unclassified
Component: DOM Level 3 (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Philippe Le Hegaret
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-19 09:53 UTC by Andrew Clover
Modified: 2004-02-19 20:33 UTC (History)
0 users

See Also:

Attachments
Add precondition of validating parser (1.65 KB, patch)
2004-02-19 15:32 UTC, Curt Arnold 		Details

Description Andrew Clover 2004-02-19 09:53:12 UTC 
This test assumes that a non-'validating' implementation won't be able to detect
ElementContentWhitespace. However according to infoset whilst a non-validating
parser is not obliged to make this information item known, it is not prohibited
from doing so either.

As the ELEMENT declaration for <body> is in the internal subset of barfoo.xml,
there is no reason a non-validating parser should be unable to determine the
content model. So the results '\nbar\n' or 'bar' are both possible.
Comment 1 Curt Arnold 2004-02-19 15:32:40 UTC 
Created attachment 239 [details]
Add precondition of validating parser