8000 feat: clean ui for iframes by elibosley · Pull Request #268 · unraid/docs · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

feat: clean ui for iframes #268

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

Jump to bottom < 8000 /div>
Merged
merged 5 commits into from
May 9, 2025
Merged

feat: clean ui for iframes #268

merged 5 commits into from
May 9, 2025

Conversation

elibosley
Copy link
Member
@elibosley elibosley commented May 9, 2025

Before Submitting This PR, Please Ensure You Have Completed The Following:

  1. Are internal links to wiki documents using relative file links?
  2. Are all new documentation files lowercase, with dash separated names (ex. unraid-os.mdx)?
  3. Are all assets (images, etc), located in an assets/ subfolder next to the .md/mdx files?
  4. Have you checked to ensure there aren't other open Pull Requests for the same update/change?
  5. Is the build succeeding?

Summary by CodeRabbit

  • New Features
    • Added automatic detection of when the site is viewed inside an iframe, enabling special layout adjustments.
  • Style
    • Updated styles to hide navigation and sidebar elements and expand content width when viewed in an iframe, providing a cleaner embedded experience.

Copy link
Contributor
coderabbitai bot commented May 9, 2025

Walkthrough

The changes introduce iframe detection to the Docusaurus site by adding a new JavaScript file and updating the site's configuration to load it. Corresponding CSS rules are added to modify the site's layout and hide certain elements when the site is viewed inside an iframe, based on a custom data attribute.

Changes

File(s) Change Summary
docusaurus.config.js Updated to include /js/iframe-detector.js in the scripts array, with async: false.
src/css/custom.css Added CSS rules targeting [data-iframe="true"] to hide navigation, sidebar, footer, and complementary elements; adjusted main content width and padding.
static/js/iframe-detector.js New script detects if the site is loaded in an iframe and sets a data-iframe="true" attribute on the HTML element accordingly.

Sequence Diagram(s)

sequenceDiagram
    participant Browser
    participant iframe-detector.js
    participant HTML Document
    Note over Browser: DOMContentLoaded event
    Browser->>iframe-detector.js: Load and execute
    iframe-detector.js->>iframe-detector.js: isInIframe()
    iframe-detector.js->>HTML Document: Set data-iframe="true" if in iframe
    HTML Document->>Browser: CSS applies styles based on data-iframe attribute
Loading

Suggested reviewers

  • ljm42

Poem

A rabbit hopped into an iframe one night,
Hiding navbars and footers from sight.
With a sprinkle of CSS and a JavaScript cheer,
The content stretched wide—now everything’s clear!
“In iframes we trust!” the bunny declared,
As the layout transformed, perfectly prepared.
🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between 0693c2f and 2a96085.

📒 Files selected for processing (1)
  • static/js/iframe-detector.js (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • static/js/iframe-detector.js
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: build
  • GitHub Check: AWS Amplify Console Web Preview

🪧 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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 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.

@elibosley elibosley requested a review from zackspear May 9, 2025 21:03
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

🧹 Nitpick comments (2)
static/js/iframe-detector.js (1)

1-4: Refine header comment for accuracy
The top comment says "sets a CSS variable" but the script actually toggles a data-iframe attribute on the root element. Consider updating the description to reflect its behavior precisely.

src/css/custom.css (1)

74-93: Optional: Consolidate repetitive selectors
To improve maintainability, you could group the attribute prefix into a single block and leverage a CSS custom mixin or variable. For example:

:root[data-iframe="true"] {
  --iframe-hide-selectors: .navbar, header, footer, .theme-doc-sidebar-container, .theme-doc-toc-desktop, .theme-doc-toc-mobile, nav.pagination-nav, div[role="complementary"], aside;
  --iframe-main-container: main[class^="docMainContainer_"];
}

:root[data-iframe="true"] var(--iframe-hide-selectors) {
  display: none !important;
}

:root[data-iframe="true"] var(--iframe-main-container) {
  max-width: 100% !important;
  width: 100% !important;
}
:root[data-iframe="true"] var(--iframe-main-container) > div {
  padding-top: 1rem !important;
}

This reduces duplication and centralizes the attribute selector.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b36974e and 0693c2f.

📒 Files selected for processing (3)
  • docusaurus.config.js (1 hunks)
  • src/css/custom.css (1 hunks)
  • static/js/iframe-detector.js (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: build
🔇 Additional comments (5)
static/js/iframe-detector.js (2)

7-15: Iframe detection logic is solid
The use of window.self !== window.top combined with a try/catch for cross-origin frames correctly determines when the page is embedded.


17-24: Attribute toggling is clear and idempotent
applyIframeMode() cleanly adds or removes data-iframe="true" on the <html> element, enabling scoped CSS for iframe contexts.

docusaurus.config.js (1)

42-45: Script inclusion looks correct
Adding { src: "/js/iframe-detector.js", async: false } ensures the detector runs synchronously. Verify that static/js/iframe-detector.js is served at /js/iframe-detector.js in production (Docusaurus should map static/ to the site root).

src/css/custom.css (2)

74-84: Iframe-specific hiding is effective
The selectors under html[data-iframe="true"] correctly target and hide the navbar, sidebars, footer, etc., in iframe mode.


86-93: Layout expansion for iframe contexts is correct
Setting the main container to width: 100% and adding top padding ensures full-bleed content inside an iframe.

Copy link

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-268.d1o5s833kbd339.amplifyapp.com

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
@elibosley elibosley merged commit 50d1cdd into main May 9, 2025
3 checks passed
@elibosley elibosley deleted the feat/docs-iframe-ui branch May 9, 2025 22:31
@coderabbitai coderabbitai bot mentioned this pull request May 9, 2025
5 tasks
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.

2 participants
0