You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just curious if there's any way to control the execution order of plugins... I ran into a conflict where one plugin was trying target elements by id but the removeAttrs plugin had already been run—and it was configured to remove the id attribute! Obviously, the order the plugins are executed would make a difference in this case...
The text was updated successfully, but these errors were encountered:
Thanks for clarifying, @GreLI. Turns out that my issue was actually the cleanupIDs plugin running before the removeElementsByAttr—which I had configured to remove an element by ID but by that time the ID had already been removed.
Easy fix was to explicitly declare the cleanupIDs plugin in my config after the removeElementsByAttr plugin.
I wonder if it's worth giving removeElementsByAttr a little more priority in the order of execution... Seems like there could definitely be conflicts with cleanupAttrs and cleanupIDs.
Just curious if there's any way to control the execution order of plugins... I ran into a conflict where one plugin was trying target elements by
id
but theremoveAttrs
plugin had already been run—and it was configured to remove theid
attribute! Obviously, the order the plugins are executed would make a difference in this case...The text was updated successfully, but these errors were encountered: