-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
setValue() emits $blockScrolling = Infinity warning #2499
Comments
add config functions, reference https://github.com/ajaxorg/ace/wiki/Configuring-Ace also support $blockscrolling variable; reference ajaxorg/ace#2499
"Automatically scrolling cursor into view after selection change" "this will be disabled in the next version" "set editor.$blockScrolling = Infinity to disable this message" cf. ajaxorg/ace#2499 > [...] I'm calling a documented API, and it's in turn > telling me to call an undocumented one. and angular-ui/ui-ace#104
I'm also interested in why it's being deprecated. |
"Automatically scrolling cursor into view after selection change" "this will be disabled in the next version" "set editor.$blockScrolling = Infinity to disable this message" cf. ajaxorg/ace#2499 > [...] I'm calling a documented API, and it's in turn > telling me to call an undocumented one. and angular-ui/ui-ace#104
For the curious, this seems to be the commit where it was deprecated: 8c1aa5c. Unclear, but I think I saw hints that it is getting replaced with another feature. (We use this feature, but we have to monkey patch our own calculations because (horrors) we are doing the parent-scroll thing.) |
Sticking with Ace 1.1.8 for now because later versions give a funky, poorly documented console warning (ajaxorg/ace#2499)
I am having the same problem, using
If I uncomment the |
This warning was removed several versions ago |
When using setValue(), the following warning is issued:
I'm a bit confused as to what this is trying to tell me, as I'm calling a documented API, and it's in turn telling me to call an undocumented one.
The text was updated successfully, but these errors were encountered: