And change the description for one of the describe blocks, which may
have been a copy-paste leftover as there's an existing describe block
with the exact same sentence. Change this to accurately describe that
we are testing without the form's input values (as we're using
replace() directly instead of submit()).
Tailwind has a similarly-named 'pulse' animation that behaves differently:
it makes the element fade in and out.
Meanwhile, it has a 'ping' animation that behaves similarly to our 'pulse'
animation: https://tailwindcss.com/docs/animation
Follow the Tailwind names to avoid confusion. In the future, we might
want to implement a similar 'pulse' animation. Or, perhaps we can reuse
Tailwind's animations as-is.
In 5a8c33f34a the minimum version was set to 7.3 to allow use of the long-form `--fail-on-warning` option, but this is not compatible with Python 3.8. Revert this to the original `-W` option and set 7.0 as the minimum version.
Also deprecate the `window.ActivateWorkflowActionsForDashboard` and
`window.ActivateWorkflowActionsForEditView` functions as they no longer
need to be globally-accessible
This reverts commit b3846a63fc.
It's a partial revert as the changes to DropdownController itself is
still useful, since it allows us to target the 'shown' event on the more
specific element instead of the document.
This allows us to more easily hook up any event listeners for elements in the dropdown on init. Without keeping it mounted, Tippy will immediately unmount the content, making it impossible for attaching event listeners without listening for the dropdown's show event
We want to make sure the feature works (without the new version
detection) when using a snippet model that does not use RevisionMixin.
We don't have any tests that ensures the new version detection works
with a RevisionMixin-enabled snippet. We can add those later, but the
code itself doesn't make a special-case between snippet vs pages, so
it's probably okay to skip them.
This will simplify the logic when we come to incorporate revision data, since A) we have a lookup by user ID to work with, and B) if a user has multiple sessions AND a revision, we'd have to arbitrarily choose one session to attach the revision data to.