Skip to content

why sometimes slash-menu-items doesn't exist #781

Description

@rex-0085

I don't know why sometimes slash-menu-items doesn't exist. many thanks
Image

Activity

  1. palmer-cl commented on Aug 18, 2025

    @palmer-cl
    Collaborator

    Hey Rex,

    In the developer tools like you have open, are you seeing any errors in the console?

  2. rex-0085 commented on Sep 2, 2025

    @rex-0085
    Author
    Image

    "mf-dep____vendor.d0d1be01.js:507866 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'readText')"

    @palmer-cl could you please have a look, thanks a lot

  3. palmer-cl commented on Sep 2, 2025

    @palmer-cl
    Collaborator

    Trying to pinpoint your failure. Can you tell me a little more about your environment?

    • what is your webpage url when accessing? localhost or something else?
    • are you in an iframe?
    • can you send your browser version information?
  4. linked a pull request that will close this issuefix: add safety check for clipboard usage #859on Sep 3, 2025
  5. harbournick commented on Sep 3, 2025

    @harbournick
    Collaborator

    @rex-0085 We merged a fix to prevent the clipboard error that is likely causing this, deployed to 0.16.0-next.8

    Please let us know if you still have this issue, though, in case there's anything else going on

  6. rex-0085 commented on Sep 6, 2025

    @rex-0085
    Author

    @palmer-cl
    I found error only exist in localhost. after build, I can see the following panel, is that relative reason?
    It still exist at 0.16.3
    Image

    ps:
    not iframe
    macos
    chrome 139.0.7258.155

  7. palmer-cl commented on Sep 6, 2025

    @palmer-cl
    Collaborator

    Yes this likely means that your production URL is behaving correctly prompting you for permissions, but localhost url does not have permissions. When on local host navigate to the site settings and turn it to allow.

    Image
  8. asumaran commented on Feb 13, 2026

    @asumaran

    I believe I ran into the same bug, so I opened a PR with a fix: #2018

  9. superdoc-bot commented on Feb 14, 2026

    @superdoc-bot
    Contributor

    🎉 This issue is included in superdoc v1.13.0-next.11

    The release is available on GitHub release

  10. linear commented on Feb 14, 2026

    @linear
  11. superdoc-bot commented on Mar 11, 2026

    @superdoc-bot
    Contributor

    🎉 This issue is included in superdoc-cli v0.2.0

    The release is available on GitHub release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

status: doneAll linked engineering blockers are marked Done.

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions