Add option to block animation on <title> tag

[eoghanmurray]

These can generate massive recordings on some websites (think scrolling title tag)

[jlalmes]

I am making use of the <title> in recordings. I think it's fine to offer the option to ignore changes, but maybe removing changes from recordings by default when slimDOMOptions is set to all is an unintended breaking change?

Use case - when recording SPAs I would like the <title> value to update when navigating from page to page.

[Yuyz0112]

good point @jlalmes

[eoghanmurray]

Great spot, thanks @jlalmes ... in light of that, maybe it should be a throttling thing?
In the mean time I'll update so that you have to explicitly turn this on, rather than including it with all as you suggested.

[eoghanmurray]

Actually @jlalmes, the intention of the 'all' is to enable all slim dom options — there is also a true option which is there to enable all 'safe' options (for some definition of 'safe').
Do you think you should change to using true or is that difference non-obvious?

This also reminds me that I've got some code external to rrweb which detects Single Page App url changes, but only if they happen in tandem with a <title> tag change. If I were to integrate that in rrweb it would introduce a new event, analogous to the Meta event to record SPA navigation. (this wouldn't get recorded if just the URL changed). Would that be useful?

[jlalmes]

Do you think you should change to using true or is that difference non-obvious?

Good idea! I will look into that.

This also reminds me that I've got some code external to rrweb which detects Single Page App url changes, but only if they happen in tandem with a <title> tag change. If I were to integrate that in rrweb it would introduce a new event, analogous to the Meta event to record SPA navigation. (this wouldn't get recorded if just the URL changed). Would that be useful?

Yes, a PageNavigation event would be really useful I think. I imagine we would want this event to fire even if the <title> tag doesn't change, however, I'd be interested to take a look at your implementation of this & collaborate on a PR.

[Juice10]

This looks good, it's missing a type, and would also be great to have a test.
Is also missing a changeset, but this is a pretty old PR so that's totally understandable. Apart from that this looks good!

[changeset-bot]

🦋 Changeset detected

Latest commit: 2887191

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 8 packages

Name	Type
rrweb-snapshot	Patch
rrweb	Patch
rrdom	Patch
rrdom-nodejs	Patch
rrweb-player	Patch
@rrweb/types	Patch
@rrweb/web-extension	Patch
rrvideo	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[eoghanmurray]

I thought I satisfied all the requested changes, not sure how to indicate that!

[eoghanmurray]

OK I guess my force push messed things up, as it can't find the commits the requested changes were attached to!

[Juice10]

This will fix the issues with CI not passing on this PR: #1500