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

Expansion Panel default slotted element should be displayed as block element. #1401

Closed
didimmova opened this issue Sep 25, 2024 · 0 comments · Fixed by #1415 or IgniteUI/igniteui-angular#14855
Assignees
Labels
bug Something isn't working expansion-panel

Comments

@didimmova
Copy link
Contributor

Which component(s) are affected?

Expansion panel

Description

When you use the default slot of the expansion panel with an inline element (span for example), the text isn't flowing properly. There should be a style added to make any slotted element in the default slot a block element.

Here's the issue with the span element:
Screenshot 2024-09-25 at 14 35 17

And here's how it looks like if you use "display: block" for it:
Screenshot 2024-09-25 at 14 39 28

Reproduction

  1. Open the expansion panel sample
  2. Use an inline element (for example span) to slot the text in the default slot.
  3. See how it speads more than it should.

Workaround

All slotted elements in the default slot should use the "display: block" style.

Is this a regression?

No or unsure. This never worker, or I haven't tried before.

Affected versions

5.0.1

Browser/OS/Node environment

Tested on Chrome, probably the problem is present in all browsers.

@didimmova didimmova added bug Something isn't working 🆕 status: new The issue is new and will be reviewed when somebody picks it up. expansion-panel labels Sep 25, 2024
@SisIvanova SisIvanova assigned SisIvanova and unassigned simeonoff Oct 1, 2024
@SisIvanova SisIvanova removed the 🆕 status: new The issue is new and will be reviewed when somebody picks it up. label Oct 1, 2024
@SisIvanova SisIvanova linked a pull request Oct 1, 2024 that will close this issue
14 tasks
@SisIvanova SisIvanova linked a pull request Oct 2, 2024 that will close this issue
14 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment