Sounds like it will be tricky to fix in IE, and maybe even the current version of Edge:

https://developer.mozilla.org/en-US/docs/Web/CSS/overscroll-behavior
https://stackoverflow.com/questions/23502941/preventing-overscroll-in-internet-explorer-11

Not an issue in Chrome or Firefox.

Maybe get rid of the status bar at the bottom? What purpose does it serve?

The documentation is lacking or outdated in a lot of areas ; a lot of spelling errors and bad translations are also present. I open this issue to break the problem in smaller tasks so we can see how we progress (plus ticking checkmarks is quite enjoyable don't you think ? ^^)

Some items are already done and up-to-date, and I have probably forgotten a bunch of things too. Please correct me below

I want to extract string from PDF. How to achive it with this library.
PDFTextExtractor class from PdfSharp seems to be missing.

Clay currently misses a few vital pieces of documentation that need to be added in the future. Preferably before the next version is released however, in my opinion, this is not a blocking issue.

The documentation that should written or modified:

• an usage man page
• a configuration man page
• sphinx documentation
• an rst version of the README for PyPy
• improved do

• Shorter demo.
• No errors shown
• No need to select sRGB colors
• Demonstrate other color spaces
• Maybe some subtitles could help

They exist, and can be manipulated in Rust with symlink_file and symlink_directory.

I don't know yet if we need to encode the distinction between file and directory symlinks in the entry kind.

We need to migrate the wiki documentation to the section being created within the OnixJS-System.

Right now all OS installs of HNN require a git clone. This conflates user installs with developer workflow. It would be nice if the install was a self-executable file for Windows and a .pkg for Mac. The number of binary downloads would be easy to track. Developer code pulls would still be tracked by git clones and upgrades could be tracked by Docker Hub downloads.

I've had feedback from a user saying that the current guide available here isn't suitable for some visually impaired users.

The user finds it difficult to make use of videos as they don't offer detail on the scale they need and they also found it difficult to make use of the screenshots provided a