зеркало из https://github.com/mozilla/gecko-dev.git
9a81f2437f
KeyframeEffect and KeyframeEffectReadOnly constructors can run in the caller compartment, which is okay because the current compartment is used in the following places and all of them are safe: 1. GlobalObject::CallerType(), that is ultimately passed to nsDocument::IsWebAnimationsEnabled in KeyframeEffectParamsFromUnion, to decide whether to copy mIterationComposite/mComposite to KeyframeEffectParams. GlobalObject::CallerType() can now be different than the target window's one, if the caller has the system principal and the target is web content, and in that case nsDocument::IsWebAnimationsEnabled there always returns true while Web Animations can be disabled on web content. honoring the mIterationComposite/mComposite properties is OK, since it just changes the animation behavior, and this is disabled by default until remaining spec issues are resolved. 2. GlobalObject::Context(), that is ultimately passed to KeyframeUtils::GetKeyframesFromObject and used while extracting information from passed-in keyframe object, with iterable/iterator protocols. Performing that operation in the caller side is okay, since the same thing can be done on caller, and the operation doesn't perform any GCThing allocation on the target window global. |
||
|---|---|---|
| .. | ||
| file_animate_xrays.html | ||
| test_animate_xrays.html | ||
| test_animation_observers_async.html | ||
| test_animation_observers_sync.html | ||
| test_animation_performance_warning.html | ||
| test_animation_properties.html | ||
| test_cssanimation_missing_keyframes.html | ||
| test_generated_content_getAnimations.html | ||
| test_keyframe_effect_xrays.html | ||
| test_running_on_compositor.html | ||
| test_simulate_compute_values_failure.html | ||