github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-07-16 06:42:23 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

URL input box appears at incorrect position from both top and inline toolbars #2435

New Issue
Closed
opened 2026-03-22 14:07:26 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-03-22 14:07:26 -05:00
Owner
Copy Link

Originally created by @Plong-Wasin on GitHub (Nov 28, 2025).

Description

When clicking the "Insert Link" button, whether from the top toolbar of the editor or the inline toolbar that appears upon text selection, the URL input box shows up at an incorrect position. It does not appear near the selected text or in relation to the toolbar button clicked.

This positioning issue occurs both when the editor is at the top of the page and after scrolling down. The URL input box may appear detached from the selection area, floating in unrelated areas such as further up the page, making it hard to use.

Steps to reproduce:

  1. Using the top toolbar:

    • Open the task description editor.
    • Select some text.
    • Click the “Link” button in the top toolbar.
    • Observe that the URL input box appears in an incorrect position.

  2. Using the inline toolbar:

    • Select some text in the editor.
    • Wait for the inline toolbar to appear.
    • Click the “Link” button on the inline toolbar.
    • The URL input box again appears improperly positioned, similarly detached from the relevant text or toolbar.

This occurs regardless of whether the page is scrolled or not.

Expected behavior:
The URL input box should appear close to either the text selection or the toolbar button clicked, maintaining correct positioning regardless of scrolling.

Actual behavior:
The URL input box floats away from the selected text and toolbar, often appearing near the top or elsewhere on the page, causing a confusing and inconvenient user experience.

Vikunja Version

v1.0.0-rc2-297-0b0928e2

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

https://github.com/user-attachments/assets/85eec714-edc3-4e9b-9318-b6a10fd7d1e6

Originally created by @Plong-Wasin on GitHub (Nov 28, 2025). ### Description When clicking the "Insert Link" button, whether from the top toolbar of the editor or the inline toolbar that appears upon text selection, the URL input box shows up at an incorrect position. It does not appear near the selected text or in relation to the toolbar button clicked. This positioning issue occurs both when the editor is at the top of the page and after scrolling down. The URL input box may appear detached from the selection area, floating in unrelated areas such as further up the page, making it hard to use. Steps to reproduce: 1. Using the top toolbar: - Open the task description editor. - Select some text. - Click the “Link” button in the top toolbar. - Observe that the URL input box appears in an incorrect position. 2. Using the inline toolbar: - Select some text in the editor. - Wait for the inline toolbar to appear. - Click the “Link” button on the inline toolbar. - The URL input box again appears improperly positioned, similarly detached from the relevant text or toolbar. This occurs regardless of whether the page is scrolled or not. Expected behavior: The URL input box should appear close to either the text selection or the toolbar button clicked, maintaining correct positioning regardless of scrolling. Actual behavior: The URL input box floats away from the selected text and toolbar, often appearing near the top or elsewhere on the page, causing a confusing and inconvenient user experience. ### Vikunja Version v1.0.0-rc2-297-0b0928e2 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots https://github.com/user-attachments/assets/85eec714-edc3-4e9b-9318-b6a10fd7d1e6
GiteaMirror commented 2026-03-22 14:07:27 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Dec 3, 2025):

Does this only happen when you scroll?

@kolaente commented on GitHub (Dec 3, 2025): Does this only happen when you scroll?
GiteaMirror commented 2026-03-22 14:07:27 -05:00
Author
Owner
Copy Link

@vikunja-bot-app[bot] commented on GitHub (Dec 10, 2025):

This issue has been fixed in #1963, please check with the next unstable build (should be ready for deployment in ~30min, also on the demo).

@vikunja-bot-app[bot] commented on GitHub (Dec 10, 2025): This issue has been fixed in #1963, please check with the next unstable build (should be ready for deployment in ~30min, also on [the demo](https://try.vikunja.io)).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#2435
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?