Footer displays on the right side of the page instead of at the bottom
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 84/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- css, html, javascript
- Domain
- frontend
Research direction
Start by comparing the footer and .footer rules in app/static/css/custom.css with the footer wrapper in app/templates/base.html, especially in light of commit 4d91ebda. Reproduce the layout on the Home page with the “Create a Deadline” form, then adjust the relevant layout so the footer spans below the content. Done means it appears at the bottom rather than as a right-side panel.
Written by the indexing model from the issue text.
Description
Description
The footer ("Created & Designed by the Student Software Developers Group. Comments? Questions? Concerns? Email Us") renders as a vertical dark panel on the right side of the page instead of spanning the bottom.
Steps to reproduce
- Log in and open the page with the "Create a Deadline" form (Home).
- Observe the footer placement.
Expected behavior
The footer appears at the bottom of the page, below the main content.
Actual behavior
The footer is displayed beside the content, as a dark column on the right edge running the full page height.
Notes
- Likely related to the recent "Remove fixed footer" change (4d91ebda). Check the
footer/.footerrules inapp/static/css/custom.cssand the<footer>wrapper inapp/templates/base.html.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 2
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 1
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from BCStudentSoftwareDevTeam/cas
-
Improve menu selectionPossibly taken @bakobagassas claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
BCStudentSoftwareDevTeam/cas#448 · 1 assignee ·
-
Update ReadMePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
BCStudentSoftwareDevTeam/cas#444 · 2 comments ·
-
Success messages stay on screen and should auto-dismissPossibly taken @zapataa0 claimed this 2 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
BCStudentSoftwareDevTeam/cas#443 · 1 assignee ·
-
Error pages direct user to contact system support, without providing contact information.Possibly taken @baobao1355 claimed this 9 days ago. Opengood first issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
BCStudentSoftwareDevTeam/cas#439 · 1 assignee ·
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
BCStudentSoftwareDevTeam/cas#438 ·
All issues in BCStudentSoftwareDevTeam/cas
Similar issues
-
[guide] AGENTS.md claims the coverage gate, e2e and full lint run on every PR after ADR 0011 focused validationPossibly taken @hivecommons-hive claimed this today. Openagent/guide documentation hive/claimed-by-guide stage/040-covered-by-pr
Difficulty 2/5 1-3 hours Newbie friendliness 81/100
cncf/endusers#2006 · 1 comment ·
Maintainers usually reply within 1 day
-
check:passed feeds:add
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
all-contributors/cli#587 ·
Maintainers usually reply within 1 day
-
RGAA5
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 8 days
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
githubnext/gh-aw-workshop#5157 ·
Maintainers usually reply within 1 day