Since v7, interaction idle spans have been an experimental feature of the SDK. It doesn't seem as if we'd promote them to stable anytime soon but they do take up a bit of bundle size in the SDK.
For v11, we can move them into a dedicated integration and let users who use this experiment migrate over to the dedicated integration.
This came up while we discussed splitting up browserTracingIntegration. Given the option is experimental, I'd suggest we fully extract it out and no longer make it part of the browserTracingIntegration "sub integrations".
Since v7, interaction idle spans have been an experimental feature of the SDK. It doesn't seem as if we'd promote them to stable anytime soon but they do take up a bit of bundle size in the SDK.
For v11, we can move them into a dedicated integration and let users who use this experiment migrate over to the dedicated integration.
This came up while we discussed splitting up browserTracingIntegration. Given the option is experimental, I'd suggest we fully extract it out and no longer make it part of the
browserTracingIntegration"sub integrations".