This is unrelated to core.
We can’t known all CPT a user is going to add, it is task of the person or code that adds said CPT to add this to the widget.
It’s my belief that this petition isn’t asking for support for a specific CPT; I think it’s asking for support for any CPT that happens to be active which would be a reasonable request. There’s core functions to determine which CPTs are active, so, this would be trivial to implement if it had the votes.
And if I want to remove one of the 10 CPTS I have?
What would I do to remove the special CPT (lets say I have a “contacts” CPT that I do not want in said widget)
Unless this would allow with a setting to control each CPT, like any plugin that allows you to register CPT does already, I don’t agree that this should be in core.
We wold not only clutter said widget but also make it harder to control - as now I can add, but if Core adds for me, how to I remove? I would need a setting specified in core, which makes all current existing settings in plugins obsolete or would have to change from “ADD” to “REMOVE”
I was just leaving some notes in case it ended up getting the votes. I didn’t vote for it and don’t think it should go into core.
In actuality, I don’t ever use the At a Glance widget. I think of it more like the Just Barely a Glimpse widget. Instead, I’ve concocted the Site Overview widget which displays much more site data (including my CPTs) and offers a lot of quick admin navigation.