BD103

#12305 is a feature that fits the best in `bevy_dev_tools`. What needs to be done for this PR to be merged, to unblock the simplified backtraces one?

My first thoughts are to feature flag it something like this, but it could be confusing: ```rust { let system = ui_stack_system .in_set(UiSystem::Stack) // the systems don't care about stack...

> system `extract_uinodes` should not be behind the `bevy_text` feature, it can work without changes without `bevy_text` I believe I fixed this in b236ab5679287e7f8552fb662d1a2d9753a7651c.

I'm considering moving all of the `#[cfg(feature = "bevy_text")]` statements to a separate function, that way we only have to use the `cfg` attribute once. ```rust #[cfg(feature = "bevy_text")] fn...

Closing this because #12973 has been created for `accesskit_winit` 0.19.

@doonv would you mind rebasing this onto main?

I feel like implementing this without hardcoding individual features' extensions would be very difficult. The point of features is that disabling them prevents them from ever being compiled, so `bevy_asset`...

See https://github.com/AccessKit/accesskit/issues/233 and #8258 for details. This should probably be combined with #12973.

See #12974, #8258, and https://github.com/AccessKit/accesskit/issues/233 for details.

See #11466, specifically [James's comment](https://github.com/bevyengine/bevy/pull/11466#issuecomment-1905324746), for a history on why this is blocked. I'm not sure if it still applies or not.