Change History

A fast look at https://project-gc.com/Challenges/GCBGCK5/109425 shows uses of style and images with set width of 900x850px. I am not sure how those images can be expected to fit. In all honesty, it's very hard for us to make sure that checker output using this amount of customized styling keeps working. But that is also the point of removing inheritance from the site itself and more or less go back to web browser defaults.

I don't know what you want with the second and third to be honest. You don't appreciate the responsive design that it uses its full width? I would say that they look as one should expect. But if you want them less wide, uyou can set style width=auto; on the table element. Or a fixed width if you prefer. Using all width available is the common standard though.


> and just leave everything else to what it was before?

That is not possible. Challenge checkers were using CSS that they shouldn't. We must be able to change CSS of the website itself without changing how third party HTML renders. Our upgrade of Bootstrap proved this quite well. Many challenge checkers started breaking because users relied on the site's own CSS. Which is understandable, but not reasonable.

We are doing this to prevent that these things should happen in the future. Disconnecting the challenge checker output formatting from the site itself.

A fast look at https://project-gc.com/Challenges/GCBGCK5/109425 shows uses of style and images with set width of 900x850px. I am not sure how those images can be expected to fit.
In all honesty, it's very hard for us to make sure that checker output using this amount of customized styling keeps working. But that is also the point of removing inheritance from the site itself and more or less go back to web browser defaults.

I don't know what you want with the second and third to be honest. You don't appreciate the responsive design that it uses its full width? I would say that they look as one should expect. But if you want them less wide, uou can set style=auto; on the table element. Or a fixed width if you prefer. Using all width available is the common standard though.


> and just leave everything else to what it was before?

That is not possible. Challenge checkers were using CSS that they shouldn't. We must be able to change CSS of the website itself without changing how third party HTML renders. Our upgrade of Bootstrap proved this quite well. Many challenge checkers started breaking because users relied on the site's own CSS. Which is understandable, but not reasonable.

We are doing this to prevent that these things should happen in the future. Disconnecting the challenge checker output formatting from the site itself.

A fast look at https://project-gc.com/Challenges/GCBGCK5/109425 shows uses of style and images with set width of 900x850px. I am not sure how those images can be expected to fit.

I don't know what you want with the second and third to be honest. You don't appreciate the responsive design that it uses its full width? I would say that they look as one should expect. But if you want them less wide, uou can set style=auto; on the table element. Or a fixed width if you prefer. Using all width available is the common standard though.


> and just leave everything else to what it was before?

That is not possible. Challenge checkers were using CSS that they shouldn't. We must be able to change CSS of the website itself without changing how third party HTML renders. Our upgrade of Bootstrap proved this quite well. Many challenge checkers started breaking because users relied on the site's own CSS. Which is understandable, but not reasonable.

We are doing this to prevent that these things should happen in the future. Disconnecting the challenge checker output formatting from the site itself.