8000 fix(ui): make overflow hidden to fix fitAddon when search bar by simonrey1 · Pull Request #13324 · podman-desktop/podman-desktop · GitHub
[go: up one dir, main page]

Skip to content

Conversation

simonrey1
Copy link
Contributor
@simonrey1 simonrey1 commented Jul 23, 2025

What does this PR do?

Fixes the logs display when there is a search bar.
When resizing the window, there was an issue where the height of the search controls was not taken into account overflowing to the status bar and making logs not visible.

Screenshot / video of UI

Screen.Recording.2025-07-23.at.17.37.15.mov

What issues does this PR fix or reference?

Fixes #13231

How to test this PR?

  • Tests are covering the bug fix or the new feature

Copy link
Contributor
coderabbitai bot commented Jul 23, 2025
📝 Walkthrough

Walkthrough

The update modifies the Svelte component template in two ways: it changes the prop passing for the TerminalSearchControls component to use shorthand syntax, and it adds the overflow-hidden CSS class to the main terminal container <div>. No changes are made to the component's script logic, event handling, or exported/public entities.

Estimated code review effort

1 (~2 minutes)

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

packages/renderer/src/lib/ui/TerminalWindow.svelte

Oops! Something went wrong! :(

ESLint: 9.31.0

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'svelte-eslint-parser' imported from /eslint.config.mjs
at Object.getPackageJSONURL (node:internal/modules/package_json_reader:255:9)
at packageResolve (node:internal/modules/esm/resolve:767:81)
at moduleResolve (node:internal/modules/esm/resolve:853:18)
at defaultResolve (node:internal/modules/esm/resolve:983:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:801:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:725:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:309:38)
at #link (node:internal/modules/esm/module_job:202:49)


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Signed-off-by: Simon Rey <sfbrey+eqqe@gmail.com>
@simonrey1 simonrey1 changed the title fix(ui): wrap search controls with terminal in div for fitAddon fix(ui): make overflow hidden to fix fitAddon when search bar Jul 23, 2025
@simonrey1 simonrey1 marked this pull request as ready for review July 23, 2025 15:55
@simonrey1 simonrey1 requested review from benoitf and a team as code owners July 23, 2025 15:55
@simonrey1 simonrey1 requested review from jeffmaury, SoniaSandler and cdrage and removed request for a team July 23, 2025 15:55
Copy link
Contributor
@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey @eqqe - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@simonrey1
Copy link
Contributor Author

@cdrage can you test it please? I am a bit surprised by the solution I provided but it seems to work for me.

Copy link
Contributor
@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 782a68c and efeb540.

📒 Files selected for processing (1)
  • packages/renderer/src/lib/ui/TerminalWindow.svelte (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (11)
  • GitHub Check: typecheck
  • GitHub Check: unit tests / ubuntu-24.04
  • GitHub Check: build website
  • GitHub Check: macOS
  • GitHub Check: smoke e2e tests (development)
  • GitHub Check: unit tests / macos-15
  • GitHub Check: smoke e2e tests (production)
  • GitHub Check: unit tests / windows-2025
  • GitHub Check: linter, formatters
  • GitHub Check: Linux
  • GitHub Check: Windows
🔇 Additional comments (1)
packages/renderer/src/lib/ui/TerminalWindow.svelte (1)

88-90: Prop-shorthand looks good

Switching to Svelte’s {terminal} shorthand is idiomatic and keeps the markup succinct; no behavioural change introduced.

{/if}
<div class="{className} p-[5px] pr-0 bg-[var(--pd-terminal-background)]" role="term" bind:this={logsXtermDiv}></div>

<div class="{className} overflow-hidden p-[5px] pr-0 bg-[var(--pd-terminal-background)]" role="term" bind:this={logsXtermDiv}></div>
Copy link
Contributor

Choose a reason for hiding this comment

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

💡 Verification agent

🧩 Analysis chain

overflow-hidden may unintentionally kill horizontal scroll / selection

overflow-hidden clips both axes. While it fixes the vertical overflow caused by the search bar, it also disables horizontal scroll and can truncate long log lines or break mouse-drag text selection past the viewport.

Consider restricting the clipping to the vertical axis only:

-<div class="{className} overflow-hidden p-[5px] pr-0 bg-[var(--pd-terminal-background)]" role="term" bind:this={logsXtermDiv}></div>
+<!-- Preserve horizontal scroll while hiding vertical overflow -->
+<div class="{className} overflow-y-hidden p-[5px] pr-0 bg-[var(--pd-terminal-background)]" role="term" bind:this={logsXtermDiv}></div>

Please verify that horizontal scrolling / selection still works after this change, especially with very wide log lines.


I’ll inspect how the terminal is instantiated and whether horizontal overflow/wrapping is configured before adjusting the overflow utility. Gathering the snippet…


🏁 Script executed:

#!/bin/bash
# Locate and print the TerminalWindow.svelte around the template and script
FILE=$(fd --hidden --exclude node_modules TerminalWindow.svelte)
echo "File: $FILE"
# Print first 200 lines to capture template + script
sed -n '1,200p' "$FILE"
# Show where and how Xterm is constructed
grep -n "new Terminal" -n "$FILE"

Length of output: 2710


Restrict terminal container overflow to vertical axis

The terminal’s outer <div> currently uses overflow-hidden, which prevents any horizontal overflow or extended text selection if wrapping is ever disabled or very long lines appear. Switching to overflow-y-hidden confines clipping to vertical overflow only while preserving horizontal overflow/selection.

Please update and verify:

-<div class="{className} overflow-hidden p-[5px] pr-0 bg-[var(--pd-terminal-background)]" role="term" bind:this={logsXtermDiv}></div>
+<div class="{className} overflow-y-hidden p-[5px] pr-0 bg-[var(--pd-terminal-background)]" role="term" bind:this={logsXtermDiv}></div>

• Confirm that text selection and horizontal overflow still work correctly, especially if lineWrap is ever disabled or with very wide log lines.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<div class="{className} overflow-hidden p-[5px] pr-0 bg-[var(--pd-terminal-background)]" role="term" bind:this={logsXtermDiv}></div>
<div class="{className} overflow-y-hidden p-[5px] pr-0 bg-[var(--pd-terminal-background)]" role="term" bind:this={logsXtermDiv}></div>
🤖 Prompt for AI Agents
In packages/renderer/src/lib/ui/TerminalWindow.svelte at line 92, replace the
CSS class 'overflow-hidden' on the terminal container div with
'overflow-y-hidden' to restrict overflow clipping to the vertical axis only.
This change will allow horizontal overflow and text selection to function
properly, especially when line wrapping is disabled or with very long lines.
After updating, test the terminal to ensure horizontal scrolling and text
selection behave as expected.

Copy link
codecov bot commented Jul 23, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

📢 Thoughts on this report? Let us know!

Copy link
Contributor
@jeffmaury jeffmaury left a comment

Choose a reason for hiding this comment

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

LGTM

Wondering if we can also have a unit test

@simonrey1 simonrey1 merged commit 392c7f8 into podman-desktop:main Jul 24, 2025
33 checks passed
@simonrey1
Copy link
Contributor Author

LGTM

Wondering if we can also have a unit test

I don't think so, maybe a e2e

@podman-desktop-bot podman-desktop-bot added this to the 1.21.0 milestone Jul 24, 2025
@simonrey1 simonrey1 deleted the fix-13321 branch July 25, 2025 07:09
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.

The bottom bar cuts off the log/terminal sometimes.
3 participants
0