Very good point. I'm using Next.js link components but handling the dual target behavior with JS click handlers, which does indeed break native browser behavior.
You're right that this should be:
- Proper <a href> for the card wrapper
- Nested <a href> for the source link
- Let the browser handle ctrl+click, middle-click, etc.
Will add this to the refactor list right away. Thank you for the detailed breakdown this is exactly the kind of extra eyes and explanation I need!
You're right that this should be: - Proper <a href> for the card wrapper - Nested <a href> for the source link - Let the browser handle ctrl+click, middle-click, etc.
Will add this to the refactor list right away. Thank you for the detailed breakdown this is exactly the kind of extra eyes and explanation I need!