Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

With canvas, should the line be continuous? #158984

Closed
TylerLeonhardt-alt opened this issue Aug 23, 2022 · 3 comments · Fixed by #162855
Closed

With canvas, should the line be continuous? #158984

TylerLeonhardt-alt opened this issue Aug 23, 2022 · 3 comments · Fixed by #162855
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders terminal-rendering upstream Issue identified as 'upstream' component related (exists outside of VS Code) upstream-issue-fixed The underlying upstream issue has been fixed upstream-issue-linked This is an upstream issue that has been reported upstream verified Verification succeeded
Milestone

Comments

@TylerLeonhardt-alt
Copy link

TylerLeonhardt-alt commented Aug 23, 2022

Testing #158827

using canvas render.

image
Should the line be continuous even though it overlaps the characters?

vs "on":

image

I'm talking about characters like p and q.

@TylerLeonhardt's alt

@Tyriar
Copy link
Member

Tyriar commented Aug 23, 2022

I didn't bother adding this to the canvas renderer as it's the fallback which is primarily for iPad atm, nothing stopping it from working there too though. Should really consolidate the rendering code for webgl and canvas as they mostly do the same thing when drawing the actual characters. xtermjs/xterm.js#4062

@Tyriar Tyriar added feature-request Request for new features or functionality upstream Issue identified as 'upstream' component related (exists outside of VS Code) upstream-issue-linked This is an upstream issue that has been reported upstream terminal-rendering labels Aug 23, 2022
@Tyriar Tyriar added this to the Backlog milestone Aug 23, 2022
Tyriar added a commit that referenced this issue Oct 6, 2022
- Bump copyright year xtermjs/xterm.js#4176
- Share texture atlas cache code between webgl and canvas renderers xtermjs/xterm.js#4170
- Add willReadFrequently to canvas renderer too xtermjs/xterm.js#4169
- Ensure texture atlas comparison uses rgba not object xtermjs/xterm.js#4168
- Create new event with emitter object to simplify code xtermjs/xterm.js#4166
- Define all events and emitters consistently xtermjs/xterm.js#4165
- Inline dirty row service into input handler xtermjs/xterm.js#4163
- Move w objects to $ prefix variables xtermjs/xterm.js#4162

Fixes #158984
Fixes #158874
@Tyriar Tyriar modified the milestones: Backlog, October 2022 Oct 6, 2022
@Tyriar Tyriar added the upstream-issue-fixed The underlying upstream issue has been fixed label Oct 6, 2022
@VSCodeTriageBot VSCodeTriageBot added unreleased Patch has not yet been released in VS Code Insiders insiders-released Patch has been released in VS Code Insiders and removed unreleased Patch has not yet been released in VS Code Insiders labels Oct 6, 2022
@Tyriar Tyriar added bug Issue identified by VS Code Team member as probable bug and removed feature-request Request for new features or functionality labels Oct 24, 2022
@rzhao271 rzhao271 added the verified Verification succeeded label Oct 27, 2022
@rzhao271
Copy link
Contributor

The wavy underline looks off with gpu enabled (first example in the attached screenshot). With the canvas setting, it's not rendered at all.
Different terminal text underline decorations

@github-actions github-actions bot locked and limited conversation to collaborators Nov 20, 2022
lemanschik pushed a commit to code-oss-dev/code that referenced this issue Nov 25, 2022
- Bump copyright year xtermjs/xterm.js#4176
- Share texture atlas cache code between webgl and canvas renderers xtermjs/xterm.js#4170
- Add willReadFrequently to canvas renderer too xtermjs/xterm.js#4169
- Ensure texture atlas comparison uses rgba not object xtermjs/xterm.js#4168
- Create new event with emitter object to simplify code xtermjs/xterm.js#4166
- Define all events and emitters consistently xtermjs/xterm.js#4165
- Inline dirty row service into input handler xtermjs/xterm.js#4163
- Move w objects to $ prefix variables xtermjs/xterm.js#4162

Fixes microsoft#158984
Fixes microsoft#158874
@Tyriar
Copy link
Member

Tyriar commented Dec 1, 2022

The look of curly was going to be revisited in xtermjs/xterm.js#4064

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders terminal-rendering upstream Issue identified as 'upstream' component related (exists outside of VS Code) upstream-issue-fixed The underlying upstream issue has been fixed upstream-issue-linked This is an upstream issue that has been reported upstream verified Verification succeeded
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants