You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently updated my book to the latest mdbook version.
Unfortunately the flashing of code blocks in dark themes that I reported some months ago is still there. Do you think it can't be avoided? Perhaps, but my feeling is that other pages don't show this behaviour, even old mdbook pages. And my feeling is, that when I started with my book in October 2024 with mdbook versions < 0.4.43 I have not seen that flashing.
The other issue that was observed first in v0.4.43 and is still present in v0.4.44 is that with "mdbook serve --open" sometimes code blocks have no syntax highlighting. I have observed that again yesterday. It occurs rarely, but we get always a tiny shock thinking that there is an issue in the Markdown we wrote, but then discovering that it is only a random issue fixed by a page reload.
I should admit that I tested only with Firefox -- currently with version 135.0. Do you think it might be a Firefox issue? I don't think so, but it would be difficult for me to test with another browser, sorry. And it is on Gentoo Linux with Gnome and Wayland.
Best regards,
Dr. Stefan Salewski
The text was updated successfully, but these errors were encountered:
$ mdbook --version
mdbook v0.4.44
Hello.
I recently updated my book to the latest mdbook version.
Unfortunately the flashing of code blocks in dark themes that I reported some months ago is still there. Do you think it can't be avoided? Perhaps, but my feeling is that other pages don't show this behaviour, even old mdbook pages. And my feeling is, that when I started with my book in October 2024 with mdbook versions < 0.4.43 I have not seen that flashing.
The other issue that was observed first in v0.4.43 and is still present in v0.4.44 is that with "mdbook serve --open" sometimes code blocks have no syntax highlighting. I have observed that again yesterday. It occurs rarely, but we get always a tiny shock thinking that there is an issue in the Markdown we wrote, but then discovering that it is only a random issue fixed by a page reload.
I should admit that I tested only with Firefox -- currently with version 135.0. Do you think it might be a Firefox issue? I don't think so, but it would be difficult for me to test with another browser, sorry. And it is on Gentoo Linux with Gnome and Wayland.
Best regards,
Dr. Stefan Salewski
The text was updated successfully, but these errors were encountered: