Oh no.

Someone is approaching.

Seem like not happening on me. Maybe try using external image host (like shota.nu) next time?

Originally in that post, I commented that the bug is caused on Firefox nightly. But later, I find out the bug is caused by misconfigeration of no-scripts, so I detete the comment and post another one.

Maybe I should edit the comment next time. Sorry for inconvenience caused.

In Chinese, we usually read out a date with year first, month latter and days after it. For example, if it’s 4/6/1989 , we would say 一九八九年六月四日 (year 1989, June, day 4). I think there’s not any relation with date format we use.

I reproduce it with no-script addson enable. Should be some wrong setting in the extension cause the problem.

deleted by creator

after a few testing, it seem it is caused by no script of my browser. Thank for your reply.

deleted by creator

Go to your profile and the bug is reproduced.

Sound dumb, but have you switched the write protection of the SD card off? It’s the tiny switch on the side of the SD card.

Yes, you can get it at here

No. I am too broke to buy the license of gnome :(

Thanks for reply. Report on bugzilla

Its runcat, a extension to tell me the current cpu usage. Can also act as a short cut to system monitor, very useful.

Video may not shown in your lemmy client. Use this link instead.

Here is the video

As you can see, scrolling is available for webpage, but not in sub-menu.

I know these two environment, and it helps with webpage scrolling only. In some menu, like history menu, it does not scroll but drag the text only. Better file a bug report.

big thanks for you!!

Also, firefox does not recognize my touchscreen input in a few area. For example, you can not scroll on menu, history, and I am considering to file a report. Does this happen to you? Using Firefox on Wayland.

Mentioned by Philip goto, someone has already filed a report

https://gitlab.gnome.org/GNOME/mutter/-/issues/1523

And I am surprise how the bug exists for years and no-one brother it. Anyway, it’s going to be fixed in future.

Mentioned by Philip goto, it is reported

https://gitlab.gnome.org/GNOME/mutter/-/issues/1523