No.
Wildcard certs are an important and valuable part of the Web PKI. Google has been supportive in the CA/Browser Forum of expanding the support of wildcard certificates to include EV certificates as well.
In general, discussion about changes to the Web PKI happen:
- In the CA/Browser Forum initially, to solicit wide feedback from CAs on the potential implications and complications
- Within mozilla.dev.security.policy, which provide a forum that allows the public to comment on changes and implications (which the CA/Browser Forum does not permit) and collaborative development amongst browser vendors
- And, should a change be made to deprecate or remove something, on blink-dev@, in the context of an "Intent to Deprecate and Remove" (if removing support for a feature)
In general, the CA/Browser Forum governs what CAs can or cannot issue. mozilla.dev.security.policy similarly reflects discussions related to policies on CA's permitted and unpermitted actions. blink-dev@ represents collaborations on what is supported and not-supported - independent of whether or not a CA is permitted to issue such certificates.
To give a finer point on this - CAs are permitted to issue all manner of certificates with different EKUs, while Chromium only trusts a limited subset of those for purposes of SSL/TLS authentication (namely, id-kp-serverAuth, the any EKU, or lacking an EKU extension entirely).
Does that help address the question?