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

[AccessibleAccordion] does not support section variations for themes #1195

Closed
fabiofranzini opened this issue Apr 28, 2022 · 1 comment · Fixed by #1205
Closed

[AccessibleAccordion] does not support section variations for themes #1195

fabiofranzini opened this issue Apr 28, 2022 · 1 comment · Fixed by #1205
Labels
type:enhancement New feature or enhancement of existing capability
Milestone

Comments

@fabiofranzini
Copy link
Collaborator

Category

[X] Enhancement
[ ] Bug
[ ] Question

Version

Please specify what version of the library you are using: [3.7.2]

Expected / Desired Behavior / Question

Support section theme variations in SharePoint and/or apply a custom theme to the control

Observed Behavior

The AccessibleAccordion control does not support theme variations for page sections as it uses CSS for styles and therefore is unable to apply a Theme object to the control itself.

Steps to Reproduce

Use the AccessibleAccordion control in a Web Part that supports section variations and change the theme applied to the section.

@ghost
Copy link

ghost commented Apr 28, 2022

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

@ghost ghost added the Needs: Triage 🔍 label Apr 28, 2022
@AJIXuMuK AJIXuMuK added type:enhancement New feature or enhancement of existing capability and removed Needs: Triage 🔍 labels May 2, 2022
@AJIXuMuK AJIXuMuK added this to the 3.8.0 milestone May 2, 2022
@AJIXuMuK AJIXuMuK mentioned this issue May 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:enhancement New feature or enhancement of existing capability
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants