-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Backport WordPress 5.2.1 fixes #15650
Conversation
* Rich Text: Set applied format as active in applyFormats * Rich Text: Update toggleFormat tests per activeFormats revision * Rich Text: Replace existing active format in applied * Rich Text: Remove active format in all cases for removeFormat * Rich Text: Update toggleFormat tests per removeFormats revision * Testing: Update E2E test case to verify link display regression * Rich Text: Verify by test of activeFormats format replacement
I think everything is added now. |
Let's see if the tests pass. |
A recurring error I see in the failing build is this one:
I can reproduce it as well, when trying to ArrowUp / ArrowDown between two paragraphs. There are changes to both |
This error is because we should have kept the In 72539b8, I chose to simply reintroduce the |
There's a build failure caused by the console warnings tracked at Trac#47183 and fixed in master at #15502 . The changes in that pull request affect only tests, and should be safe to pull in here. I'll cherry-pick the merge commit 17c3571 to allow the build to pass. |
* Testing: Skip test failures for font decoding warnings * Testing: Fix Classic block Add Media toolbar button click
@@ -483,5 +483,4 @@ Undocumented declaration. | |||
|
|||
<!-- END TOKEN(Autogenerated API docs) --> | |||
|
|||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've seen this around locally as well sometimes. Why does this happen?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is probably related #15626 I'm investigating it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#15679 should fix it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No I actually had to add empty lines to the previous npm release (because of the failure we had) to force learna to detect these as changed. This just reverts those unnecessary changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No I actually had to add empty lines to the previous npm release (because of the failure we had) to force learna to detect these as changed. This just reverts those unnecessary changes.
Can someone clarify for me: Do these changes matter? Is there anything further which needs to be done in this branch for them?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, nothing left to do here.
Thanks for looking at the test failures, @aduth! I seems there are still two left involving metaboxes. |
The failure seems related to I wonder if it's fine to just ignore this failure? |
I've tracked the build failure to Advanced Custom Fields, specifically these two lines: It's not clear to me yet why (a) this fails specifically on this branch and not others and (b) why or if ACF should be mutating the Worth highlighting that the field being used in the test is not one intended to be managed by ACF, but rather its own custom metabox field: https://github.com/WordPress/gutenberg/blob/master/packages/e2e-tests/plugins/wp-editor-metabox.php |
In master, the specific test case was changed to be skipped due to intermittent failures, perhaps related to the same plugin incompatibility (though not necessarily so, since it was both intermittent, and with a different error message). The relevant pull request was #15211, tracked for reintroduction at #15538 . I will cherry-pick the merge commit 93c5ad3 from #15211 to sync with expected behavior from master. This still means there is a legitimate failure to be addressed, though it is not specific to this branch. |
I'm going to test quickly the fixes cherry-picked here and see if everything works as expected. |
Noting: We probably want to be dropping the commit f004741 before merging. It was included to force Travis to run the tests. Then again, it wouldn't be a terrible thing to have the commit merged into the |
To verify, I applied local changes to unskip the test in the master branch, and with |
Can't approve my own PR. I tested everything (except the google doc thing where it's hard to replicate). Everything seems to work as intended. |
Relevant Trac ticket: https://core.trac.wordpress.org/ticket/47284 |
https://github.com/WordPress/gutenberg/issues?q=label%3A%22Backport+to+WP+Core%22+is%3Aclosed