Felix Schütt

Thanks for fixing it, but I'd rework the implementation a bit so it's easier to understand what's going on (and add comments for future maintainers). I'll do a review later.

Just wanted to say, I haven't forgotten about this, but there are large refactorings in progress right now, may take a while to get merged.

Yeah, I think I'll manually implement and check this again, I committed some huge files into git early on and needed to remove them via git-bfg, so this PR is...

I won't merge this right now, because this problem might be already fixed on the `positioned_words` branch - there are a lot of changes in that branch that may already...

> May I suggest to put the guide directly on the readme on Github The guide would get too long, I originally used the GitHub wiki, but I also didn't...

The release links are broken because there is no release yet. So far I've only uploaded the_ linux `libazul.so` and other files, for example the API header: https://azul.rs/release/nightly/files/azul.h The links...

yeah, also that's a relatively old version by now. I should do another release.

No, there is no accessibility yet and it's not planned. While it's not impossible to support it in the future, it's a lot of work to implement, since every platform...

On Windows, there are two APIs: Microsoft Active Accessibility, and the newer way of using Microsoft UI Automation. Most of the documentation is written for .NET (what a surprise), but...

I've added stub APIs (you can target them, but they don't do anything yet): https://azul.rs/api/1.0.0-alpha1#Dom.set_accessibility_info https://azul.rs/api/1.0.0-alpha1#st.AccessibilityInfo Since Azul is now MPL-2.0 licensed (same as Firefox), my plan for handling a11y...