Vuetify: [Bug Report] Autofocusing processing was blocked

Created on 2 Jan 2020  路  4Comments  路  Source: vuetifyjs/vuetify

Environment

Vuetify Version: 2.2.0
Vue Version: 2.6.11
Browsers: Chrome 79.0.3945.88
OS: Windows 7

Steps to reproduce

Have an autofocusing text field.

Expected Behavior

No console message saying it was blocked.

Actual Behavior

In a normal site: "Autofocus processing was blocked because a document already has a focused element."
In CodePen: "Blocked autofocusing on a form control in a cross-origin subframe."

Reproduction Link

https://codepen.io/teellcory/pen/PowOZJe

Other comments

It seems like it's triggering twice on the same element, hence the message, since there is only one autofocus in the page. It does not prevent the autofocus from working, though.

VTextField low bug upstream wontfix

Most helpful comment

Vue has designated this as something they can't resolve. We will take on the same opinion. We aren't going to be the only people having this issue so I assume it will be treated as a Chrome bug and resolved as such.

If you have any additional questions, please reach out to us in our Discord community.

All 4 comments

This must be something new in chrome, otherwise it would have come up a long time ago鈥攖his persists all the way back to v1.5.

I found this, not sure if it pertains https://www.chromestatus.com/feature/5654905853313024

It looks like Chrome is parsing the raw vuetify tag's autofocus, then vuetify is implementing it as it always has, which causes a double attempt. Do you think it would be best if vuetify were to change it to "autofocused" or something along those lines, to not conflict?

I believe this is an upstream issue: https://codepen.io/johnjleider/pen/oNgoYda

I've filed a report for now: https://github.com/vuejs/vue/issues/10976

Vue has designated this as something they can't resolve. We will take on the same opinion. We aren't going to be the only people having this issue so I assume it will be treated as a Chrome bug and resolved as such.

If you have any additional questions, please reach out to us in our Discord community.

Was this page helpful?
0 / 5 - 0 ratings