Preload: fix settings fields order

[ellatrix]

What?

See #66459 (comment). The fields were added to preload, but the order was not maintained.

We should somehow add e2e tests for this at some point. Perhaps check that there are no network requests before the iframe loads or something.

Why?

The order must match in order for the preload to be used.

How?

Testing Instructions

Testing Instructions for Keyboard

Check the network tab for the site editor.

Screenshots or screencast

[Mamaduka]

Good catch! Thanks, @ellatrix!

We should somehow add e2e tests for this at some point. Perhaps check that there are no network requests before the iframe loads or something.

That would be great!

[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: ellatrix <[email protected]>
Co-authored-by: Mamaduka <[email protected]>

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

[github-actions]

Flaky tests detected in cc98867.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/12105527071
📝 Reported issues:

• [Flaky Test] submenu click on the arrow interactions #61884 in /test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js

[gigitux]

Thanks for catching this! 🙇