I agree with you. The problem is the bug presents itself **_after_** the fragment is appended. It is **_after_** it is appended that the `selectedIndex` of `node` is forced to the last element in the fragment. `addHTML` is the only time in which we have access to the `node` variable, and thus are able to reset its `selectedIndex` property (other than in `Node#_insert`, which is in a completely different module).

So, sure, we could have a feature test detecting whether this bug occurs, but the "fix" would still have to set the `selectedIndex` property of `node` inside of `addHTML`, and in turn, do the same amount of work we are doing now, if not more. 

After studying the `node` and `dom` modules' architecture,  there is literally no where else we can place this fix.

However, I may be wrong. Perhaps @msweeney can hit us with some knowledge.