Fix a broken-macros

[skyclouds2001]

Description

Motivation

Additional details

Related issues and pull requests

[github-actions]

Preview URLs

• /en-US/docs/Web/CSS/@view-transition

Flaws (48)

URL: /en-US/docs/Web/CSS/@view-transition
Title: @view-transition
Flaw count: 48

• macros:
  • Wrong xref macro used (consider changing which macro you use). Error processing path /en-US/docs/Learn/CSS
  • Wrong xref macro used (consider changing which macro you use). Error processing path /en-US/docs/Learn/Getting_started_with_the_web/CSS_basics
  • Wrong xref macro used (consider changing which macro you use). Error processing path /en-US/docs/Learn/CSS/First_steps
  • Wrong xref macro used (consider changing which macro you use). Error processing path /en-US/docs/Learn/CSS/First_steps/What_is_CSS
  • Wrong xref macro used (consider changing which macro you use). Error processing path /en-US/docs/Learn/CSS/First_steps/Getting_started
  • and 43 more flaws omitted

[wbamberg]

Suggested change

	In addition to the `@view-transition` at-rule, we define two {{cssxref("@keyframes")}} animations and use the {{cssxref("animation")}} shorthand property to apply those keyframe animations to the elements in the outbound ({{cssxref("::view-transition-old()")}}) and inbound ({{cssxref("::view-transition-new()")}}) pages that we want to animate.
	In addition to the `@view-transition` at-rule, we define two {{cssxref("@keyframes")}} at-rules and use the {{cssxref("animation")}} shorthand property to apply those keyframe animations to the elements in the outbound ({{cssxref("::view-transition-old()")}}) and inbound ({{cssxref("::view-transition-new()")}}) pages that we want to animate.

Maybe? The double plural "keyframes animations" is ugly.

[skyclouds2001]

Suggested change

	In addition to the `@view-transition` at-rule, we define two {{cssxref("@keyframes")}} animations and use the {{cssxref("animation")}} shorthand property to apply those keyframe animations to the elements in the outbound ({{cssxref("::view-transition-old()")}}) and inbound ({{cssxref("::view-transition-new()")}}) pages that we want to animate.
	In addition to the `@view-transition` at-rule, we use {{cssxref("@keyframes")}} at-rule to define two keyframe animations and use the {{cssxref("animation")}} shorthand property to apply those keyframe animations to the elements in the outbound ({{cssxref("::view-transition-old()")}}) and inbound ({{cssxref("::view-transition-new()")}}) pages that we want to animate.

maybe it is better?

[skyclouds2001]

Suggested change

	In addition to the `@view-transition` at-rule, we define two {{cssxref("@keyframes")}} animations and use the {{cssxref("animation")}} shorthand property to apply those keyframe animations to the elements in the outbound ({{cssxref("::view-transition-old()")}}) and inbound ({{cssxref("::view-transition-new()")}}) pages that we want to animate.
	In addition to the `@view-transition` at-rule, we use {{cssxref("@keyframes")}} at-rule to define two keyframe animations and use the {{cssxref("animation")}} shorthand property to apply those keyframe animations to the elements in the outbound ({{cssxref("::view-transition-old()")}}) and inbound ({{cssxref("::view-transition-new()")}}) pages that we want to animate.

maybe it is better?

[wbamberg]

why do you like this better? I must say I prefer my version, but perhaps I'm missing something?

(one reason I prefer mine is that "we use @keyframes at-rule" is not grammatical, "we use two @keyframes at-rules" would be, but then "we use two @keyframes at-rules to define two keyframe animations" is very repetitive)