-
Notifications
You must be signed in to change notification settings - Fork 31
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
bug: navigation popoever doesn't follow hovered item #23
Comments
I also notice this issue after the last updates... |
This problem exisit in every version, as it is not caused by shadcn-docs. So it has to be fixed by the radix team. |
Yeah, I mean before you fix #22 the issue doesn't exist. Can you fall back the |
This is in Also, in unovue/shadcn-vue#705 the maintainer mentioned that it is a long lasting issue, not a bug caused by new updates.
|
Interesting...
Before I update today, the problem was not there.
…On Sat, 10 Aug 2024 at 14:29, Tony Zhang ***@***.***> wrote:
Screenshot-2024-08-10_20.24.50.png (view on web)
<https://github.com/user-attachments/assets/14f70502-5810-4f6f-9fde-5701c7f2687b>
This is in 0.4.6, and an old version of radix-vue. I think it never
worked.
—
Reply to this email directly, view it on GitHub
<#23 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOVGVUJKKIW7PITDRWF4EDZQYBUHAVCNFSM6AAAAABMFWXKXCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBRGQ3TENRWHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Zhao MA
*https://beyond-disciplines.com <https://beyond-disciplines.com>*
*"SAVE PAPER - PLEASE THINK BEFORE YOU PRINT!"*
|
Can you share a screenshot of when it working and the package lock at that moment? |
|
lock file too large. You can check it here: |
Are you sure it works? I still can't get it to work, even with the same dep versions. I think we will wait for radix-vue to fix this. |
Yes. This only happens today after I update this repo (for fixing the symbol in the nav bar). I saw radix-vue is targeting this bug for |
The text was updated successfully, but these errors were encountered: