Closed Bug 1559231 Opened 1 year ago Closed 1 year ago

[motion-1] Support offset-anchor

Categories

(Core :: CSS Transitions and Animations, enhancement, P3)

enhancement

Tracking

()

RESOLVED FIXED
mozilla70
Tracking Status
firefox69 --- wontfix
firefox70 --- fixed

People

(Reporter: boris, Assigned: boris)

References

(Blocks 1 open bug, )

Details

(Keywords: dev-doc-complete)

Attachments

(2 files)

Support <offset-anchor>, which defines an anchor point of the box positioned along the offset path. The anchor point specifies the point of the box which is to be considered as the point that is moved along the offset path.

OS: Unspecified → All
Hardware: Unspecified → All
Assignee: nobody → boris.chiou
Keywords: dev-doc-needed
Summary: Support <offset-anchor> → [motion-1] Support <offset-anchor>
Depends on: 1568370
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/18259 for changes under testing/web-platform/tests
Upstream web-platform-tests status checks passed, PR will merge once commit reaches central.
Upstream PR was closed without merging

Thanks. Didn't see this on my try yesterday. Probably need to rebase these patches.

Flags: needinfo?(boris.chiou)
Upstream web-platform-tests status checks passed, PR will merge once commit reaches central.
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla70

Just to be clear on this, offset-anchor and the other Motion Path features are still behind the layout.css.motion-path.enabled preference and do not ship with Firefox 70, right?

Sebastian

Flags: needinfo?(boris.chiou)
Summary: [motion-1] Support <offset-anchor> → [motion-1] Support offset-anchor

(In reply to Sebastian Zartner [:sebo] from comment #14)

Just to be clear on this, offset-anchor and the other Motion Path features are still behind the layout.css.motion-path.enabled preference and do not ship with Firefox 70, right?

Sebastian

Yes. All motion properties, including offset-anchor, are still behind layout.css.motion-path.enabled, which is disabled on beta/release. Later (perhaps Q4), I will file a bug which ships these properties, and will mark it dev-doc-needed and cc you. (of course, will send a intend to ship mail).

Flags: needinfo?(boris.chiou)

(In reply to Boris Chiou [:boris] from comment #15)

(In reply to Sebastian Zartner [:sebo] from comment #14)

Just to be clear on this, offset-anchor and the other Motion Path features are still behind the layout.css.motion-path.enabled preference and do not ship with Firefox 70, right?

Sebastian

Yes. All motion properties, including offset-anchor, are still behind layout.css.motion-path.enabled, which is disabled on beta/release. Later (perhaps Q4), I will file a bug which ships these properties, and will mark it dev-doc-needed and cc you. (of course, will send a intend to ship mail).

Perfect! Thanks a lot! Normally, the dev-doc-needed flag wouldn't be needed for this then, because it's already mentioned at the Experimental Firefox features page and is not riding the trains yet, but I'll use it to document the property itself in preparation.

Sebastian

I've done some documentation for this property; see https://github.com/mdn/sprints/issues/2105#issuecomment-532633814 and the comments below that one for all the details.

A review would be really great if you get the time; thanks!

I have set this bug to dev-doc-complete; we'll track docs work to update the browser compat data in the release bug when it appears.

Blocks: 1582554
You need to log in before you can comment on or make changes to this bug.