-
Notifications
You must be signed in to change notification settings - Fork 9
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
[Warning] [Vue warn]: Property "style" was accessed during render but is not defined on instance #178
Comments
According to the warning the problem occurs at line 53 of CodepenEdit.vue My guess and according to this Stack overflow the style property is being accessed here but isn't defined in this scope. I will start following this lead to see what I can turn up |
@kikuomax there is no style prop of any kind that is accessible. Is there any logic I am missing here? |
@wesdevpro I do not believe |
They are using |
@wesdevpro It seems |
* fix: remove unnecessary prop `style` causing console warning Hardcode `editors` prop to `101` to keep the current behavior. See: https://blog.codepen.io/documentation/prefill/#:~:text=editors%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3A%20%22101%22%2C%20//%20Set%20which%20editors%20are%20open.%20In%20this%20example%20HTML%20open%2C%20CSS%20closed%2C%20JS%20open Fixes #178
I rewrite the CHANGELOG according to my preference, however we should discuss and establish a minimum guideline for the CHANGELOG. Categorizes the issue #19 as a "Breaking changes". Removes "Fix" prefixes in the "Fixes" section because they look redundant. Writes the issues instead of the solutions in the headlines. Moves the issue #178 to a new category "Fixes (docs)" because it does not matter to the core buefy-next library. Adds the following fixes: - #23 - #257 - #171 (docs)
I rewrite the CHANGELOG according to my preference, however we should discuss and establish a minimum guideline for the CHANGELOG. Categorizes the issue #19 as a "Breaking changes". Removes "Fix" prefixes in the "Fixes" section because they look redundant. Writes the issues instead of the solutions in the headlines. Moves the issue #178 to a new category "Fixes (docs)" because it does not matter to the core buefy-next library. Adds the following fixes: - #23 - #257 - #171 (docs)
Overview of the problem
Buefy version: [0.1.3-decc2c0e9fc94eef0715566892e86655c901ee82]
Vuejs version: [3.3.10]
OS/Browser: Safari/macOS
Description
If we open the documentation pages of Buefy-next, we will see a lot of warnings like the following:
Steps to reproduce
Move to
packages/docs
:cd packages/docs
Start a dev server:
Open
http://localhost:5173
with your browser.Open the JavaScript console on your browser.
Navigate to any component documentation page on your browser.
Expected behavior
No above warnings.
Actual behavior
Got warnings.
The text was updated successfully, but these errors were encountered: