Issue: Rendering issue in apps like Obsidian

[Fish-Owl]

I use Obsidian to write notes, and I had an issue using KeyType, as suggestions would appear inside of bubbles rather than in-line.
There was also an issue with the scale of the text in the app.

See attached screenshot:

[johnbean393]

@Fish-Owl

Let me look into this.

To be honest, I don't personally use many Electron apps (e.g. Obsidian), so unfortunately my own testing in these apps will be hit and miss. It doesn't help that macOS's Accessibility API isn't great with Electron apps and browsers, so bug smashing in these apps will be difficult and time consuming, and often need per-app testing and intervention..

[slatlasdev]

I have noticed the scaling or positioning is off in other common apps as well.

macOS Chrome Omnibar:

macOS Chrome Google Search:

This is really funny, it thinks Dia's dialog boxes are text input fields for some reason :

I'm finding it really buggy on Confluence in Dia, I think it's something about how the text spans work.

It looks great on macOS Safari:

Even Confluence works a lot better on Safari:

I guess it's really challenging to account for all these different apps, and especially web browsers + random websites, but I thought I'd just report it regardless.

[johnbean393]

@slatlasdev

You caught me! I'm a Safari user myself, so it's no surprise that support is best in Safari.

Dia is notoriously bad with macOS Accessibility API compatibility. Unfortunately, given that the user base is rather limited, I don't think I'll be spending too much time trying to patch Dia support.

The focus for browser support will remain Chrome + Safari.

If you can make a PR to help, I'm happy to take a look and merge it if it works well!

[slatlasdev]

No worries, thanks for being upfront about that.

I'm actually surprised that there would be such a discrepancy between Dia and Chrome, considering the underlying engine is the same. I guess the UI layer is what's different?

For now, I'm giving Cotypist a try (yes, I actually started with your app and went the other way to most people 😅), and I found interestingly it tells me "For inline suggestions, enable Text Metrics in the Dia Accessibility settings.": https://cotypist.app/compatibility#arc-dia - so I guess it does have poorer support.

Giving your app a try as well with that setting enabled, it actually improves the behavior quite a bit.
So maybe it's just a matter of letting your users know to do the same thing?

When does the app decide to use the floating bubble vs inline suggestions?

[DanBennettUK]

Shame issue happens in basically every app for me. Slack, Discord, Edge, Outlook. It's pretty unusable currently due to this.

[johnbean393]

@DanBennettUK

Fix incoming for these Slack and Discord. Will release in the next few days.

[johnbean393]

@slatlasdev

The app uses the floating bubble:

1. For mid-line completions
2. When the coordinates for the ghost text inline suggestions are likely very unreliable

Edit: As part of release 1.3 (5), ghost text inline suggestion placement has been improved for Google Chrome. Feel free to update and test it!

[johnbean393]

@DanBennettUK

The fixes for Slack and Discord have shipped in version 1.3 (5). Feel free to update and test it!