On Tue, Aug 6, 2013 at 4:47 PM, Adam Klein wrote:
> On Tue, Aug 6, 2013 at 4:38 PM, Jonas Sicking wrote:
>> On Tue, Aug 6, 2013 at 4:27 PM, Adam Klein wrote:
>>> On Tue, Aug 6, 2013 at 4:21 PM, Jonas Sicking wrote:
>>>> As I recall it (it was ages since I dea
On Tue, Aug 6, 2013 at 4:38 PM, Jonas Sicking wrote:
> On Tue, Aug 6, 2013 at 4:27 PM, Adam Klein wrote:
>> On Tue, Aug 6, 2013 at 4:21 PM, Jonas Sicking wrote:
>>> As I recall it (it was ages since I dealt with this), the tricky case
>>> that you need to handl
mpat. The only one I'm asking to change is the
case when the and end up in different trees.
> On Tue, Aug 6, 2013 at 2:01 PM, Adam Klein wrote:
>> Hixie opened my eyes last week to parser-association behavior of the
>> sort found at
>> http://software.hixie.ch/utilities
On Tue, Aug 6, 2013 at 4:09 PM, Ryosuke Niwa wrote:
>
> On Aug 6, 2013, at 2:01 PM, Adam Klein wrote:
>
>> Hixie opened my eyes last week to parser-association behavior of the
>> sort found at
>> http://software.hixie.ch/utilities/js/live-dom-viewer/?saved=2428
Hixie opened my eyes last week to parser-association behavior of the
sort found at http://software.hixie.ch/utilities/js/live-dom-viewer/?saved=2428.
In that case, an in a detached tree is associated with a
in the main document. This causes badness in WebKit and Blink
because the association betw
e (e.g. checking if an element is in
> a specific scope, popping elements from the stack of open elements
> until an element with the same tag name...)
>
> On Wed, Feb 27, 2013 at 12:39 PM, Adam Klein wrote:
>> Consider the following script:
>>
>> tr = document.createEle
Consider the following script:
tr = document.createElement('tr')
tr.innerHTML = '';
That is, the fragment is parsed with tr as the context element. What
should the generated DOM be? Note that is a "MathML text
integration point", which causes the to be processed not as
foreign content but as a
