Clicking issues in text area

[L3P3]

• Web Browser: Mypal 29.0.1 (Pale Moon/Firefox)
• Local OS: Windows XP SP3
• Remote OS: Debian 10
• Remote Architecture: x86-64
• code-server --version: 3.9.0 fc6d123

1. When right-clicking in the text area (and only there), the context menu does not appear. Following error is thrown:

  ERR this.shadowRootHostElement.attachShadow is not a function: setContainer@out/vs/workbench/workbench.web.api.js:448:617
setContainer@out/vs/workbench/workbench.web.api.js:1724:79
showContextView@out/vs/workbench/workbench.web.api.js:1724:180
showContextMenu@out/vs/workbench/workbench.web.api.js:2171:372
showContextMenu@out/vs/workbench/workbench.web.api.js:2524:362
_doShowContextMenu@out/vs/workbench/workbench.web.api.js:2036:481
showContextMenu@out/vs/workbench/workbench.web.api.js:2035:614
_onContextMenu@out/vs/workbench/workbench.web.api.js:2035:347
e/<@out/vs/workbench/workbench.web.api.js:2034:213
fire@out/vs/workbench/workbench.web.api.js:99:694
_createView/i.onContextMenu@out/vs/workbench/workbench.web.api.js:2357:766
emitContextMenu@out/vs/workbench/workbench.web.api.js:2215:957
emitContextMenu@out/vs/workbench/workbench.web.api.js:2007:54
_onContextMenu@out/vs/workbench/workbench.web.api.js:2202:979
p/<@out/vs/workbench/workbench.web.api.js:2201:318
onContextMenu/<@out/vs/workbench/workbench.web.api.js:479:433

2. When clicking on empty lines, nothing happens (cursor does not jump to that line), no error is thrown. Clicking on lines containing text behaves correctly. Is quite annoying, have to always click on nearest populated line and navigate down/up via keyboard.

[jsjoeio]

Hmm... can you provide reproduction steps? I don't have a Windows XP machine around and I haven't used Mypal but willing to try and test on my machine locally.

[L3P3]

The reproduction steps are like this:
Install mypal, open the app, right click in code editor area. 😉

The reason ist obvious to me: Mypal is based on a firefox version older than 63, lacking support of shadow dom.
I see no reason for using shadowDom in vscode anyway, maybe it can be replaced by something older without any issues.
If not, there is at least one polyfill for shadowDom available, it should be fairly easy to integrate that into the app.

[code-asher]

I don't think this is something we'd patch here but rather would be better to raise upstream (but best to see if it replicates in Codespaces first to prove it's an issue for upstream).

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no activity occurs in the next 5 days.