Accurate sizes: Get accurate sizes base on ancestor block context

[mukeshpanchal27]

Summary

• Introduces an initial proof of concept (POC) to return accurate sizes based on ancestor block context.
• This PR does not address all the use cases described in Incorporate layout constraints from ancestor blocks into the sizes calculations #1511.
• Includes some unit tests that may require updates or extensions.
• Additional unit tests will be added in future iterations.

See #1511

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.59%. Comparing base (7757e50) to head (80cc029).
Report is 16 commits behind head on feature/1511-incorporate-layout-constraints-from-ancestors.

Additional details and impacted files

@@                                      Coverage Diff                                       @@
##           feature/1511-incorporate-layout-constraints-from-ancestors    #1818      +/-   ##
==============================================================================================
+ Coverage                                                       69.41%   69.59%   +0.18%     
==============================================================================================
  Files                                                              86       86              
  Lines                                                            7006     7018      +12     
==============================================================================================
+ Hits                                                             4863     4884      +21     
+ Misses                                                           2143     2134       -9     

Flag	Coverage Δ
multisite	69.59% <100.00%> (+0.18%)	⬆️
single	39.66% <100.00%> (+0.23%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[mukeshpanchal27]

@joemcgill This one ready for your review.

[mukeshpanchal27]

The PR is ready for internal review.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: mukeshpanchal27 <[email protected]>
Co-authored-by: swissspidy <[email protected]>
Co-authored-by: westonruter <[email protected]>
Co-authored-by: felixarntz <[email protected]>
Co-authored-by: phanduynam <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[swissspidy]

What‘s with the failing tests?

[mukeshpanchal27]

What‘s with the failing tests?

In 3a51aed it will skip failed tests for WordPress versions lower than 6.8

[westonruter]

Each of the tests has the exact same sizes attribute: sizes="(max-width: 413px) 100vw, 413px".

Is this expected?

[mukeshpanchal27]

Yes, this is expected as it end up to the default alignment any of it's parents or image alignment as default alignment. In bba4997, I added more variations of alignment options.

[felixarntz]

@mukeshpanchal27 This looks really good, just a few questions.

[felixarntz]

Thanks @mukeshpanchal27 for the updates, looks great!