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
It seems there is a bit of discrepancy between Xterm.js's encoding of mouse coordinates and blessed.js's decoding when the coordinate is greater than 127. When the coordinate is greater than 127 (7bits), Xterm.js encodes it using two characters whereas blessed.js assumes just one. Furthermore, Xterm.js uses at most 11 bits for encoding. After changing the limit to 255 in Xterm.js compatibility is restored :)
After reading the spec I am not sure who is right.
I am leaving the 'Details' and 'Step to reproduce' sections blank as I don't think they are relevant here.
Let me know if you need more information,
John.
Details
Browser and browser version:
OS version:
xterm.js version:
Steps to reproduce
The text was updated successfully, but these errors were encountered:
tl;dr: IMO implement the default (works up to coordinates 223; coordinate is always encoded as a single byte even in UTF-8, that is, the stream is not valid UTF-8) and the SGR 1006 mode, forget the other two :)
It seems there is a bit of discrepancy between Xterm.js's encoding of mouse coordinates and blessed.js's decoding when the coordinate is greater than 127. When the coordinate is greater than 127 (7bits), Xterm.js encodes it using two characters whereas blessed.js assumes just one. Furthermore, Xterm.js uses at most 11 bits for encoding. After changing the limit to 255 in Xterm.js compatibility is restored :)
After reading the spec I am not sure who is right.
I am leaving the 'Details' and 'Step to reproduce' sections blank as I don't think they are relevant here.
Let me know if you need more information,
John.
Details
Steps to reproduce
The text was updated successfully, but these errors were encountered: