microsoft / microsoft/AdaptiveCards
[Adaptive Cards- Designer - Host App Docs]: 'Redo' functionality is not working.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2k
- Forks
- 595
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 1
Description
Target Platforms
Other
SDK Version
1.5
Application Name
Adaptive Cards
Problem Description
Test Environment:
OS Version: 21H2 (OS build 22000.318)
Browser Version: 105.0.1300.0 (Official build) dev(64-bit)
URL: Adaptive Cards
Repro Steps:
- Launch the URL: Adaptive Cards
- Navigate to header control ‘Designer’ using tab key and activate it through enter key.
- Navigate to the ‘CARD PAYLOAD EDITOR’ and edit the code.
- Navigate to the ‘Undo’ button using tab key and activate it using ‘Enter’ key.
- Observe whatever the changes user made to the code got deleted.
- Navigate to the ‘Redo’ button using the tab key and Activate it with ‘Enter’ key.
- Observe the issue.
Actual Result:
After Activating of ‘Redo’ button there are no changes in the ‘Card Payload Editor’.
Expected Result:
After Activating ‘Redo’ button the changes which has been deleted with ‘undo’ button activation should appear in the ‘Card Payload Editor’.
User Experience:
users will be impacted to use the functionality of the control if ‘Redo’ button is not functional.
"Have feedback to share on Bugs? Please help fill Trusted Tester Bug Feedback (office.com)”
Screenshots
Card JSON
NA
Sample Code Language
NA
Sample Code
NA
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Adaptive Cards website's Designer and reproduce the keyboard flow through the Card Payload Editor, Undo, and Redo controls. Trace the Designer implementation from the reproduced failure; done means changes removed by Undo reappear when Redo is activated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100