Closed Ms2ger closed 1 year ago
I think Firefox is correct. At least I can't find a reason why foreignObject
would be popped from the stack of open elements.
@hsivonen @mfreed7?
I've changed my mind. WebKit and Chromium are correct.
Reasoning:
<div>
gets put on the stack<table>
gets put on the stack<svg>
gets foster parented and put on the stack<foreignObject>
gets put on the stack<select>
gets put on the stack<table>
implies </select>
which resets the insertion mode. That walks up the stack until it finds <table>
which sets the insertion mode to "in table". Then <table>
in that mode causes everything up to and including the prior <table>
to be popped from the stack.<s>
gets foster parented.Stepping through the spec I reach the same conclusion.
Chrome: Firefox: Not sure who's right.