dobidi / logseq-bidi Goto Github PK

Popups (from hovering links to pages) don't enjoy the bidi support of this plugin.

In many cases, the content under a block follows the same direction of the root block.

Applying the bidi to the root block has these advantages:

• Better UX when adding sub-blocks in different direction (in most of the cases)
• Better performance because of less processing

We can add an option in the setting for applying bidi to the whole tree. Maybe we can call it greedy.

The opened pages on the sidebar don't benefit from this project.

See screenshot for illustration.

• When using the default labels NOW/LATER, it reverts the block to LTR.
• When using the label DONE, it stays RTL.

Ideally, the plugin disregards NOW/LATER when it parses them and doesn't count them as the first strong character.

Hi,

The correct behaviour is when the block is LTR:

1. CMD + left arrow = Home (move cursor to start of block)
2. CMD + right arrow = End (move cursor to end of block)
3. OPT + left arrow = move cursor one word backwards
4. OPT + right arrow = move cursor one word forwards

However, when the block is in RTL mode, this doesn't work.

Ideally, this will be implemented similarly to the LTR behaviour, but with the arrows switched, i.e.:

1. CMD + left arrow = End (move cursor to end of block)
2. CMD + right arrow = Home (move cursor to start of block)
3. OPT + left arrow = move cursor one word forwards
4. OPT + right arrow = move cursor one word backwards

@ahangarha, I would be happy to tip money to have this implemented

In RTL text, pressing the left/right arrow keys moves the cursor in the opposite direction.

I am writing to express my sincere gratitude for your work on the logseq-bidi extension. As a user who frequently writes in right-to-left languages, this extension has significantly improved my experience with Logseq.
Before discovering your extension, I was struggling with the lack of native right-to-left support in Logseq. Your extension has effectively addressed this issue, making it much easier for me to take notes in my native language.
Your work is greatly appreciated. Please keep up the excellent work!

Add an optional setting for fixing padding/margin styles for RTL content.

It should be optional so that it doesn't affect custom themes.

Some of the mutations are not HTML elements. as a result we get several of the following errors in the console:

caught TypeError: t.querySelectorAll is not a function