Hi @thlassche. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.

❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

@thlassche wasn't it fixed in #38276 ?
Ah, looks like we had a similar fix in #38537

@magento run all tests

@magento run all tests

@magento give me test instance

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.

Hi @engcom-Bravo, here is your Magento Instance: https://16dd4518b17f0dfee16359646226dbfd.instances-prod.magento-community.engineering
Admin access: https://16dd4518b17f0dfee16359646226dbfd.instances-prod.magento-community.engineering/admin_9c6d
Login: 365088d2
Password: 6d2b5eb3900a

Hi @thlassche,

Thanks for the collaboration & contribution!

✔️ QA Passed

Preconditions:

• Install fresh Magento 2.4-develop

Steps to reproduce

• Edit category in the backend on storeview level
• Untick the box 'Use default value' next to the category description field WYSWYG editor
• Enter a description in the WYSIWYG editor
• Save

Before: ✖️ 

After: ✔️  

Builds are failed. Hence, moving this PR to Extended Testing.

Thanks.

@magento run all tests

@magento run Functional Tests EE,Functional Tests CE,Functional Tests B2B,WebAPI Tests,Integration Tests

@magento run Functional Tests EE,Functional Tests CE,Functional Tests B2B,Integration Tests,WebAPI Tests

@magento run all tests

Functional Test B2B, Functional Test CE, Functional Test EE contain known failures.
Below is the list of known failure along with the Internal JIRA.
ACQE-6487 - StorefrontSelectedByQueryParamsConfigurableOptionsThumbImagesTest
ACQE-6590 - AdminCheckConfigurationForPayPalExpressCheckoutInUnitesStatesTest
ACQE-6523 - AdminReorderWithCatalogPriceRuleDiscountTest
ACQE-6331 - StorefrontCreateOrderAllQuantityGroupedProductOptionDefaultStockTest
ACQE-6423 - ApplyTaxesAndFptForSimpleProductWithCanadianPstOriginTest
ACQE-5677 - StorefrontQuoteCanBeRenamedUntilLockedTest

Hence Moving it to merge in Progress

This critical bug is still present in Magento 2.4.7-p4
It's been almost a year and this serious issue has not been merged to latest version yet.

@maluda259, it was added to 2.4.8-beta1 and 2.4.8-beta2.
I'm not sure if it will be ported to 2.4.7 since it should receive the only security updates

No one has appeared to mention, Fixed via QPT

ACSD-64467

https://github.com/magento/quality-patches/blob/master/patches/os/ACSD-64467_2.4.7-p3.patch

I just don't understand how these sort of bugs keep on getting introduced into Magento releases. Everytime we upgrade, we are faced with the pain of having to work out why random functionality stops working properly, and it's bad for business and bad for reputation. QA testing needs to be significantly improved imho.