[Improvment] Add disclaimer for the things not working in the live preview editing
Maintainers usually reply within 7 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start by reproducing the three reported live preview behaviors in the Strapi website: exiting draft mode switches to the published version, formatting appears only after saving, and list items duplicate text. Use the linked video to compare the list behavior. Trace the preview editing flow and identify where draft state and rich text rendering diverge; done when edits, formatting, and lists display correctly in the preview before publishing.
Written by the indexing model from the issue text.
Description
- When I click to "Exit" button from the draft mode, in the strapi preview, the published version is displayed (which means I don't see saved draft anymore, even after hitting save button again).
STR:
- Open preview
- Edit text in the component + see the live editation happening in the preview
- Click "Exit" on the yellow banner in the preview window
- Observe the version of the page displayed in the preview mode is now the published version
- Try to edit text + save
- Observe the changes are not displayed in the preview anymore
-
The styles and formatting of the text are displayed only after save (e.g. bold).
-
Lists (bullets, numbers) breaking the text component in the preview (the text is displayed again with each bullet in the component). It fixes once published.
https://jam.dev/c/4737742a-1010-4c81-bfed-2746ee5b0011 - see the behaviour in the video.
STR:
- Add bullet point into the component
- Write
- Observe text being duplicated
- Add another bullet point
- Observe text being triplicated.
- Dominant language
- TypeScript
- Stars
- 6
- Forks
- 5
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from strapi/website
-
[SEO] Remove /blog/categories page from sitemapPossibly taken @fonodi claimed this 5 days ago. Openreopened
Difficulty 1/5 Under an hour Newbie friendliness 80/100
strapi/website#128 · 2 assignees ·
Maintainers usually reply within 7 days
-
Create a new collection type and component for cloud-legalPossibly taken @fonodi claimed this 12 days ago. Openenhancement
strapi/website#169 · 2 assignees ·
Maintainers usually reply within 7 days
-
Update GitHub Actions that still run on Node.js 20May be free again @matej-marcisovsky claimed this 30 days ago, and no pull request is open. Open
strapi/website#153 · 1 assignee ·
Maintainers usually reply within 7 days
-
Pricing buttons don't respond until the cards hydratePossibly taken @fonodi claimed this 5 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
strapi/website#152 · 1 assignee ·
Maintainers usually reply within 7 days
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 7 days
Similar issues
-
Add: BOM CineOpenapproved check:passed streams:add
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug platform-android
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Termix-SSH/Mobile#146 · 1 comment ·
Maintainers usually reply within 2 days
-
MCP mcp-feedback-pattern
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
getsentry/toolkit#2276 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
devswha/herdr-web-ui#3875 ·