sync#48
Open
hotcoding85 wants to merge 7768 commits into
Open
Conversation
…selection parameter.
… check in deleteContent funciton.
…leteContent function.
…-lists-with-paragraphs Fix nested lists interrupted by paragraphs losing structure and consecutive numbering.
Add `v47.6.2` changelog entries to `CHANGELOG.md`
…tes from $root. Also clipboard holder and document fragment definitions should include content of inline root.
…r classes to async/await.
Upgrade Chrome version to `147.0.7727.55`.
Clarify editor loads in getting started
Merge stable to master
Merge release (v48.1.1) to stable
Merge stable (v48.1.1) to master
Updated changelog for v48.1.1
Docs: Fix tsdoc link in the multi root error code.
Bump CKBox to `2.12.0`.
Revision: 95f4f0e85dd0e1796421ca9d799feb5f0551e99d
Revision: 0d5dfb3dbbae126e9368737f9777027a7804706a Co-authored-by: Kamil Piechaczek <pomek@users.noreply.github.com>
… comments, and GHS `hgroup` features. - Fixed the Title feature to silently skip roots whose `modelElement` does not accept the `title` element, and to log a single `title-no-supported-root` warning when no root supports the title structure. - Fixed `HtmlComment` to preserve HTML comments in editors configured with a custom root `modelElement`, by gating per-comment attributes on `$comment` declared on `$root` rather than hardcoding the root element name. - Fixed the General HTML Support schema for `hgroup` to use `allowWhere: '$container'` instead of hardcoding `allowIn: '$root'`, so the element is correctly registered in editors with a custom root `modelElement`. - Refactored `$rootEditableOptions` initialization in `MultiRootEditor` so placeholder and label options are normalized into `modelAttributes` before editor initialization, making the attribute available via `getRootAttributes()` and ensuring correct round-tripping through revision history and RTC. - Added documentation for custom root elements to the schema deep-dive guide and improved API notes on `DataController#parse`, `DataController#toModel`, `UpcastDispatcher#convert`, `ModelDocument#createRoot`, and `ModelWriter#addRoot`. Revision: d90c66834ad294e40a18639af1f0d6299fcf4f0f Co-authored-by: Kuba Niegowski <j.niegowski@cksource.com>
- Added a `config.mediaEmbed.styles` option that allows integrators to define custom style sets for embedded media, replacing the previously fixed default styles. - Extended the media embed toolbar to expose style buttons driven by the new configuration. - Updated and expanded documentation, including a new guide for styling non-previewable media and revised media embed styles reference pages. - Improved test coverage for the media embed styles command, editing, UI, and toolbar components. Revision: 8d5b4635e258c12e717afefb6e9fdec25cfbe30e Co-authored-by: Jacek Idzik <j.idzik@cksource.com>
…xt input. Improved the `HighlightedTextView` component so that text containing HTML-special characters such as `&`, `<`, and `>` is correctly escaped before rendering, preventing unintended HTML interpretation. Revision: 68d76bec3ea8a0f7c60e6b22d393e30fdd2d3b8d Co-authored-by: Dawid Kossowski <d.kossowski@cksource.com> Co-authored-by: Michał Kozielski <m.kozielski@cksource.com>
- Added a new `list.allowSkipLevels` configuration option that controls whether list items can be indented to non-sequential levels (skipping intermediate levels). - Improved paste from Microsoft Word to correctly handle lists with skipped indentation levels, respecting the `allowSkipLevels` setting. - Updated the indent block list integration and related list utilities to enforce or relax level constraints based on the new configuration. - Added manual test and supporting fixture data for the skip-levels list behavior. Revision: 2dd8c5b206d5758a5404f178490337b65bc94815 Co-authored-by: Marta Motyczynska <m.motyczynska@cksource.com> Co-authored-by: Mateusz Baginski <cziken58@gmail.com>
- Fixed top-level list items becoming visually misaligned in the editor when the same list was interrupted by a different list or an empty paragraph. - Fixed nested list items being incorrectly flattened to the top indentation level when pasted immediately after their parent item. Revision: 249e4ec360266b505a55246b2777f2badd748a3b Co-authored-by: Marta Motyczynska <m.motyczynska@cksource.com>
- Corrected the autoformat trigger description for numbered lists to reflect that any number followed by `.` or `)` and a space starts a numbered list. - Added documentation for the `config.list.enableSkipLevelLists` option, including a code example and a compatibility warning for email clients. Revision: 9b9c79a80c55d9a08bdcc29f5a0a0a15afb7f5f2 Co-authored-by: Marta Motyczynska <m.motyczynska@cksource.com> Co-authored-by: Mateusz Gorzeliński <mateusz.gorzelinski@gmail.com>
Minor CSS formatting normalization and an update to the Spotify embed minimum width to account for widget border space used by track changes suggestion markers. Revision: 743a4ebda039616909a88deb854321818328ad39 Co-authored-by: Jacek Idzik <j.idzik@cksource.com>
…itor types. - Added a new `rootsConfig` editor configuration option that allows specifying per-root settings, including an `inline` flag to restrict a root to inline content only (disallowing block elements). - Introduced a `rootAcceptsBlocks` utility function and updated root configuration normalization to support the new per-root inline content model. - Updated all built-in editor types (Classic, Balloon, Decoupled, Inline, and Multi-root) to respect per-root inline configuration when creating editables and their UI views. - Disabled inline image insertion in roots configured as inline-only content areas. - Added manual tests for inline-content roots across all editor types. Revision: a0240e439c6a30d9338e8d422699998b11493ea0 Co-authored-by: Kuba Niegowski <1232187+niegowski@users.noreply.github.com> Co-authored-by: Kuba Niegowski <j.niegowski@cksource.com> Co-authored-by: Piotr Szczęśniak <szczesniakp@o2.pl>
…ent dependency. - Updated the documentation site promo bar to advertise an upcoming webinar on CKEditor AI multi-root content orchestration. - Updated the `puppeteer` development dependency to a newer version. Revision: af199e0f1850683b8be73d2fe05da83a9200a7e0 Co-authored-by: Andrzej Kała <a.kala@cksource.com> Co-authored-by: Przemysław Zań <przemyslaw.zan@gmail.com>
Revision: fdf4abfe57f68d28bfa5506eaba69082c9f981aa Co-authored-by: Jacek Idzik <j.idzik@cksource.com>
…t schema. - Added a public `sourceRange` getter to `MoveOperation` that returns the range covered by the move source, and used it internally to reduce code duplication. - Fixed the `form` element schema definition in HTML support to no longer mark it as a block element, restoring correct handling of `<form>` in general HTML support. Revision: d2d1e55d56ec7260b80b47b138010abd68fdf3dc Co-authored-by: Szymon Cofalik <s.cofalik@cksource.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
19 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Suggested merge commit message (convention)
Type: Message. Closes #000.
Additional information
For example – encountered issues, assumptions you had to make, other affected tickets, etc.