Any "insiders" have comments on this? Is this the Chrome team just trying to keep pushing forward, or are they technically sticking to the referenced compatibility guidelines they published?
I'm just wondering if there has been a lack of progress with Shadow DOM and their solution is just go-go-go to get things moving.