andydotxyz

Well the obvious reason would be if your users may not have Chrome installed?

On a more basic level it comes down to whether you want to code pure Go or HTML/CSS as well...

Unfortunately it is a matter of hours in the day. Accessibility relies on things like focus handling that are just not ready yet. Maybe we released too early or maybe it was sensible to get a basic but solid release together to build on. I expect that time will tell.

Thanks, I think there is a patch nearly ready for that, will roll out a hotfix as soon as that is done and I expect a 1.0.1 in a few days

The biggest reason is that we have not implemented shadows yet... once we have that things may look more like you expect.

Can you help us and report the issue on GitHub please? There must be something different about your interaction or setup as the developers have not seen that app crash in a long time...

For the simple text markup views we will support markdown as it has those features. After that we could consider HTML...

None of those are in yet. Tree views and data grids require a data binding API that we have not yet decided on. HTML view is going to be difficult on Linux as we don’t want to bring in GTK or Qt - but we will get there.

A fair point. At this time it is desktop only but the design of the API does not limit this. People are looking at mobile and web drivers but this will be a fair distance off I expect.

At the moment that is lacking - we intend to add it in a future version as accessibility is important