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

auro-hyperlink: support 'mailto:' protocol handler in 'href' attribute #87

Closed
MattSidor opened this issue Dec 10, 2021 · 0 comments · Fixed by #81
Closed

auro-hyperlink: support 'mailto:' protocol handler in 'href' attribute #87

MattSidor opened this issue Dec 10, 2021 · 0 comments · Fixed by #81
Assignees
Labels
auro-hyperlink Status: Work In Progress Issue or Pull Request work is in Progress Type: Feature New Feature

Comments

@MattSidor
Copy link
Contributor

Is your feature request related to a problem? Please describe.

I would like <auro-hyperlink> to support the mailto: protocol handler in the href attribute so that we can take advantage of the browser's email protocol handler.

Describe the solution you'd like

<auro-hyperlink href="mailto:[email protected][email protected]&[email protected]&subject=The%20subject%20of%20the%20email&body=The%20body%20of%20the%20email">[email protected]</auro-hyperlink> opens the browser's default email client with 'to', 'cc', 'bcc', 'subject', and 'body' lines pre-filled.

Describe alternatives you've considered

There are UX considerations for linking to email handlers like this, so maybe Alaska Air generally does not want to encourage these kinds of links. If this is the case, I think we should document it as part of the component to discourage developers from substituting with vanilla <a> tags.

Additional context

MDN docs on email links: https://developer.mozilla.org/en-US/docs/Learn/HTML/Introduction_to_HTML/Creating_hyperlinks#e-mail_links

@MattSidor MattSidor added the Type: Feature New Feature label Dec 10, 2021
@blackfalcon blackfalcon mentioned this issue Dec 10, 2021
@blackfalcon blackfalcon added auro-hypelrink Status: Work In Progress Issue or Pull Request work is in Progress and removed not-reviewed labels Dec 10, 2021
@blackfalcon blackfalcon added this to the v3.0-rc milestone Dec 10, 2021
blackfalcon added a commit that referenced this issue Dec 10, 2021
Changes to be committed:
modified:   demo/demo.md
modified:   src/component-base.js
modified:   test/auro-hyperlink.test.js
@blackfalcon blackfalcon linked a pull request Dec 10, 2021 that will close this issue
6 tasks
blackfalcon added a commit that referenced this issue Dec 10, 2021
Changes to be committed:
modified:   demo/demo.md
modified:   src/component-base.js
modified:   test/auro-hyperlink.test.js
@settings settings bot removed the auro-hypelrink label Dec 18, 2021
blackfalcon added a commit that referenced this issue Dec 21, 2021
Changes to be committed:
modified:   demo/demo.md
modified:   src/component-base.js
modified:   test/auro-hyperlink.test.js
blackfalcon added a commit that referenced this issue Jan 7, 2022
Changes to be committed:
modified:   demo/demo.md
modified:   src/component-base.js
modified:   test/auro-hyperlink.test.js
blackfalcon pushed a commit that referenced this issue Jan 7, 2022
# [3.0.0](v2.4.3...v3.0.0) (2022-01-07)

### Bug Fixes

* icon CSS/Sass for IE fallback [#72](#72) ([14cebaf](14cebaf))
* remove outline-offset [#79](#79) ([f3ff147](f3ff147))

### Code Refactoring

* **generator migration:** migrate repo to latest gen build [#73](#73) ([543f723](543f723))

### Features

* **mailto:** add support for mailto: http request [#87](#87) ([33ad5fd](33ad5fd))
* **referrer:** add feature for external url referral tracking ([b416a60](b416a60))

### Performance Improvements

* **mdmagic:** update mdmagic watched files ([276b0e9](276b0e9))

### BREAKING CHANGES

* **generator migration:** This commit will move the element to the new
@AuroDesignSystem npm namespace as well redefine legacy API
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auro-hyperlink Status: Work In Progress Issue or Pull Request work is in Progress Type: Feature New Feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants