-
Notifications
You must be signed in to change notification settings - Fork 130
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
Uncaught TypeError: this.textEditor.displayBuffer.getMaxScrollTop is not a function #387
Comments
Thanks for keeping an eye on this, @Alchiadus. @abe33: the method in question was not part of the public API (and wasn't either present in I am not sure this ought to be included in the public API, but maybe it should. What do you think? |
That was a bold move...
Raised when moving a file by drag and drop to another pane. Another one is raised from the wrap guide package:
I'll make sure the patch won't be available for the current Atom version, cause it'll probably breaks with versions before the deprecations |
I should probably have emphasized this more but, if you want to keep compatibility for both versions, you can use methods on Please, note that they will be deprecated at some point, so you should probably switch to Thanks, @abe33. |
I'm trying to figure how to get rid of all the deprecations, but it has a major impact on the minimap behavior. Properties that were available even when the text editor was not in the DOM are no longer available, etc... I don't know how long it will take to fix all the broken specs... |
A quick update, the |
@abe33 You can just bump the target atom version instead of waiting for a release. |
@steelbrain sadly not. |
Ok, so I reverted many changes and published a new version with an adapter layer to handle the differences, let me know if it fixes things for you. |
Looks like most people with this issue confirmed the latest version fix these errors, I'm closing this issue then. |
1.1.0 is now out and this error now appears 😄 |
yep 😒 error information: https://gist.github.com/M4GNV5/b15b87d02c29f3658d12 |
reopen please. EDIT: |
I just opened Atom I typically use the latest master of Atom, so that is how I got the minimap update, but the engines field hasn't changed so everyone should be receiving the update? |
v4.15 engine field is no longer restricted to > 1.0.19 so yes they should get the update (but they should also have been notified of v4.14 as well as its engine field should match 1.1) |
Just checked and I had an old version of the plugin, sorry On 30 October 2015 at 10:05, Cédric Néhémie [email protected]
|
same for me, updating to |
Please reopen: EDIT: apparently restarting everything fixed it (despite having done so already). strange. |
@peterfraedrich Yeah, it's a recurring problem with custom elements, as you can't unregister them, if a change is made in an update, the updated version won't be able to register (as one is already registered), leading to this kind of nasty behaviour. I think the Minimap will have to move on a new version without custom elements to definitely get rid of these issues. |
@bencasalino Not sure to understand what you mean? What is your problem? |
nvm i figured it out thanks tho, ty!!!
|
[Enter steps to reproduce below:]
Atom/master
. At leastf17767a
or newer.DisplayBuffer::getMaxScrollTop
is removed in this PR: atom/atom#8905Atom Version: 1.2.0-dev-e9a8646
System: Microsoft Windows 10 Pro Insider Preview, Build 10547
Thrown From: minimap package, v4.13.4
Stack Trace
Uncaught TypeError: this.textEditor.displayBuffer.getMaxScrollTop is not a function
Commands
Config
Installed Packages
The text was updated successfully, but these errors were encountered: