Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vite error overlay appears to side of content on live update #9969

Closed
7 tasks done
jez9999 opened this issue Sep 2, 2022 · 0 comments · Fixed by #9971
Closed
7 tasks done

Vite error overlay appears to side of content on live update #9969

jez9999 opened this issue Sep 2, 2022 · 0 comments · Fixed by #9971
Labels
p3-minor-bug 🔨 An edge case that only affects very specific usage (priority)

Comments

@jez9999
Copy link

jez9999 commented Sep 2, 2022

Describe the bug

The Vite error 'overlay', which according to screenshots I can see is supposed to appear on top of the content, is appearing to the side of the content when a live update breaks things.
screenshot

If you then refresh the browser, it appears properly.
screenshot2

Reproduction

Create default Vue.js site and break an import in App.vue

System Info

System:
    OS: Windows 10 10.0.19042
    CPU: (12) x64 Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz
    Memory: 3.89 GB / 15.64 GB
  Binaries:
    Node: 16.15.0 - C:\Program Files\nodejs\node.EXE
    npm: 8.5.5 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.423.0), Chromium (104.0.1293.70)
    Internet Explorer: 11.0.19041.1

Used Package Manager

npm

Logs

No response

Validations

@sapphi-red sapphi-red added the p3-minor-bug 🔨 An edge case that only affects very specific usage (priority) label Sep 3, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Sep 21, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
p3-minor-bug 🔨 An edge case that only affects very specific usage (priority)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants