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

Fallback on default color when linkifier can't find the character #1670

Merged
merged 1 commit into from Sep 9, 2018

Conversation

Tyriar
Copy link
Member

@Tyriar Tyriar commented Sep 8, 2018

This probably doesn't fix the underlying problem, but it will make it
obvious by using the white background color and more easily help identify
the problem case.

Fixes #1669


I suspect it's related translating the string index to the column index.

This probably doesn't fix the underlying problem, but it will make it
obvious by using the white background color and more easily help identify
the problem case.

Fixes xtermjs#1669
@Tyriar Tyriar added this to the 3.8.0 milestone Sep 8, 2018
@Tyriar Tyriar self-assigned this Sep 8, 2018
@jerch
Copy link
Member

jerch commented Sep 8, 2018

Guess we should add this to master for now to get a hold of those broken linkifier attempts. Wasn't able to repro this, all nasty inputs I tried got just silently swallowed.

Edit: You are right about the root of this, see #1669 (comment)

@Tyriar Tyriar merged commit f9717bc into xtermjs:master Sep 9, 2018
@Tyriar Tyriar deleted the 1669_linkifier_exception branch September 9, 2018 14:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Linkifier doesn't handle some unicode strings
2 participants