Can we make Chrome's caret cursor more efficient, so that we no longer have to put up with Safari

Hello guys,
I was thinking—since Apple introduces new bugs with nearly every new Safari or macOS build, it would be much more efficient if I could completely switch to Google Chrome instead of going back and forth between Safari and Chrome. Maybe we could reach out to Google Chrome’s accessibility team to ask if they could implement a feature that allows VoiceOver to follow the caret cursor when caret browsing (activated with F7) is on. That way, we could have a similar experience to what NVDA or JAWS users on Windows have. If that were possible, I’d probably make Chrome my default browser.
Comment your thoughts below. What do you think is the best way to contact Chrome’s accessibility development team?