From this analysis, there are serious problems with Chrome32, and it is unlikely that it will be "rejected" by domestic manufacturers collectively. Moreover, as the world's leading technology company, Google's development process is very rigorous. A version will go through an iterative period of at least 3-4 months from entering the development branch to release (that is, before the official release of Chrome 30, version 32 has entered the development branch), during which a large number of unit tests will be automatically performed every time it is built.
In this way, there is no possibility that domestic browser manufacturers will not follow up the kernel because of Chrome 32 problems.