Skip to Main Content
Feature Request FR-4989
Product Area Application Builder
Status OPEN

2 Voters

Inconsistent word-selection with Ctrl+Shift+Left in APEX Code Editor

mazin1390 Public
· Aug 16 2026

Expected Behavior

Each Ctrl+Shift+Left Arrow press should extend the selection anchor-to-cursor by exactly one word to the left, using a consistent definition of "word boundary" (matching the behavior in VS Code on the same file/content). The selection should only grow while Shift is held and Left is pressed repeatedly — it should never shrink on a subsequent press of the same key combination.

Current Behavior

• Non-monotonic selection (shrinks instead of extends): With the cursor after a word, one press selects the full token. The very next press of the same shortcut collapses the selection down to just any character, instead of extending further left.
• Inconsistent word-boundary detection within a single identifier: Selecting backward through TB_OPENING_BALANCE stops mid-word (TB_OPENIN|G_BALANCE) rather than at the underscore or the start of the identifier — i.e., the same snake_case identifier is tokenized differently at different points along its length.
• Selection-highlight rendering artifact across line breaks: When the selection is extended backward across a line boundary (from a word back into the end of the previous line), the rendered highlight includes a floating rectangle positioned past the actual end of the line text, not aligned to any real character position.
Shift+Alt+Left Arrow (syntax-aware Shrink Selection) is unaffected and works correctly — this appears isolated to the plain word-extend-selection command, not the selection/rendering engine as a whole.

• Product/Component: APEX Code Editor (SQL Workshop / Page Designer PL-SQL & SQL code fields)
• APEX version: 26.1
• Browser: [Edge, Chrome]
• OS: Windows
• Comparison editor: VS Code (same machine, same keyboard) — shortcut works correctly there
 

Code Editor Example

https://1drv.ms/v/c/faf75a7f01c44782/IQBJXRY1o9j7QaKRjYOn4UL7AULMtua7cpP8L6pOCreFVzM?e=nJeG8q

This idea is open.

Comments

Comments

  • tduin OP 7 days ago

    I think this is a bug in the code editor in 26.1; it wasn't broken in 24.2. I am facing the same issues!