Description
Preconditions (*)
Magento 2.3.5
Magento 2.4-develop
Steps to reproduce (*)
Search for the string $this->_isScopePrivate = true inside vendor/magento.
Expected result (*)
Since using the $_isScopePrivate property in blocks is obsolete and will not work properly, it should not be used by any block provided by Magento 2.
Actual result (*)
More than 80 (eighty) blocks use that property, potentially leading to unexpected results, because Do not use the $_isScopePrivate property in your blocks. This property is obsolete and **will not work properly**.
Thoughts
Fixing this issue is nearly impossible for developers. It mean overriding every blocks that use that property. This needs to be fixed upstream. Or if the property works, the documentation needs to be updated.
As a matter of fact, it created some strange cache issues on blocks inheriting from \Magento\Checkout\Block\Onepage\Link where the block would first appear as expected then be replaced a few tenth of seconds later by a previsously cached version, probably grabbed from the local storage.
As long as this issue has not been fixed, we can't trust any of the 80+ concerned blocks: instanciation one of them or inheriting from one of them can lead to unexpected results.
Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.
- Severity: S0 - Affects critical data or functionality and leaves users without workaround.
- Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
- Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
- Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
- Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status