Skip to content

Conversation

incandesc3nce
Copy link
Contributor

Because

The div > p option in solution.css file is listed as a possible descendant combinator. According to MDN, it is not a descendant combinator, and it actually enforces stricter inheritance between parent and child element relationships, therefore it should not be listed as a possible combinator.

This PR

  • Removes child combinator from the list of possible descendant combinators

Issue

Closes #558

Additional Information

None.

Pull Request Requirements

  • I have thoroughly read and understand The Odin Project Contributing Guide
  • The title of this PR follows the location of change: brief description of change format, e.g. 01-flex-center: Update self check
  • The Because section summarizes the reason for this PR
  • The This PR section has a bullet point list describing the changes in this PR
  • If this PR addresses an open issue, it is linked in the Issue section
  • If applicable, I have ensured that the TOP solution files match the Desired Outcome image

Child combinator is not considered as a descendant combinator, therefore it should not be listed as a possible combinator.
@mao-sz mao-sz merged commit 38a2af2 into TheOdinProject:main Jun 15, 2024
jitu660 pushed a commit to jitu660/css-exercises that referenced this pull request Aug 2, 2024
Child combinator is not considered as a descendant combinator, therefore it should not be listed as a possible combinator.
TeamPlatinum1 pushed a commit to TeamPlatinum1/css-exercises that referenced this pull request Sep 3, 2024
Child combinator is not considered as a descendant combinator, therefore it should not be listed as a possible combinator.
nanafox pushed a commit to nanafox/css-exercises that referenced this pull request Nov 8, 2024
Child combinator is not considered as a descendant combinator, therefore it should not be listed as a possible combinator.
Oussama5379 added a commit to Oussama5379/css-exercises that referenced this pull request Feb 1, 2025
Child combinator is not considered as a descendant combinator, therefore it should not be listed as a possible combinator.
CourtzDee pushed a commit to CourtzDee/css-exercises that referenced this pull request Apr 2, 2025
Child combinator is not considered as a descendant combinator, therefore it should not be listed as a possible combinator.
repo-jr added a commit to repo-jr/css-exercises that referenced this pull request Aug 29, 2025
Child combinator is not considered as a descendant combinator, therefore it should not be listed as a possible combinator.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bug - Foundations exercise 5: Child combinator wrongly labeled as descendant combinator in solution
2 participants