This is a simple test to see if SELECT lists in chrome support nested optgroups. Answer is "no", but I had expected/hoped dom structure would be intact. Instead, chrome rewrites the dom to appear as though nested optgroup were declared immediately following the parent optgroup.
For this reason, the select2 widget also can't handle nested optgroups, as it builds it's structure off by trolling the select dom node.