igozalishvili

To a degree that is what we are doing here. There are some technical difficulties there and we plan to write followup post on that as well. That being said having a visual representation of the navigation trail is very useful even if it's just to gain ability to jump few steps back rather than going step by step.

One of the primary goals of this UX is to address that specific problem. It may not be the best UI for that specific task, but that's not only use case it supposed to serve. I would also argue it's far better UI than ones present in the current browsers.

If you have any specific suggestions how to improve UI to make it even better for that use case we'd be happy to get feedback.

Some of what you describe here is on the table and we plan on sharing details on that in the followup posts.

1. That is intentional UX decision. 2. That is known bug, that hopefully will be fixed soon. https://github.com/servo/servo/issues/11937

There are several issues at play here, native keybindings for input fields has not being fully implemented in servo yet.

As of auto complete, few people have reported issues. In our testing we did not run into this issue. Right now we have an issue and a reproducible test case to tackle this issue: https://github.com/browserhtml/browserhtml/issues/1157

Feel flee to report more browser.html issues here: https://github.com/browserhtml/browserhtml

We'll do our best to get them resolved promptly.