Design what magic block UI should look like in different states #6740
Assignees
Labels
domain:ui/ux
This issue reports a problem related to UI or UX.
package:widget
squad:magic
type:feature
This issue reports a feature request (an idea for a new functionality or a missing option).
Milestone
Comments
oleq
added
type:feature
Reinmar
added a commit
that referenced
this issue
May 14, 2020
Feature (widget): Brought the feature allowing users to type in tight spots around block widgets where web browsers do not allow the caret to be placed (see #407). Closes #6740. Closes #6688. Closes #6689. Closes #6695. Internal (horizontal-line): Updated the styling of .ck-horizontal-line from overflow: hidden to display: flow-root to allow the typing around UI inside the widgets (see #407, #6795). Tests (image): Updated various image test to take the widget typing around feature into account (see #407). Fix (media-mebed): The media widget conversion should not discard widget internals (drag or resize handlers, buttons to insert paragraphs, etc.) injected by other features when converting the URL (see #407). Feature (theme-lark): Brought styles for the feature allowing users to type in tight spots around block widgets (see #407). MINOR BREAKING CHANGE: The new --ck-color-focus-border-coordinates CSS custom property has been added and the existing --ck-color-focus-border property now uses it internally. If your integration overrides the latter, we recommend you update the former to avoid compatibility issues with various editor UI features.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the initial implementation, magic block buttons will be injected into widget wrappers (UI elements). We need different styles for different states:
position: relativeandoverflow: visible(probably mentioned in widget guides).The text was updated successfully, but these errors were encountered: