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

CMD+click does not open a tab #609

Open
petarmarj opened this issue Oct 12, 2023 · 6 comments
Open

CMD+click does not open a tab #609

petarmarj opened this issue Oct 12, 2023 · 6 comments
Labels
bug Something isn't working

Comments

@petarmarj
Copy link

Bug Description

Since one of the more recent updates, users can no longer use the established shortcut CMD/CTRL+click to open an article in a new tab.

Expected Behaviour

CMD/CTRL+click opens link in new tab.

Steps to reproduce

CMD/CTRL+click on a teaser on the front. The article opens in the same frame.

Environment

Chrome

Version

Concerns Chrome and Firefox, version-independent, as dependent on implemented Javascript handling.

@petarmarj petarmarj added the bug Something isn't working label Oct 12, 2023
@manuelmeister
Copy link

This is a degradation of accessibility. 🙁

@manuelmeister
Copy link

You could just wrap the image in anchor tags (more like a secondary click area).

@petarmarj
Copy link
Author

I cannot confirm that CMD+click on the title wrapped in an a-tag in the current state brings the desired effect. Just tested with Firefox 118.0 (64-bit) on MacOS 10.15.7 (19H2026). A quick google tells me that <Link passHref><a>...</a></Link> could fix this - but I have no idea about NextJS. Please don't hit me up if it's wrong.

@trm217 trm217 self-assigned this Oct 13, 2023
@manuelmeister
Copy link

@trm217 where is the template/schema for the teaser?

@petarmarj
Copy link
Author

Well, then I'll see what possibilities I have as a subscriber to create the appropriate resources for you. I'm sure I'll find some say if it doesn't work here via Github.

@jstcki
Copy link
Contributor

jstcki commented Oct 20, 2023

I believe we've been relying on a behavior of next.js' Link component that doesn't seem to work anymore (i.e. attaching an onClick handler on any element that's wrapped inside – not just links). There are better (CSS-only) solutions but getting this right is a bit more involved:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants