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

[Flaky Test] should always expand single line selection #39787

Closed
github-actions bot opened this issue Mar 27, 2022 · 0 comments · Fixed by #48035
Closed

[Flaky Test] should always expand single line selection #39787

github-actions bot opened this issue Mar 27, 2022 · 0 comments · Fixed by #48035
Labels
[Type] Flaky Test Auto-generated flaky test report issue

Comments

@github-actions
Copy link

github-actions bot commented Mar 27, 2022

Flaky test detected. This is an auto-generated issue by GitHub Actions. Please do NOT edit this manually.

Test title

should always expand single line selection

Test path

/test/e2e/specs/editor/various/multi-block-selection.spec.js

Errors

[2023-03-30T09:02:10.961Z] Test passed after 1 failed attempt on try/footnotes-again.
[2023-04-04T19:48:03.514Z] Test passed after 1 failed attempt on try/block-tools-marry-document-tools.
[2023-09-15T21:51:58.083Z] Test passed after 1 failed attempt on try/rich-text-value-refactor.
[2023-09-26T11:41:40.378Z] Test passed after 1 failed attempt on try/debounce-rich-text-on-input.
[2023-10-24T23:03:17.554Z] Test passed after 1 failed attempt on try/block-edit-lazy-loading.
[2023-10-25T10:49:43.585Z] Test passed after 1 failed attempt on try/block-edit-lazy-loading.
[2023-11-11T00:16:40.541Z] Test passed after 1 failed attempt on trunk.
@github-actions github-actions bot added the [Type] Flaky Test Auto-generated flaky test report issue label Mar 27, 2022
github-actions bot referenced this issue Dec 16, 2022
* Migrate Font Size Picker tests to Playwright

* Remove legacy tests

* Open document settings before each test
github-actions bot referenced this issue Dec 16, 2022
…46598)

A defect introduced in #46018 led to the tag processor backing up
one index too far after flushing its queued changes on a document.

For most operations this didn't cause any harm because when immediately
moving forward after an update, the `next_tag()` returned to the same
spot: it was backing up to one position before the current tag instead
of at the start of the current tag.

Unfortunately, when the current tag was the first in the document this
would lead the processor to rewind to position `-1`, right before the
start of the document, and lead to errors with `strpos()` when it
received out-of-bounds indices.

In this fix we're correcting the adjustment for the HTML tag's `<` and
documenting the math in the file so that it's clearer why it's there
and providing guidance should another fix be necessary.

As supporting work to this patch we're making the text replacement sort
stable, inside the tag processor, for when determining the order in which
to apply text replacements. This isn't necessary for the runtime but is
a nuissance for testing because different PHP versions produce different
unstable sort orderings and this prevents that from causing the unit
tests to fail in one version but pass in another.

Props to @anton-vlasenko for finding this bug.

Enforce sort stability when flushing out text replacements
github-actions bot referenced this issue Dec 19, 2022
github-actions bot referenced this issue Dec 20, 2022
…'s `raw_content.content` to an empty string if it's `undefined`" (#46600)

* Revert "[`customize-widgets/utils/widgetToBlock`] Initialize a widget's `raw_content.content` to an empty string if it's `undefined` (#46487)"

This reverts commit 271f650.

* Guard against undefined content closer to parse() call
github-actions bot referenced this issue Feb 23, 2023
Co-authored-by: Marco Ciampini <marco.ciampo@gmail.com>
github-actions bot referenced this issue Feb 23, 2023
* Update font origin to match updated API

When fonts are converted to theme.json format, origin is set to `gutenberg_wp_fonts_api`.

* Update font origin set in deprecated WP_Web_Fonts class

---------

Co-authored-by: Tonya Mork <tonya.mork@automattic.com>
@github-actions github-actions bot reopened this Mar 30, 2023
@github-actions github-actions bot reopened this Apr 4, 2023
@github-actions github-actions bot reopened this Sep 15, 2023
github-actions bot referenced this issue Nov 11, 2023
The Top Toolbar was relying on position: absolute; CSS and layoutEffect calculations to display the selected block tools visually within the top toolbar. This PR places it in the header DOM where we want it, allowing us to use native CSS and DOM flow to improve accessibility (tab order matches visual order) and have more maintainable code.

* Imports `<BlockContextualToolbar />` via private-api and the <Popover /> for image captions to the edit site, edit post, edit widgets, and customize widget headers.
* Removes position: absolute; and layoutEffect block toolbar positioning hacks.
* CSS for the top toolbar to use flex-shrink and overflow-x: hidden; to allow for the block toolbar to fit its current space and scroll to reveal the hidden tools.
* With top toolbar mode, Shift+Tab does not go directly to the toolbar but the first tabstop outside of the editor.

Co-authored-by: Alex Lende <ajlende@gmail.com>
Co-authored-by: Andrei Draganescu <me@andreidraganescu.info>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Flaky Test Auto-generated flaky test report issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants