RaspberryPiFoundation/blockly

Check for duplicates I have searched for similar issues before opening a new one. Description Newly created typescript plugins have "typescript": "^7.0.2" in devDependencies which results in two problems: npm install fails because @blockly/dev-scripts caps TS at ^5 even updating dev-scripts, or installing with --legacy-peer-deps, the ts-loader pacakge does not seem to support version 7 yet (TypeError: Cannot read properties of undefined (reading 'fileExists')). Reproduction steps run npx @blockly/create-package plugin my-plugin --type plugin --typescript see it fail when it tries to install Priority There are two issues here, the fact that @blockly-dev-scripts is capping at TS version ^5, and what seems to be a more critical issue which is ts-loader not supporting TS version 7 (I believe the underlying API has changed). There are two workarounds: Manually modify devDependencies in package.json to TS ^5 Manually modify devDependencies in package.json to TS ^6 and install with --

Check for duplicates I have searched for similar issues before opening a new one. Problem When a block is expanded, if the block overlaps one or more other blocks it makes for a "noisy" interface and a corresponding degraded developer experience. Request I was wondering if an option could be added so that when a block is expanded any blocks that would be overlapped are instead repositioned vertically and/or/horizontally so there is no overlap? Similarly, collapsing a block would result in the vertical/horizontal repositioning of other blocks. Alternatives considered No response Additional context No response

Location https://docs.blockly.com/guides/configure/serialization/#serializer-hooks Type Text Image or Gif Other Suggested content The "Save and Load" doc serialization.mdx claims that workspace comments are not supported by JSON serialization, but support for this was added in #7927 The stale doc should be updated to remove this claim. The following serializer hooks example should also be renamed to something more applicable, since it uses workspace-comments as an example which could be confusing. Additional context No response

Check for duplicates I have searched for similar issues before opening a new one. Description We have been catching up with the behaviour of Page Up / Down and Home / End as we didn't ship this in MakeCode. I think we have found a couple of bugs, but also have thoughts on the behaviour in some areas as well. Bugs When a container end statement position is focused, pressing End moves focus into the previous block's end statement position. In this case, I'd expect End to do nothing at all. Screen.Recording.2026-07-24.at.13.58.01.mov When a container block is focused, pressing End moves focus to the container end statement position, but this position is in the wrong place. It focuses an impossible position between the top inside edge of the container and the top of the statement block inside. This is normally unreachable with Up / Down. Screen.Recording.2026-07-24.at.14.02.30.mov Thoughts on behaviour Sometimes i

Check for duplicates I have searched for similar issues before opening a new one. Description There are no longer commas at the end of block aria-labels. This means NVDA (and probably JAWS) output information as "...has input statement" which might be confusing for some users. VoiceOver automatically places commas between the aria-label and aria-roledescription, so outputs "...has input, statement". Should there be a conditional comma appended to the aria-labels where appropriate based on OS to improve screen reader output? Reproduction steps Priority No response Stack trace Screenshots No response Browsers No response