Re: Bikeshed Major Version updates (v6 and v7) and Python min version update (3.12)

FYI, the documentation has not managed to republish since the Python upgrade, even after #3213. I notice the CI workflow failed on snapshots when it was merged?

https://github.com/speced/bikeshed/actions/runs/20051858469/job/57509532505

--Ken

On Thursday, December 11, 2025 3:20:50 PM EST Tab Atkins Jr. wrote:
> On Mon, Dec 8, 2025 at 11:09 AM Kenneth G. Franqueiro
> <kfranqueiro@w3.org> wrote:
> >
> > RE v6, I've run a battery of tests comparing outcomes involving fatal errors in the newest version, as an FYI to anyone wondering if their documents may be affected.
> >
> > The following pass with v5 and fail with v7 (and presumably v6), due to issues with markup:
> 
> Thanks for the check-over! I've confirmed as well that, yes, all of
> these (except css-scrollbars) are markup errors already present in the
> document, that were just silently missed before due to the parser's
> error recovery. Now that Bikeshed is being stricter with its own
> parser, they're getting caught and reported. Some of them definitely
> produced wrong markup in the past (like unclosed <section> elements,
> which wrapped the entire rest of the document in that section...),
> others are more innocuous (like doing <thead><td> - no <tr> around the
> cells) but still definitely an error.
> 
> (The css-scrollbars error was an actual crasher in Bikeshed; since
> fixed in 7.0.2. My testsuite is old enough that it didn't contain that
> spec, and nobody else exercised that precise markup... It's tested now
> in my manual tests.)
> 
> ~TJ
> 
>

Received on Friday, 12 December 2025 13:38:02 UTC