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

UI Position property should be honored for the page Tags ? #145

Open
1 of 2 tasks
cannibalox opened this issue Oct 18, 2024 · 0 comments
Open
1 of 2 tasks

UI Position property should be honored for the page Tags ? #145

cannibalox opened this issue Oct 18, 2024 · 0 comments

Comments

@cannibalox
Copy link

cannibalox commented Oct 18, 2024

Search first

  • I searched and no similar issues were found

What Happened?

currently, if we go to page Tags and click configure Property > UI Position to a non-default setting (different than block-property`, the tags are displayed twice : at the position set by the configuration option and at the end of the block :

image

  • see below using 'below the block`
    image

  • using end of the block :
    image

the behavior when clicking a #tag is different between the tags: #mytag and #mytag.

Reproduce the Bug

go to the page Tags and try different UI Position

Expected Behavior

  • I would expect the default option to be end of the block rather than block perperty , with the current display position :
* my block                                                                #mytag1 #mytag2
  • I would expect UI Position > block property to display the tags inside the block property:
* myblock
      tags: mytag1, mytag2
      prop: my prop
  • and same for the other options

so basically, honor the user configuration, without showing the tags twice (at the endof the block)

alternatively, maybe any #Tag should have the UI Position option that includes inline (which would complement the ctrl enter) ?

Screenshots

No response

Browser, Desktop or Mobile Platform Information

logseq db 20241018 on win11

Additional Context

No response

Are you willing to submit a PR? If you know how to fix the bug.

  • I'm willing to submit a PR (Thank you!)
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

No branches or pull requests

1 participant