I am aware of issues. Note that this is not a "website" in the regular sense of the word. This is actually a TUI app written in rust and compiled to wasm (and other platforms too: https://github.com/ronilan/incredible/releases) as parrt of alpha testing of the Incredible TUI framework.
Creating the screen, reading a markdown file, laying out the text, colouring it, enabling the scroll, managing it, changing the mouse pointer over the scroll bar, responding to the drag on said scroll bar, underlining the links, colouring them when they are hovered, removing colour when they are not, inverting them when they are clicked, loading the next markdown page, changing the browser URL hash, the keyboard shortcuts, Ctrl+e to select all, Ctrl+c to copy, etc. - it's all coming from Incredible TUI framework, not the browser.
I'd make a website with regular website technologies, and then create some view/iframe/page that has the usable TUI in the browser (if that's the concept). Keep pages that are mainly text / docs in that standard tech, these oddities and overrides are better when the user knows it's going to happen, or another way
1. landing page, normal tech so you don't turn people off immediately
2. app/tui page, linked to from landing page letting the user know you did some cool rust/wasm/tui thing, don't necessarily have to call out scroll issues, it will be understood/accepted by way of the weird web tech they have clicked through to
nice, one thing you might also do, in your wasm version, is figure out how to replicate scroll momentum, that's the thing that makes it feel weird, I can flick a page and it will scroll for a while
I tried to methods to get that effect and both cases it felt worse than the current. Will circle back to that sometime maybe. Touch support in a TUI framework is little of an edge case..
Page up/down, home/end doesn't work. Page scrolling (by pressing/holding above/below the handle in scrollbar) is not working. No button up/down in scrollbar (and ability to just hold them to continue scrolling) - I guess this is optional for "cleanliness". Pressing space key doesn't scroll one page down. Scroll speed when using scroll wheel is too slow.
Scrolling while selecting text (by moving mouse above or below where page is on screen) doesn't work. In the past I managed to get mouse events outside of the page area by attaching the mouse handler to "window" instead of "document" (at least in Firefox at the time, not sure about Chrome).
Text selection should highlight a character when the mouse is beyond mid point and not after the whole character. Double clicking should highlight a word, triple clicking should highlight a paragraph. When clicking more times it should cycle. It should also support dragging after double/triple click to continue selection of more words/paragraphs.
URLs are not shown when hovering over links. Ideally some invisible overlay that is actually a real link would be preferrable. This way all the ways to open links would work.
I think it could be solved by either using float values for the coordinates (probably not desirable), having some extra native properties in the event or by passing the coordinates based on the mid point while dragging (but not for the initial press so clicking is not affected).
I am aware of issues. Note that this is not a "website" in the regular sense of the word. This is actually a TUI app written in rust and compiled to wasm (and other platforms too: https://github.com/ronilan/incredible/releases) as parrt of alpha testing of the Incredible TUI framework.
Creating the screen, reading a markdown file, laying out the text, colouring it, enabling the scroll, managing it, changing the mouse pointer over the scroll bar, responding to the drag on said scroll bar, underlining the links, colouring them when they are hovered, removing colour when they are not, inverting them when they are clicked, loading the next markdown page, changing the browser URL hash, the keyboard shortcuts, Ctrl+e to select all, Ctrl+c to copy, etc. - it's all coming from Incredible TUI framework, not the browser.
Feedback on all aspects much appriciated.