Actually, we faced this warning because it occurs in Vuetify version 3.6.8. This issue has been fixed in the latest version (3.8.0), so please upgrade Vuetify to the latest version to resolve the problem.