[Feature] Add a control to display a list of metadata #3688
Labels
Milestone
Comments
vgromfeld
added
the
feature request 📬
|
Hello, 'vgromfeld! Thanks for submitting a new feature request. I've automatically added a vote 👍 reaction to help get things started. Other community members can vote to help us prioritize this feature in the future! |
vgromfeld
changed the title
ghost
pushed a commit
that referenced
this issue
Jun 16, 2021
<!-- 🚨 Please Do Not skip any instructions and information mentioned below as they are all required and essential to evaluate and test the PR. By fulfilling all the required information you will be able to reduce the volume of questions and most likely help merge the PR faster 🚨 --> <!-- 📝 It is preferred if you keep the "☑️ Allow edits by maintainers" checked in the Pull Request Template as it increases collaboration with the Toolkit maintainers by permitting commits to your PR branch (only) created from your fork. This can let us quickly make fixes for minor typos or forgotten StyleCop issues during review without needing to wait on you doing extra work. Let us help you help us! 🎉 --> ## Fixes #3688 <!-- Add the relevant issue number after the "#" mentioned above (for ex: Fixes #1234) which will automatically close the issue once the PR is merged. --> Adds a control to display metadata separated by bullets like done in Groove Music or the Store. The metadata list can contain actionable links. **Groove**  **Store**  ## PR Type What kind of change does this PR introduce? - Feature ## What is the new behavior? I've added `MetadataControl`. It aggregates strings and commands separated by bullets ("•" / U+2022) in a `TextBlock`. The commands are represented using `Hyperlink` items. It receives the items to display as `MetadataUnit`s through its `MetadataControl.MetadataUnits` property. ## PR Checklist Please check if your PR fulfills the following requirements: - [x] Tested code with current [supported SDKs](../readme.md#supported) - [ ] Pull Request has been submitted to the documentation repository [instructions](..\contributing.md#docs). Link: <!-- docs PR link --> - [x] Sample in sample app has been added / updated (for bug fixes / features) - [x] Icon has been created (if new sample) following the [Thumbnail Style Guide and templates](https://github.com/windows-toolkit/WindowsCommunityToolkit-design-assets) - [ ] New major technical changes in the toolkit have or will be added to the [Wiki](https://github.com/windows-toolkit/WindowsCommunityToolkit/wiki) e.g. build changes, source generators, testing infrastructure, sample creation changes, etc... - [ ] Tests for the changes have been added (for bug fixes / features) (if applicable) - [x] Header has been added to all new source files (run *build/UpdateHeaders.bat*) - [x] Contains **NO** breaking changes <!-- If this PR contains a breaking change, please describe the impact and migration path for existing applications below. Please note that breaking changes are likely to be rejected within minor release cycles or held until major versions. --> ## Other information 
ghost
locked as resolved and limited conversation to collaborators
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the problem this feature would solve
Some application like Groove or the Store are using a control to display metadata separated by bullets with some of them that can be actionable (navigate to dedicated pages)
Describe the solution
We should add to the toolkit a control that would:
This control will have to be fully accessible. The "default" bullet control is skipped when using screen reader. The control should generate a screen reader compliant representation of its content (replacing the bullet by a coma is usually enough).
The text was updated successfully, but these errors were encountered: