Some more details for the code block flashing

[StefanSalewski]

Problem

In dark themes, code block flash white when page is (re)-loaded.
I reported that a few times in the last months.

Steps

Try with Mozilla or Chromium

Possible Solution(s)

I just noticed, that only editable code blocks are flashing. Initially I thought that older releases of mdbook might not suffer from this issue, but now I think it is just, that when I started with my book, I initially made the example code not editable.

I think, if this is not fixable, I might make the examples in my book non-editable, than it should load smooth.

Notes

I already suggested an option to copy code directly in the Rust playground (a button, that when clicked opens directly the playground with the code block copied in to edit and run). I guess that would be possible, I have seen that somewhere, and that would avoid this issue :-)

And no, no pull request from my side, I am not a web developer. Perhaps AI will be able to provide a PR soon.

Version

latest.

[shenef]

Instead of opening an issue and closing it shortly after (see #2502 and #2546), you could try leaving them open so a dev actually looks into it.
Closing the issue suggests that it has been resolved and that there is no more need to look into it.

[StefanSalewski]

Sometimes issues are just closed not because being resolved, but for other reasons, e.g. because the maintainer is not interested in fixing it, or can not even verify it. Some projects even close issues by bots after some time. I think my issues has been open for maybe one or two weeks, without a reply of someone. As I was not able to contribute more myself, I think it was a justified action to close them then. Reopen my old issues might have been an option, but then the issue looks old, and often no one cares at all for very old issues (I know that from other projects). And is it not the case that the maintainers gets an email for issues? For my github projects, I typically get informed via email if someone reports it, so closing at github is OK, as the mail should persists. And finally, if I remember correctly, mdbook has already a number of open issues, so I assume the authors might be quite happy when users close minor issues themselves.

[szabgab]

If you manage to resolve the issue yourself locally, then IMHO the best thing is to comment on your issue explaining how you managed to do that and then close it.

If you don't care about the issue any more, comment that and close it.

Otherwise keep it open. It might take time, but someone will look at it and might comment on it or even help solving it.