Sub-theme doesn't inherit base theme default block config

With the docs update, this is a duplicate of #3278410: block_theme_initialize() sledgehammers square blocks into round regions, allow themes to provide a mapping of regions to 'roles' → and related issues.

I'm sorry, how can an issue duplicate a second issue which didn't even exist until seven years after the first issue was created?

@bkline, would you agree that a later ticket could supersede an existing ticket due to some combination of similarity, clarified direction, and traction? In that case, if not "Closed (duplicate)", what alternative?

Just on a cursory review, it seems that #3278410: block_theme_initialize() sledgehammers square blocks into round regions, allow themes to provide a mapping of regions to 'roles' → was spun off from 📌 block_theme_initialize() falls back to putting blocks in the first region it finds, provide a better default Needs work , and these tickets combined are attempting to organize a solution. Is either ticket deficient in some way? Do you have a solution that supersedes the efforts bubbling up in those tickets? If not, marking this ticket as a duplicate may just be a way of, hopefully, limiting duplicate efforts.

Also, it turns out the original ticket, 📌 block_theme_initialize() falls back to putting blocks in the first region it finds, provide a better default Needs work , was created 1 day prior to this one.

Not making an argument for either ticket--haven't dug in enough to have an opinion on that. I do wonder, though,--but don't have time to dig in just now--are any of these efforts a spin off of #37 🐛 Sub-theme doesn't inherit base theme default block config Closed: duplicate ? :)

@jcandan I absolutely agree that it is logical for a later ticket to supersede an earlier ticket. I just don't agree that "supersedes" and "duplicates" are synonyms.