-
Notifications
You must be signed in to change notification settings - Fork 51
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
Unexpected behaviour when using an Icon within ClientOnly fallback #129
Comments
Are you sure this is from Nuxt icon directly and not Nuxt itself? |
Can't tell, but when you remove the Icon from the template, it works |
Could you try with |
Already tried that, it doesn't work either |
Can you create a reproduction with Stackblitz please? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Consider following code for your app:
Expected behaviour when loading the page:
![image](https://private-user-images.githubusercontent.com/57626963/290984155-429415cd-5c77-4a07-8b1f-7c9142c97953.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU2NjA1OTAsIm5iZiI6MTcyNTY2MDI5MCwicGF0aCI6Ii81NzYyNjk2My8yOTA5ODQxNTUtNDI5NDE1Y2QtNWM3Ny00YTA3LThiMWYtN2M5MTQyYzk3OTUzLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA5MDYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwOTA2VDIyMDQ1MFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWRiMjZmMTJhY2ZkYjg1MTZiNGNhM2MwYzRjNTNlMDE3NmY0NmQzYzhhZTk2NzEzYzMxODM3ODAzMTg2ZmVkNjImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.w2cI2SSw3bJ6en1l6XvXxXwjCK9xERj4zWJUQO8evb4)
A big loading spinner, and, when everything is done loading, some normal text, like this:
Instead, you get this:
![image](https://private-user-images.githubusercontent.com/57626963/290984178-6b2a0259-c64c-4298-befa-fd8776488d0e.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU2NjA1OTAsIm5iZiI6MTcyNTY2MDI5MCwicGF0aCI6Ii81NzYyNjk2My8yOTA5ODQxNzgtNmIyYTAyNTktYzY0Yy00Mjk4LWJlZmEtZmQ4Nzc2NDg4ZDBlLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA5MDYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwOTA2VDIyMDQ1MFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTZhYjFmMjQ0MTI4MzIxYWExZjlhM2E3OTcyNjQ3OGFiZjgwMjJhN2QyNTk5YmQwOGUyMWJiMjkwYTY0ZGVkZDQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.q7ILIvCb48yQCMj2bxoRUHu6jqSKBZyFpFe1RNRzFI8)
When you remove the
ref="someRef"
from the content div, it works as expectedThe text was updated successfully, but these errors were encountered: