HideMiniMap switch is not working:
New-UDCodeEditor -Code "Get-Process notepad" -Original "Get-Process code" -Theme 'vs-dark' -Language 'powershell' -Height '200' -Width '100%' -ReadOnly -Id 'codeEditor3' -HideMiniMap 
5e41ce0f-1296-4986-a9ef-15d12ab91808.png
HideMiniMap switch is not working:
New-UDCodeEditor -Code "Get-Process notepad" -Original "Get-Process code" -Theme 'vs-dark' -Language 'powershell' -Height '200' -Width '100%' -ReadOnly -Id 'codeEditor3' -HideMiniMap
@mmorrow
Thank you for reporting this and for including a minimal example and screenshot.
The example you provided gives us a good starting point to test the behavior of `New-UDCodeEditor -HideMiniMap` under controlled conditions.
Could you please confirm the following?
* Exact PowerShell Universal version and build, if available
* Browser and browser version
* Whether you see the same behavior in another browser, if you have already tested it
We will also attempt to reproduce the behavior using your example and compare the editor with and without `-HideMiniMap`.
Once we have the version details and our reproduction results, we can determine the appropriate next step.
Best regards,
Ruben Tapia
Hello mmorrow,
Thank you again for the example. We completed a controlled reproduction using PSU 2026.2.3 and 2026.2.2.
Our testing showed that the actual Monaco minimap is being hidden correctly when `-HideMiniMap` is used. We confirmed this repeatedly in both PSU versions and also repeated the test in Chrome.
The vertical strip still visible on the right side is a different Monaco component. It is the diff overview ruler generated when `-Original` is supplied to `New-UDCodeEditor`. In our tests, the minimap itself had no visible width while the diff overview ruler remained visible.
We also compared 2026.2.3 with 2026.2.2 and observed equivalent behavior, so we did not find evidence of a regression between those versions.
Could you confirm whether the element you are trying to hide is specifically that right-side diff overview ruler shown when using `-Original`?
If so, we can investigate that behavior separately and determine whether PowerShell Universal currently exposes a supported option for controlling that element.
Best regards,
Ruben Tapia