https://saxonica.plan.io/https://saxonica.plan.io/favicon.ico2016-10-28T11:56:03ZSaxonica Developer CommunitySaxonJS - Bug #3012: In browser, do not always produce HTML elements in result documents when they should be producedhttps://saxonica.plan.io/issues/3012?journal_id=74142016-10-28T11:56:03ZDebbie Lockettdebbie@saxonica.com
<ul><li><strong>Subject</strong> changed from <i>In browser, do always produce HTML elements in result documents when they should be produced</i> to <i>In browser, do not always produce HTML elements in result documents when they should be produced</i></li></ul> SaxonJS - Bug #3012: In browser, do not always produce HTML elements in result documents when they should be producedhttps://saxonica.plan.io/issues/3012?journal_id=74162016-10-28T13:34:57ZDebbie Lockettdebbie@saxonica.com
<ul></ul><p>When building result trees, elements should always be created using the Context.createElement method (in transform.js). This uses the createElement (or createElementNS) method of the JavaScript Document interface. As long as the document (context.resultDocument) that this method is called on is an HTML document, HTML elements will be produced. So we need to ensure that context.resultDocument <strong>is</strong> an HTML document in the required cases.</p>
<p>Changes to applyStylesheet method in transform.js:</p>
<ol>
<li>
<p>To set context.resultDocument to window.document when using one of the destination options.</p>
</li>
<li>
<p>To ensure that the context is passed as the 3rd arg in the Expr.makeComplexContent call, so that context.resultDocument can be accessed correctly.</p>
</li>
</ol> SaxonJS - Bug #3012: In browser, do not always produce HTML elements in result documents when they should be producedhttps://saxonica.plan.io/issues/3012?journal_id=74192016-10-28T13:58:48ZDebbie Lockettdebbie@saxonica.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul><p>Various unit tests created for this bug (in combination with <a href="https://saxonica.plan.io/issues/2944" class="external">https://saxonica.plan.io/issues/2944</a>) for the JS unit testing framework in development.</p>
<p>Further tests still required.</p> SaxonJS - Bug #3012: In browser, do not always produce HTML elements in result documents when they should be producedhttps://saxonica.plan.io/issues/3012?journal_id=74512016-11-03T16:35:36ZDebbie Lockettdebbie@saxonica.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li></ul><p>Now marking this as resolved, as more tests have been added, and have not found further issues.</p> SaxonJS - Bug #3012: In browser, do not always produce HTML elements in result documents when they should be producedhttps://saxonica.plan.io/issues/3012?journal_id=76902016-12-09T16:03:07ZDebbie Lockettdebbie@saxonica.com
<ul><li><strong>Fixed in version</strong> set to <i>0.9.1</i></li></ul><p>Bug fix applied in the Saxon-JS 0.9.1 beta release.</p> SaxonJS - Bug #3012: In browser, do not always produce HTML elements in result documents when they should be producedhttps://saxonica.plan.io/issues/3012?journal_id=77112016-12-09T16:13:36ZDebbie Lockettdebbie@saxonica.com
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Bug fix applied in the Saxon-JS 0.9.1 beta release.</p> SaxonJS - Bug #3012: In browser, do not always produce HTML elements in result documents when they should be producedhttps://saxonica.plan.io/issues/3012?journal_id=97622017-08-09T17:56:04ZCommunity Adminsupport@saxonica.com
<ul><li><strong>Fixed in JS Release</strong> set to <i>Saxon-JS 0.9.1</i></li><li><strong>Applies to JS Branch</strong> <i>0.9</i> added</li><li><strong>Fix Committed on JS Branch</strong> <i>0.9</i> added</li></ul>