Skip to content
Known Issues: 6 impacting issues currently listed.
impacting+ : 6View details

Known Issues

A running list of known issues and limitations across MyOshi Theme Lab, plus workarounds and reporting tips.

Last updated: Mar 01, 2026 Total open: 11
If you’re seeing something that’s not listed here, please report it (steps below). This page is for confirmed issues and platform limitations.

Quick links

Issues

Status: Pending OshiLab Update to Templates Areas: Custom CSS, Custom HTML, Lab Preview, Lab Templates Updated: Mar 01, 2026

What’s happening

  • Recent changes to MyOshi's CSS class structure have resulted in discrepancies between the styling in lab previews and the actual styling on profiles that use the new MyOshi classes. This is because the lab templates have not yet been updated to reflect the new class structure, leading to inaccurate previews for users who are using the new classes in their profiles, or for those using the old structures and adding them to their live profiles.

Workaround

  • Use the base extraction feature to pull in the preview code from your own profile to use as the template for your lab. This will ensure that the styling in the lab preview matches what you see on your profile, as it will be based on the same MyOshi classes and structure.
  • An update to the lab templates is planned to align with the recent changes to MyOshi's CSS class structure, which will ensure that the styling in the lab preview accurately reflects the styling on profiles using the new MyOshi classes. In the meantime, using the base extraction method will help mitigate this issue and provide a more accurate preview experience.

Status: MyOshi restriction Areas: Custom CSS, Audit Updated: Feb 27, 2026

What’s happening

  • MyOshi only allows @import from specific font CDNs (Google Fonts, Bunny Fonts, Typekit, cdnjs). Other stylesheet imports are blocked.
  • data: URIs inside @import are blocked as well.

Workaround

  • Paste non-font CSS directly into Custom CSS (up to 50,000 characters).
  • For fonts, use an allowed host (Google/Bunny/Typekit/cdnjs).

Status: MyOshi restriction Areas: Custom CSS, Audit Updated: Feb 27, 2026

What’s happening

  • Any protocol other than https: and data: is blocked (including percent-encoded evasion attempts).

Workaround

  • Host assets over https:// or embed small assets as data: URIs.

Status: MyOshi restriction Areas: Custom CSS, Custom HTML, Audit Updated: Feb 27, 2026

What’s happening

  • MyOshi enforces field size limits at the API layer.

Workaround

  • Reduce repetition, remove unused rules/markup, and consolidate styles with variables/utilities.

Status: MyOshi behavior Areas: Custom CSS, Audit Updated: Feb 27, 2026

What’s happening

  • MyOshi now scopes selectors automatically. Themes that double-scope with .profile-page/.profile-custom-css may behave incorrectly.

Workaround

  • Remove manual scoping prefixes and target elements inside your profile directly (e.g. .my-box, h2).
  • Re-run the Audit after simplifying selectors.

Status: MyOshi behavior Areas: Custom CSS, Audit Updated: Feb 27, 2026

What’s happening

  • MyOshi converts position: fixed to absolute to prevent overlays that cover navigation.

Workaround

  • Use position: absolute inside a relatively positioned container.
  • Use position: sticky for in-container sticky effects.

Status: Pending OshiLab Update Areas: Lab Preview, Lab Templates, Light Mode Updated: Mar 01, 2026

What’s happening

  • When using the Oshi Lab app in light mode, some elements of the app UI are not visible due to color contrast issues. This can make it difficult to navigate the app and use certain features effectively, as important buttons, text, or other UI components may be hidden or hard to see against the light background.

Workaround

  • Use the app in dark mode to ensure that all elements of the app UI are visible and functional. This will allow you to navigate the app effectively and use all features without any issues related to hidden UI elements.

Status: MyOshi restriction Areas: Custom CSS, Audit Updated: Feb 27, 2026

What’s happening

  • Extremely large blur values can cause GPU issues; MyOshi caps blur() to 50px.

Workaround

  • Reduce blur() to ≤ 50px.
  • Consider layered translucent panels or gradients instead of huge blur radii.

Status: Known limitation Areas: Audit, Preview Updated: Feb 27, 2026

What’s happening

  • The optional contrast audit uses computed styles from the live preview. If the preview iframe is sandboxed without same-origin access, the app cannot read computed styles, so contrast checks may be skipped.

Workaround

  • Run the audit without contrast checks enabled.
  • If you control the preview iframe attributes, allow same-origin access (but keep scripts disabled).

Snippet

<iframe id=\"previewFrame\" sandbox=\"allow-same-origin\" ...></iframe>

Status: MyOshi restriction Areas: Custom CSS, Audit Updated: Feb 27, 2026

What’s happening

  • Very large z-index values are capped to prevent stacking abuse outside your profile container.
  • MyOshi also applies isolation: isolate on your profile, so z-index cannot escape into site chrome.

Workaround

  • Keep z-index values reasonable and within [-10000, 10000].

Status: Expected behavior Areas: Audit, Preview Updated: Feb 27, 2026

What’s happening

  • MyOshi sanitizes at display time (client-side) and may change behavior without requiring you to re-save. The Lab preview aims to match current behavior, but platform updates can temporarily cause differences until the Lab is updated.

Workaround

  • If something looks off, run the Audit and check for rule warnings (fixed → absolute, z-index caps, import/url restrictions, protected selectors, etc.).
  • When in doubt, test on a real MyOshi profile after making minimal changes.

How to report an issue

If you encounter a bug that isn’t listed above, please include as much of the following as you can. It saves a lot of back-and-forth and makes fixes faster.

Include

  • What you expected vs what happened
  • Steps to reproduce (click-by-click)
  • Your browser + version (Chrome/Firefox/Safari) and OS
  • A minimal CSS/HTML sample that triggers it (if possible)
  • Audit report JSON (use “Copy JSON” in the Audit tab)

Avoid sharing

  • Personal info (emails, private links)
  • Private tokens/keys
  • Unredacted DMs or private server info
Tip: When possible, reduce the theme to the smallest snippet that still reproduces the issue. It makes debugging dramatically easier.
Help
Shortcuts
  • Ctrl/ + K: Tools palette (Lab)