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

As a Managed Package does HEDA prevent the conversion of a Classic app to a Lightning app? #735

Open
jacebryan opened this issue Mar 7, 2019 · 2 comments
Labels
accepted Internal SFDO WI has been created Customer Reported Reported in the Hub Investigation Needs more information before work can begin and/or continue

Comments

@jacebryan
Copy link

Note: FOR INTERNAL USE ONLY. For support questions, please use the HEDA Chatter group in The Power of Us Hub.
For feature requests, please use the Ideas tab in The Power of Us Hub.

  • Do you want to request a feature or report a bug?

INVESTIGATION

  • What is the current behavior?

Salesforce out of the box allows a customer to “convert” a Classic app to a Lightning app. Since HEDA is in a managed package, this may be preventing a customers ability to convert a Classic app to a Lightning app.

  • What is the expected behavior?

HEDA does not prevent a customer from converting a classic app to a Lightning app.

  • What is the motivation / use case for changing the behavior?

Issue discussed in a Hub post

  • Acceptance Criteria

    • Given: I am on a certain page
    • When: I click a button
    • Then: An action should occur
  • Keyboard Acceptance Criteria

    • Given: I am navigating the site using only my keyboard
    • When: I tab to the button
    • Then: I should see the button highlighted on focus
    • And When: I press enter on a highlighted button
    • Then: An action should occur
  • Screenreader Acceptance Criteria

    • Given: I am using a screenreader to navigate the site
    • When: I tab to the button
    • Then: I should hear the label of the button
    • And When: I press enter
    • Then: I should hear that an action has occurred
@jacebryan jacebryan added Investigation Needs more information before work can begin and/or continue Customer Reported Reported in the Hub accepted Internal SFDO WI has been created labels Mar 7, 2019
@jacebryan
Copy link
Author

**lurch: add

@LurchTheButler
Copy link

Tracking W-031738

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted Internal SFDO WI has been created Customer Reported Reported in the Hub Investigation Needs more information before work can begin and/or continue
Projects
None yet
Development

No branches or pull requests

2 participants