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

Formatting of Headings broken with new Tables #848

Closed
amc-corey-cox opened this issue Oct 11, 2024 · 8 comments · Fixed by #858
Closed

Formatting of Headings broken with new Tables #848

amc-corey-cox opened this issue Oct 11, 2024 · 8 comments · Fixed by #858
Assignees

Comments

@amc-corey-cox
Copy link
Collaborator

In #775 - we somehow broke the formatting of the headers. I've undeleted the branch issue-734-all-association-sections and added a comment to the PR.

I'm looking into the specific line that causes the problem.

@amc-corey-cox
Copy link
Collaborator Author

The commit where the issue appears to have occurred is: c1dca62

@ptgolden
Copy link
Member

The issue is that text-align is being set twice for heading elements that are children of AppSection components. Once in the global CSS settings:

h1 {
width: 100%;
margin: 0;
padding: 10px 0;
font-weight: 600;
font-size: 1.5rem;
letter-spacing: 1px;
text-align: left;
/** text-transform: uppercase; */
}
h2 {
width: 100%;
margin: 0;
padding: 10px 0;
font-weight: 500;
font-size: 1.3rem;
text-align: left;
}
h3 {
width: 100%;
margin: 0;
margin-bottom: -20px;
padding: 10px 0;
font-weight: 500;
font-size: 1.1rem;
text-align: left;
}

And then again in the AppSection container:

&.center {
align-items: center;
gap: 40px;
text-align: center;
}
&.left {
align-items: flex-start;
gap: 20px;
text-align: left;

Because the former's specificity is higher, it is being used. The solution is to take text-align out of the heading elements in the global CSS, because they are not always left aligned.

@ptgolden
Copy link
Member

The place where those changes were made is 2c878e8

@ptgolden
Copy link
Member

Ooops, specifically 4ae405b. In any case, if headings can be aligned multiple ways, then they their alignment probably shouldn't be defined globally.

@ptgolden
Copy link
Member

Fixed in fe08db5

@ptgolden
Copy link
Member

In #775 - we somehow broke the formatting of the headers. I've undeleted the branch issue-734-all-association-sections and added a comment to the PR.

Since the PR is merged, it's not possible to add commits to it anymore on the issue-734-all-associations-sections branch. Happy to make a new PR.

@amc-corey-cox
Copy link
Collaborator Author

amc-corey-cox commented Oct 11, 2024

I think we should make a new PR. - You may want to start from main or merge in main in order to make the PR a little more sane.

@amc-corey-cox
Copy link
Collaborator Author

Oh, it looks like you may have already started from main. When you make the PR, I recommend you add Kevin as the reviewer just so he can see what was going on.

kevinschaper pushed a commit that referenced this issue Oct 22, 2024
### Related issues

- Closes #848 #856

### Summary

Removes global style changes done in the process of creating the new
node overview page.

### Checks

- [ ] All tests have passed (or issues created for failing tests)
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 a pull request may close this issue.

2 participants