-
Notifications
You must be signed in to change notification settings - Fork 22
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
WC vs. WP external <Link>
s
#984
Comments
TIL: there's a
👍 upvote for this. |
I don't think it was a conscious choice, your suggestion sounds good! 👍 Thanks for checking 😄 |
@ecgan probably has more background but I think there might be have been a gotcha or some preference to do with tracks events |
TIL for me too, didn't notice the
I think that within us WooCommerce ecosystem, we should use the
It has always been that way, as far as I know. Maybe that was how WooCommerce wanted it. We can probably try to implement the icon in
Yeah I agree that the left one is better. The text and icon has the same color, and the click target is bigger.
I agree too. 👍 |
Describe the bug:
I noticed that for external documentation links we use
@woocommerce/components.Link
withexternal
prop, and occasionally add<ExternalIcon>
, then manually tweak it, to look a tad better.I wonder:
@wordpress/components.ExternalLink
?<ExternalIcon>
non-clickable in unsupported countries notice?WordPress
<ExternalLink>
on left, WooCommerce > GLA<AppDocumentationLink /><ExternalIcon />
to the right.Personally, I find the left one more appealing, plus it reduces the style tweaks on our end and just gets it for free from WP. Also, (however without deeper review of all cases), as a user, I, like it when the UI constantly visually marks all external links, so I know, when to expect to be navigated away.
@j111q, @eason9487 Do you have any comments on that?
Additional notes:
The text was updated successfully, but these errors were encountered: