The DOM ends up being correct here, but we end up showing "bar" twice. Peterv, the sink context stack n' all that must not be flushed/synced properly here, wanna have a look?
Forgot to mention: selecting the second "bar" with the mouse actually selects the first "bar".
Mass-reassigning bugs to email@example.com
So the problem, imo, is that the sink's treatment of notifications is just totally whacked. In particular, it assumes that if it's not in a script then any notifications that are generated are caused by itself. This is patently incorrect if another window/frame accesses the DOM during parsing (as here). (And why exactly does the sink not call BeginUpdate itself? Not quite clear on what the deal is there...)
15 years ago
Comment on attachment 121069 [details] [diff] [review] This fixes this bug for me... Hmm, this seems strangely correct to me, but it still scares me a bit (knowing how many regressions we've had from messing with this code over the years). sr=jst