Kim Mantas

Convert ModuleManagement to ApplicationV2

1

## Related Issues - https://github.com/foundryvtt/foundryvtt/issues/11643

`FormDataExtended` explicitly checks for `element.closest("fieldset")?.disabled`, but this should not be necessary as all elements descended from a `disabled` `` are already considered `disabled`. Having this explicit check also catches elements...

It seems most browsers now ship with native `Set` operation implementations, so we do not need to maintain our own anymore. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set

Currently we use `cloneNode`, but this is wasteful.

Refactor roll pipeline

1

There are two main goals for this refactor: 1. Separate out the various 'options groups' that are passed around as part of a roll. At the moment these are all...

This option will not bundle an electron binary, and will include cross-platform native `node_modules` dependencies.

## Related Issues - https://github.com/foundryvtt/foundryvtt/issues/11550 - https://github.com/foundryvtt/foundryvtt/issues/11551

Share image function transmits title over socket rather than fetching it from the related object

2

Originally reported by Mana#4176 https://discord.com/channels/170995199584108546/956306859491471420/1076379269674049626 **ALL MODULES DISABLED?** true **OS, Hosting, Browser (if applicable):** any **Short Description of bug:** Share image function for actors and items transmits title over socket...