Polish CSS spacing, color scheme etc#25
Conversation
|
Warning Review limit reached
Next review available in: 36 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughDocumentation pages update tab labels, blank-line spacing, and system requirements table formatting. ChangesDocumentation content fixes
CSS styling updates
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested labels
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
Redot-Documentation/wwwroot/app.css (1)
152-158: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winRemove the empty line before each
backgrounddeclaration.Stylelint is already flagging Lines 157, 169, 181, and 250 with
declaration-empty-line-before, so this file will not pass lint as written.Also applies to: 164-170, 176-181, 245-251
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@Redot-Documentation/wwwroot/app.css` around lines 152 - 158, Remove the empty line before each background declaration in the repeated callout style blocks so they satisfy the declaration-empty-line-before rule. Update the .callout-note and the other matching callout selectors in app.css by keeping background directly after the preceding declaration, preserving the existing styles while eliminating the lint violations.Source: Linters/SAST tools
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@Redot-Documentation/docs/About/complying_with_licenses.md`:
- Around line 4-22: Remove the temporary `### WILL REMOVE EXTRAS AFTER TESTING`
heading and the placeholder `:::info` / `:::danger` admonition blocks from
`complying_with_licenses.md`, or replace them with final production content
before merging. Update the heading structure in this document so it follows a
valid hierarchy under the existing top-level heading, using the relevant section
titles in `comlying_with_licenses.md` as the place to insert the real content.
- Line 5: The placeholder heading in the complying_with_licenses markdown breaks
heading order by jumping from the top-level title to an h3, so update that entry
in the document to use an h2 if it should remain, or remove the temporary “WILL
REMOVE EXTRAS AFTER TESTING” line entirely. Check the surrounding markdown in
this docs file for migration artifacts and keep heading levels consistent with
the document structure.
---
Outside diff comments:
In `@Redot-Documentation/wwwroot/app.css`:
- Around line 152-158: Remove the empty line before each background declaration
in the repeated callout style blocks so they satisfy the
declaration-empty-line-before rule. Update the .callout-note and the other
matching callout selectors in app.css by keeping background directly after the
preceding declaration, preserving the existing styles while eliminating the lint
violations.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 7aa8b483-2616-4ad7-a92e-d6218530a456
📒 Files selected for processing (4)
Redot-Documentation/docs/About/complying_with_licenses.mdRedot-Documentation/docs/About/introduction.mdRedot-Documentation/docs/About/list_of_features.mdRedot-Documentation/wwwroot/app.css
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
Redot-Documentation/wwwroot/app.css (2)
170-176: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winRemove the extra blank line before
background.Stylelint is already flagging this block, so this will keep the stylesheet failing lint until the empty line is removed.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@Redot-Documentation/wwwroot/app.css` around lines 170 - 176, The .callout-warning rule in app.css has an extra blank line before the background declaration, which is causing the Stylelint failure. Remove that empty line in the .callout-warning block so the declarations are contiguous and the stylesheet passes lint.Source: Linters/SAST tools
321-327: 🩺 Stability & Availability | 🟠 Major | ⚡ Quick win
min-width: 85%makes the content column too rigid.Line 327 overrides the earlier
min-width: 0, so the content pane can no longer shrink with the grid. With the TOC widened to 300px, this is likely to cause horizontal overflow or cramped layouts on narrower viewports. Keep the shrinkablemin-width: 0and constrain withmax-widthonly.Suggested fix
.doc-viewer-content { min-width: 0; margin-right: auto; margin-left: auto; max-width: 85%; - min-width: 85%; }🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@Redot-Documentation/wwwroot/app.css` around lines 321 - 327, The .doc-viewer-content rule is overriding the intended shrinkable layout by setting min-width to 85%, which can cause overflow when the TOC gets wider. In the app.css styling for .doc-viewer-content, keep the existing min-width: 0 behavior and remove the rigid min-width constraint so the column can shrink naturally while still using max-width to bound its size.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Outside diff comments:
In `@Redot-Documentation/wwwroot/app.css`:
- Around line 170-176: The .callout-warning rule in app.css has an extra blank
line before the background declaration, which is causing the Stylelint failure.
Remove that empty line in the .callout-warning block so the declarations are
contiguous and the stylesheet passes lint.
- Around line 321-327: The .doc-viewer-content rule is overriding the intended
shrinkable layout by setting min-width to 85%, which can cause overflow when the
TOC gets wider. In the app.css styling for .doc-viewer-content, keep the
existing min-width: 0 behavior and remove the rigid min-width constraint so the
column can shrink naturally while still using max-width to bound its size.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: d8b07098-359f-444c-a4b2-2fe109b95992
📒 Files selected for processing (2)
Redot-Documentation/docs/About/complying_with_licenses.mdRedot-Documentation/wwwroot/app.css
💤 Files with no reviewable changes (1)
- Redot-Documentation/docs/About/complying_with_licenses.md
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@Redot-Documentation/docs/About/system_requirements.md`:
- Around line 19-21: The GPU minimum requirements entry has broken markdown
table syntax because the single cell is split across multiple lines with a blank
line, so update the table row to keep the full GPU content in one cell and use
inline <br><br> breaks instead. Make the change in the system_requirements
markdown table for the GPU row, matching the formatting used in the Recommended
section so the table renders correctly and passes markdownlint.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 4a09dfa5-735e-4030-8885-2d6e7d01c0c5
📒 Files selected for processing (2)
Redot-Documentation/docs/About/system_requirements.mdRedot-Documentation/wwwroot/app.css
🚧 Files skipped from review as they are similar to previous changes (1)
- Redot-Documentation/wwwroot/app.css
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@Redot-Documentation/docs/About/system_requirements.md`:
- Line 44: The markdown table rows in system_requirements.md are missing
trailing pipe characters, which breaks table syntax consistency. Update the
affected rows in the table so each row ends with a closing `|`, keeping the
formatting consistent with the surrounding table entries and satisfying
markdownlint MD055. Use the table entries in the requirements section to locate
and fix the rows with the missing trailing delimiter.
- Around line 117-118: The Markdown in system_requirements.md is missing the
required blank line before the “Mobile device (smartphone/tablet) - Recommended”
table, so update that section to match the spacing used by the other tables in
the document. Adjust the content around the relevant heading and table start so
the `###` heading is followed by an empty line before the `| Component |
Requirements |` table header, keeping the formatting consistent and
markdownlint-compliant.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: e61ac281-bc3a-4c3c-956d-c2d847d7ddd1
📒 Files selected for processing (1)
Redot-Documentation/docs/About/system_requirements.md
| | **CPU** | **Windows:** x86_64 CPU with SSE4.2 instructions, with 4 physical cores or more, ARMv8 CPU <br> *Example: Intel Core i5-6600K, AMD Ryzen 5 1600, Snapdragon X Elite* <br><br> **macOS:** x86_64 or ARM CPU (Apple Silicon) <br> *Example: Intel Core i5-8500, Apple M1* <br><br> **Linux:** x86_32 CPU with SSE2 instructions, x86_64 CPU, ARMv7 or ARMv8 CPU <br> *Example: Intel Core i5-6600K, AMD Ryzen 5 1600, Raspberry Pi 5 with overclocking* | | ||
| | **GPU** | **Forward+ renderer:** Dedicated graphics with full Vulkan 1.2 support <br> *Example: NVIDIA GeForce GTX 1050 (Pascal), AMD Radeon RX 460 (GCN 4.0)* <br><br> **Mobile renderer:** Dedicated graphics with full Vulkan 1.2 support <br> *Example: NVIDIA GeForce GTX 1050 (Pascal), AMD Radeon RX 460 (GCN 4.0)* <br><br> **Compatibility renderer:** Dedicated graphics with full OpenGL 4.6 support <br> *Example: NVIDIA GeForce GTX 650 (Kepler), AMD Radeon HD 7750 (GCN 1.0)* | | ||
| | **RAM** | **Native editor:** 8 GB <br> **Web editor:** 12GB | | ||
| | **Storage** | 1.5 GB (used for the executable, project files, all export templates and cache) |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Add missing trailing pipes to table rows.
Lines 44, 78, 101, 115, and 124 are missing trailing | characters, violating markdownlint MD055. While Markdig often tolerates this, it breaks table syntax consistency and can risk rendering issues with stricter parsers or if cell content ever contains pipe characters.
🐛 Proposed fix
-| **Storage** | 1.5 GB (used for the executable, project files, all export templates and cache)
+| **Storage** | 1.5 GB (used for the executable, project files, all export templates and cache) |-| **Operating system** | **For native exports:** Windows 10 or 11 (Forward+/Mobile, Direct3D 12), macOS 10.13 (Compatibility), macOS 10.15 (Forward+/Mobile, Vulkan), macOS 13.0 (Forward+/Mobile, Metal), Linux distribution released after 2016<br><br>**For web exports:** Firefox 79, Chrome 68, Edge 79, Safari 15.2, Opera 64
+| **Operating system** | **For native exports:** Windows 10 or 11 (Forward+/Mobile, Direct3D 12), macOS 10.13 (Compatibility), macOS 10.15 (Forward+/Mobile, Vulkan), macOS 13.0 (Forward+/Mobile, Metal), Linux distribution released after 2016<br><br>**For web exports:** Firefox 79, Chrome 68, Edge 79, Safari 15.2, Opera 64 |-| **Operating system** | **For native exports:** Android 6.0 (Compatibility), Android 9.0 (Forward+/Mobile), iOS 12.0 (Forward+/Mobile, Vulkan), iOS 16.0 (Forward+/Mobile, Metal)<br><br>**For web exports:** Firefox 79, Chrome 88, Edge 79, Safari 15.2, Opera 64, Samsung Internet 15
+| **Operating system** | **For native exports:** Android 6.0 (Compatibility), Android 9.0 (Forward+/Mobile), iOS 12.0 (Forward+/Mobile, Vulkan), iOS 16.0 (Forward+/Mobile, Metal)<br><br>**For web exports:** Firefox 79, Chrome 88, Edge 79, Safari 15.2, Opera 64, Samsung Internet 15 |-| **Operating system** | **For native exports:** Windows 10 or 11, macOS 10.15 (Forward+/Mobile, Vulkan), macOS 13.0 (Forward+/Mobile, Metal), Linux distribution released after 2020<br><br>**For web exports:** Latest version of Firefox, Chrome, Edge, Safari, Opera
+| **Operating system** | **For native exports:** Windows 10 or 11, macOS 10.15 (Forward+/Mobile, Vulkan), macOS 13.0 (Forward+/Mobile, Metal), Linux distribution released after 2020<br><br>**For web exports:** Latest version of Firefox, Chrome, Edge, Safari, Opera |-| **Operating system** | **For native exports:** Android 9.0, iOS 14.1 (Forward+/Mobile, Vulkan), iOS 16.0 (Forward+/Mobile, Metal)<br><br>**For web exports:** Latest version of Firefox, Chrome, Edge, Safari, Opera, Samsung Internet
+| **Operating system** | **For native exports:** Android 9.0, iOS 14.1 (Forward+/Mobile, Vulkan), iOS 16.0 (Forward+/Mobile, Metal)<br><br>**For web exports:** Latest version of Firefox, Chrome, Edge, Safari, Opera, Samsung Internet |Also applies to: 78-78, 101-101, 115-115, 124-124
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 44-44: Table pipe style
Expected: leading_and_trailing; Actual: leading_only; Missing trailing pipe
(MD055, table-pipe-style)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@Redot-Documentation/docs/About/system_requirements.md` at line 44, The
markdown table rows in system_requirements.md are missing trailing pipe
characters, which breaks table syntax consistency. Update the affected rows in
the table so each row ends with a closing `|`, keeping the formatting consistent
with the surrounding table entries and satisfying markdownlint MD055. Use the
table entries in the requirements section to locate and fix the rows with the
missing trailing delimiter.
| ### Mobile device (smartphone/tablet) - Recommended | ||
|
|
||
| | Component | Requirement | | ||
| |----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | ||
| | **CPU** | - **Android:** SoC with 64-bit ARM or x86 CPU, with 3 "performance" cores or more - *Example: Qualcomm Snapdragon 845, Samsung Exynos 9810* - **iOS:** SoC with 64-bit ARM CPU - *Example: Apple A14 (iPhone 12)* | | ||
| | **GPU** | - **Forward+ renderer:** SoC featuring GPU with full Vulkan 1.2 support, or Metal 3 support (iOS/iPadOS) - *Example: Qualcomm Adreno 630, Mali-G72 MP18, Apple A14 (iPhone 12)* - **Mobile renderer:** SoC featuring GPU with full Vulkan 1.2 support, or Metal 3 support (iOS/iPadOS) - *Example: Qualcomm Adreno 630, Mali-G72 MP18, Apple A14 (iPhone 12)* - **Compatibility renderer:** SoC featuring GPU with full OpenGL ES 3.2 support - *Example: Qualcomm Adreno 630, Mali-G72 MP18, Apple A14 (iPhone 12)* | | ||
| | **RAM** | - **For native exports:** 2 GB - **For web exports:** 4 GB | | ||
| | **Storage** | 150 MB (used for the executable, project files and cache) | | ||
| | **Operating system** | - **For native exports:** Android 9.0, iOS 14.1 (Forward+/Mobile, Vulkan), iOS 16.0 (Forward+/Mobile, Metal) - **For web exports:** Latest version of Firefox, Chrome, Edge, Safari, Opera, Samsung Internet | | ||
| | Component | Requirements | |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Add blank line before Mobile Recommended table.
Line 118 starts the table immediately after the heading on Line 117 without an intervening blank line, violating markdownlint MD058. All other tables in this file follow a consistent pattern of a blank line between the ### heading and the table header.
🐛 Proposed fix
### Mobile device (smartphone/tablet) - Recommended
+
| Component | Requirements |📝 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.
| ### Mobile device (smartphone/tablet) - Recommended | |
| | Component | Requirement | | |
| |----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | |
| | **CPU** | - **Android:** SoC with 64-bit ARM or x86 CPU, with 3 "performance" cores or more - *Example: Qualcomm Snapdragon 845, Samsung Exynos 9810* - **iOS:** SoC with 64-bit ARM CPU - *Example: Apple A14 (iPhone 12)* | | |
| | **GPU** | - **Forward+ renderer:** SoC featuring GPU with full Vulkan 1.2 support, or Metal 3 support (iOS/iPadOS) - *Example: Qualcomm Adreno 630, Mali-G72 MP18, Apple A14 (iPhone 12)* - **Mobile renderer:** SoC featuring GPU with full Vulkan 1.2 support, or Metal 3 support (iOS/iPadOS) - *Example: Qualcomm Adreno 630, Mali-G72 MP18, Apple A14 (iPhone 12)* - **Compatibility renderer:** SoC featuring GPU with full OpenGL ES 3.2 support - *Example: Qualcomm Adreno 630, Mali-G72 MP18, Apple A14 (iPhone 12)* | | |
| | **RAM** | - **For native exports:** 2 GB - **For web exports:** 4 GB | | |
| | **Storage** | 150 MB (used for the executable, project files and cache) | | |
| | **Operating system** | - **For native exports:** Android 9.0, iOS 14.1 (Forward+/Mobile, Vulkan), iOS 16.0 (Forward+/Mobile, Metal) - **For web exports:** Latest version of Firefox, Chrome, Edge, Safari, Opera, Samsung Internet | | |
| | Component | Requirements | | |
| ### Mobile device (smartphone/tablet) - Recommended | |
| | Component | Requirements | |
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 118-118: Tables should be surrounded by blank lines
(MD058, blanks-around-tables)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@Redot-Documentation/docs/About/system_requirements.md` around lines 117 -
118, The Markdown in system_requirements.md is missing the required blank line
before the “Mobile device (smartphone/tablet) - Recommended” table, so update
that section to match the spacing used by the other tables in the document.
Adjust the content around the relevant heading and table start so the `###`
heading is followed by an empty line before the `| Component | Requirements |`
table header, keeping the formatting consistent and markdownlint-compliant.
Summary by CodeRabbit