Skip to content

Keep editor content out of the footer - #43

Open
kevinherron wants to merge 1 commit into
omacom:masterfrom
kevinherron:codex/opaque-status-bar
Open

Keep editor content out of the footer#43
kevinherron wants to merge 1 commit into
omacom:masterfrom
kevinherron:codex/opaque-status-bar

Conversation

@kevinherron

@kevinherron kevinherron commented Aug 30, 2026

Copy link
Copy Markdown

The footer controls and status text currently float over the editor. At some text sizes, document text and the caret remain visible underneath, causing the footer and document content to overlap.

This gives the full-width footer an opaque surface using the active theme background and clips the editor viewport exactly at the footer's top edge. The footer retains a minimum height so its fixed-size controls remain inside the opaque region at the smallest supported desktop text scale.

The save and open controls, status display, word count, theme behavior, text scaling, and search overlay remain unchanged.

Before

footer-before

After

footer-after

Give the status controls their own theme-colored surface and end the
clipped editor viewport at its top edge so document content cannot render
behind the footer.
frivas pushed a commit to frivas/omawrite that referenced this pull request Aug 31, 2026
Resolved by taking our test file and re-adding PR omacom#43's includes and test,
which land at the same insertion point as ours.
frivas pushed a commit to frivas/omawrite that referenced this pull request Aug 31, 2026
It had no anchors at all, so it sat at the footer's origin on top of the save
icon at full opacity while everything around it was muted -- a merge artifact:
PR omacom#45 placed it in a footer that PR omacom#43 had restructured, and neither
conflicted textually so both landed and the button lost its position.

The footer now splits the way the window does: what you can do to the file on
the left, what the document is doing on the right. The icon shows the action
rather than the state -- a pencil while previewing, because that click goes
back to the source -- and it lifts out of the muted group while preview is on,
so the mode is visible without reading anything.
frivas pushed a commit to frivas/omawrite that referenced this pull request Aug 31, 2026
Resolved against PR omacom#43, which had already lifted the viewport to stop at
footer.top: omacom#42's scrollbar padding and inset were for a flickable that ran
underneath the footer, so they would inset it a second time. Its test looked
the viewport up by an objectName omacom#43 renamed.
frivas added a commit to frivas/omawrite that referenced this pull request Aug 31, 2026
Resolved by taking our test file and re-adding PR omacom#43's includes and test,
which land at the same insertion point as ours.
frivas added a commit to frivas/omawrite that referenced this pull request Aug 31, 2026
It had no anchors at all, so it sat at the footer's origin on top of the save
icon at full opacity while everything around it was muted -- a merge artifact:
PR omacom#45 placed it in a footer that PR omacom#43 had restructured, and neither
conflicted textually so both landed and the button lost its position.

The footer now splits the way the window does: what you can do to the file on
the left, what the document is doing on the right. The icon shows the action
rather than the state -- a pencil while previewing, because that click goes
back to the source -- and it lifts out of the muted group while preview is on,
so the mode is visible without reading anything.
frivas added a commit to frivas/omawrite that referenced this pull request Aug 31, 2026
Resolved against PR omacom#43, which had already lifted the viewport to stop at
footer.top: omacom#42's scrollbar padding and inset were for a flickable that ran
underneath the footer, so they would inset it a second time. Its test looked
the viewport up by an objectName omacom#43 renamed.
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.

1 participant