Bug #1447
closed
XHTML and document.write
100%
Description
[Resubmitted on behalf of Manfred] The GWT created Saxonce.nocache.js still uses one ore more document.write instructions which in case of XHTML renders the DOM document (m) invalid. After that any reference to the DOM document will throw a server JavaScript error. Those document.write instructions should (and can easily) be replaced by DOM conformant methods.
N.B. It isn't that helpfull if a Google Software Architect states: "the whole Web doesn't like XHTML, so it's a non-issue"
https://groups.google.com/forum/?fromgroups#!topic/google-web-toolkit/2YzrbZwYAlU
Updated by Philip Fearon almost 13 years ago
- % Done changed from 0 to 100
The Saxon-CE build has been fixed to automate this workaround for the GWT issue, for this to work, XHTML . The fix works for all popular browsers except Internet Explorer prior to IE9, so for older versions of IE, Saxon-CE won't process pages served as XHTML.
Updated by Philip Fearon almost 13 years ago
- Status changed from New to Resolved
Updated by O'Neil Delpratt almost 12 years ago
- Status changed from Resolved to Closed
- Fixed in version changed from Beta 0.2 to 1.0
Fixed in Saxon-CE version 1.0
Updated by O'Neil Delpratt almost 12 years ago
- Sprint/Milestone changed from Beta 0.2 to Release 1.0
Updated by Henri Manson over 8 years ago
In Saxon-CE 1.1 Saxonce.nocache.js is using document.write again. Can this be fixed in the same way as it was done in Saxon-CE version 1.0?
Updated by Henri Manson over 8 years ago
I updated it myself and created a pull request: https://github.com/Saxonica/Saxon-CE/pull/10
Please register to edit this issue
.