Element Click does not handle situation where the element has no container

[AtkinsSJ]

Getting the container can return undefined (if the element is an <option> without a valid parent), however the algorithm here assumes that it always returns a node which can have events fired on. For example:

5. Scroll into view the element’s container.

1. Let parent node be the element’s container.
2. Fire a mouseOver event at parent node.

Maybe this issue does not come up in practice, but it feels like it should be handled somehow.