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

Feature: Uncontained Fieldset #14975

Open
wants to merge 12 commits into
base: 4.x
Choose a base branch
from

Conversation

thethunderturner
Copy link
Contributor

@thethunderturner thethunderturner commented Dec 2, 2024

Description

Closes #11355. This has to be discussed with @zepfietje before merging

Visual changes

image
image

Functional changes

  • Code style has been fixed by running the composer cs command.
  • Changes have been tested to not break existing functionality.
  • Documentation is up-to-date.

@danharrin
Copy link
Member

Please check #14968 for how I implemented it in the Section, with the -not- class instead, and using the CanBeContained trait.

@thethunderturner
Copy link
Contributor Author

Please check #14968 for how I implemented it in the Section, with the -not- class instead, and using the CanBeContained trait.

Will do. Thanks

@danharrin
Copy link
Member

The reason I want the -not class is because my philosophy is that an element should have a minimal number of CSS classes to achieve the "default" look, so if someone uses the raw classes instead of the Blade component they can achieve it easier.

@danharrin danharrin added the enhancement New feature or request label Dec 2, 2024
@danharrin danharrin added this to the v4 milestone Dec 2, 2024
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this is right, the code needs to apply if there is :not() this class present. Can you make sure you test it locally please?

Copy link
Contributor Author

@thethunderturner thethunderturner Dec 2, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah you're right. Im still working on it though 😅

Copy link
Member

@danharrin danharrin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add more space between the legend and the content, I think it needs to at least look the same as gap-6

But I would like to hear what Zep's idea was for this, as I don't think I'd ever use an uncontained fieldset

@thethunderturner
Copy link
Contributor Author

Please add more space between the legend and the content, I think it needs to at least look the same as gap-6

But I would like to hear what Zep's idea was for this, as I don't think I'd ever use an uncontained fieldset

Unfortunately gap wont work because we're using the display: block property which prevents gap from having an effect. Instead I used padding-top which in this case I believe has the same result.

@zepfietje zepfietje self-assigned this Dec 3, 2024
@thethunderturner
Copy link
Contributor Author

Hey @zepfietje, is there any update on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: In Progress
Development

Successfully merging this pull request may close these issues.

3 participants