Skip to content
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

react-accordion-with-richtext - "something went wrong" tinymce error on mobile #5156

Closed
3 of 9 tasks
nloand opened this issue May 29, 2024 · 2 comments
Closed
3 of 9 tasks
Labels
status:no-recent-activity status:node-compatibility type:bug-suspected Suspected bug (not working as designed/expected). See type:bug-confirmed for confirmed bugs

Comments

@nloand
Copy link

nloand commented May 29, 2024

Disclaimer

Yes

Sample

react-accordion-with-richtext

Contributor(s)

@arunkumarperumal

What happened?

Accordions throw stack trace error / "Something went wrong" with tinymce on read-device mobile rendering. This does not occur in emulator mode.

Something went wrong

If the problem persists, contact the site administrator and give them the information in Technical Details.Technical Details

ERROR:
Script error for: 51789d0c-7a65-494e-8969-59bfc883e751_0.0.1/tinymce
http://requirejs.org/docs/errors.html#scripterror

CALL STACK:
Error: Script error for: 51789d0c-7a65-494e-8969-59bfc883e751_0.0.1/tinymce
http://requirejs.org/docs/errors.html#scripterror
at B (eval at e (https://xxx.cdn.office.net/files/sp-client/sp-pages-assembly_en-us_7653987a3a588c9a3866f4c25ddb3d9a.js:198:10299), <anonymous>:8:252)
at HTMLScriptElement.onScriptError (eval at e (https://xxx.cdn.office.net/files/sp-client/sp-pages-assembly_en-us_7653987a3a588c9a3866f4c25ddb3d9a.js:198:10299), <anonymous>:30:244)

Steps to reproduce

  1. Open mobile browser such as Blackberry access
  2. Open page that contains react-accordion-with-rich-text

Expected behavior

I expect the behavior to match the mobile emulator mode and show the accordions.

Target SharePoint environment

SharePoint Online

Developer environment

Windows

Browsers

  • Internet Explorer
  • Microsoft Edge
  • Google Chrome
  • FireFox
  • Safari
  • mobile (iOS/iPadOS)
  • mobile (Android)
  • not applicable
  • other (enter in the "Additional environment details" area below)

What version of Node.js is currently installed on your workstation?

18.19.0

What version of Node.js is required by the sample?

v^12 || ^14 (didn't re-build package so n/a)

Paste the results of SPFx doctor

√ SharePoint Framework v1.13.0
× Node v18.19.0 found, v^12 || ^14 required
× yo v5.0.0 found, v^4 required
× gulp should be removed
√ gulp-cli v2.3.0
√ bundled typescript used

Additional environment details

Blackberry browser

@nloand nloand added the type:bug-suspected Suspected bug (not working as designed/expected). See type:bug-confirmed for confirmed bugs label May 29, 2024
Copy link

This issue has been marked as stale due to no progress in over 90 days. If you are still experiencing this issue, please provide additional information so we can help you resolve it.

Copy link

github-actions bot commented Sep 1, 2024

Thank you for your issue. It looks like the web part sample you're trying to use is not compatible with the version of Node.js that you're running in your environment.

You should refer to the troubleshooting instructons before opening an issue to make sure that you have eliminated the most common causes.

We'll close this issue, but if you run into further issues after you have made changes to your environment and followed the troubreshooting steps, please do not hesitate to open a new issue so we can help you further.

@github-actions github-actions bot closed this as completed Sep 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:no-recent-activity status:node-compatibility type:bug-suspected Suspected bug (not working as designed/expected). See type:bug-confirmed for confirmed bugs
Projects
None yet
Development

No branches or pull requests

2 participants