Skip to content

Move animatetransform example section after DOM interface - #46433

Merged
Josh-Cena merged 1 commit into
mainfrom
svg-element-section-order
Nov 9, 2026
Merged

Josh-Cena merged 1 commit into
mainfrom
svg-element-section-order

Conversation

@caugner

@caugner caugner commented Nov 9, 2026

Copy link
Copy Markdown
Collaborator

Description

Move the "Examples" section after "Attributes" and "DOM Interface" on one SVG element page, to match the majority order used by the other SVG element pages.

  • web/svg/reference/element/animatetransform: move "Examples" to after "DOM Interface".

Motivation

While looking into the section order of SVG element pages, I found that some pages don't follow the majority order used by the rest of their page type. The SVG element page template uses the same order. A consistent order makes it easier for readers to find the same section in the same place on every page, and gives authors a clear pattern to copy.

Additional details

Sections are moved as-is; their content is unchanged.

Related issues and pull requests

@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Preview URLs (1 page)

@caugner
caugner marked this pull request as ready for review November 9, 2026 17:57
@caugner
caugner requested a review from a team as a code owner November 9, 2026 17:57
@caugner
caugner requested review from chrisdavidmills and removed request for a team November 9, 2026 17:57
@Josh-Cena

Copy link
Copy Markdown
Member

@caugner Just FYI: pull_request_target will be blocked in public repos, so the PR labeler action didn't run. If it's not an action item already, the engineering team probably needs to prioritize migrating all actions off pull_request_target.

@Josh-Cena
Josh-Cena merged commit 0a6ff1e into main Nov 9, 2026
13 checks passed
@Josh-Cena
Josh-Cena deleted the svg-element-section-order branch November 9, 2026 19:23
@caugner

caugner commented Nov 9, 2026 •

Copy link
Copy Markdown
Collaborator Author

Just FYI: pull_request_target will be blocked in public repos, so the PR labeler action didn't run. If it's not an action item already, the engineering team probably needs to prioritize migrating all actions off pull_request_target.

This was moved to December, see: https://github.blog/changelog/2026-11-02-pull_request_target-blocked-by-default-december-2/

In this case, the action failed (as part of the brownout schedule): https://github.com/mdn/content/actions/runs/42673591870

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants