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

Bugfix: specify monospace font explicitly. #3259 #3260

Conversation

fukusuket
Copy link

@fukusuket fukusuket commented Jan 31, 2024

What Changed

Evidence

Enviroment

  • OS: macOS Sonoma version 14.2.1
  • Velociraptor: 0.7.1

Test(Google Chrome)

I run the steps to reproduce #3259 and confirmed that the issue was resolved as follows.
スクリーンショット 2024-02-01 5 59 58

Test(Firefox)

スクリーンショット 2024-02-01 6 05 34

Test(Safari)

スクリーンショット 2024-02-01 6 10 09

Thank you for your time.
Best,

@fukusuket
Copy link
Author

Enviroment

  • OS: Windows11
  • Velociraptor: 0.7.1

Test(Google Chrome)

chrome

Test(Microsoft Edge)

ms

@fukusuket fukusuket changed the title fix: specify monospace font explicitly. #3259 Bugfix: specify monospace font explicitly. #3259 Jan 31, 2024
@@ -141,6 +141,10 @@ body.ncurses {
font-size: var(--font-size-base) !important;
}

.ncurses .ace_editor, .ace_editor * {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably we dont want to add to this file since this is only for the ncurses theme.

The font family is already set in the theme file for example

--font-family-monospace: "Iosevka Term", Iosevka-Term, SFMono-Regular, Menlo, Monaco,

We actually include fonts already so the browser should not need to fall back to system fonts at all.

Can you please check if you see the same problem in all themes and then use the dev console to check what font is actually loaded at the position of the caret?

@scudette
Copy link
Contributor

scudette commented Feb 1, 2024

This issue is now fixed in #3262 so closing this PR

@scudette scudette closed this Feb 1, 2024
@fukusuket fukusuket deleted the fix-wrong-cursor-position-in-editor branch February 1, 2024 11:54
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.

Wrong cursor position Create a new artifact editor in Chrome(on macOS)
2 participants