This is now the second time I'm aware of Google essentially vetoing a technology in favor of performance (MathML being the first). Seeing it happen twice now i

This is now the second time I'm aware of Google essentially vetoing a technology in favor of performance (MathML being the first). Seeing it happen twice now is a little disconcerting. It feels like Google is eschewing a responsibility it has to standards as one of the major browser vendors in favor of its own interests. If CSS Regions are truly a problematic proposal, it should collectively be addressed now during the draft stage to either improve the standard or decide to abandon them.