-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
t.getStyle is not a function when dragging a list #12723
Comments
Hi dpapala, Thanks for bringing this issue to our attention. I tried reproducing it on my end but wasn't able to do it. Could you provide us with more detailed steps on how to recreate the issue? I know that you mentioned that the error appears irregularly but maybe you noticed some pattern when it occurs? Is it just this one particular list that is problematic? And if so, could you paste it in this conversation retaining its formatting? And could you tell us what build of our editor you're using? Is it a custom version built from source or maybe it's one of our predefined builds? |
@mabryl It is a custom build. |
Resurrecting this thread because thanks to a report from one of our customers I found a way to more consistently reproduce this issue. Firstly, the It looks like the editor doesn't like the fact that the Not exactly sure how it's related to the dragging issue that @dpapala initially reported but it's possible that somehow the |
Thanks, @mabryl! Most likely, this issue won't be picked up, as we have #14632 in the pipeline that should finish soon. I highly recommend switching to the Document list, as this will be our main list implementation. |
π Provide detailed reproduction steps (if any)
β Actual result
The console error
This the function that is called
getAttributeOnUpcast( listParent ) { return listParent.getStyle( 'list-style-type' ) || DEFAULT_LIST_TYPE; }
in listpropertiesediting.js
This error comes periodically not every time that I drag and drop the same list.
π Other details
If you'd like to see this fixed sooner, add a π reaction to this post.
The text was updated successfully, but these errors were encountered: