You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whenever I type an open-parenthesis in a code cell, the cursor gets placed behind the open-paren instead of in front of it. This also occurs with the Matched Brackets setting enabled, placing it behind the matched parentheses instead of between them.
However, this only occurs when typing statements on the top level; inside other parentheses, the cursor gets placed as normal.
See recording for example:
Screen.Recording.2024-02-13.at.4.24.45.PM.mov
Reproduce
Type an open parenthesis ('(') character.
Expected behavior
Cursor should be placed after the parenthesis character.
Do you have the "auto close brackets" setting enabled? Without it enabled, as is the default, I just see ( when I press (, and with it on, I see () with the cursor inside the parentheses when I press (.
The related item suggests you're using Firefox on macOS, which I am as well, although I'm using the ESR version. Do you still see the problem in any other browsers, or if you disable extensions in Firefox?
The related item suggests you're using Firefox on macOS, which I am as well, although I'm using the ESR version. Do you still see the problem in any other browsers, or if you disable extensions in Firefox?
Huh. Yeah, looks like it was caused by the Word Replacer extension I just started using. Looking at the reviews, it seems it has problems with things using React, which would also explain the awful errors I've been getting with Outlook lately. Guess I'll be uninstalling that, which stinks because now I have to sift through the wall of course numbers my college gives me again. Can't be helped, I suppose.
Description
Whenever I type an open-parenthesis in a code cell, the cursor gets placed behind the open-paren instead of in front of it. This also occurs with the Matched Brackets setting enabled, placing it behind the matched parentheses instead of between them.
However, this only occurs when typing statements on the top level; inside other parentheses, the cursor gets placed as normal.
See recording for example:
Screen.Recording.2024-02-13.at.4.24.45.PM.mov
Reproduce
Expected behavior
Cursor should be placed after the parenthesis character.
Context
See #15797.
Logs
JS Console,
troubleshoot
, etc. do not have any notable output.The text was updated successfully, but these errors were encountered: