Crash Data

Security

(public)

User Story

Bug 1009628 made it so that removing a child from a deck would update the selected index. However, this is based on whether the frame goes away, which can happen for other reasons, for example causing bug 1131052. For example:
<deck>
<label value="First" onclick="this.removeAttribute('label')"/>
<label/>
</deck>
Clicking on the label will change the frame for the label without removing the node.
Either:
1. nsDeckFrame needs to handle this case.
2. nsDeckFrame should instead store the node instead of the index.
The deck should also be improved to handle insertion of children.