4 ms·

Just opened up the MacOS build. It is pretty impressive! But the autocomplete is just awful. Typing in "http://localhost:3000" http://localhost:3000" at normal

Just opened up the MacOS build. It is pretty impressive! But the autocomplete is just awful. Typing in "http://localhost:3000" http://localhost:3000" at normal speed produced "http:///localhost:300000" http:///localhost:300000". Especially while it's in such a primitive developer-oriented state it would be much more useful to disable that silly autocomplete. Edit: Additionally, it doesn't yet support native keybindings like Command left-right or Alt left-right.

publicfig 10y ago
I doubt that there's going to be much effort into improving the HTML based browser that they're using as a shell to the engine outside of making sure you can go to a specific URL. Things like hotkeys and autocomplete are nice, but not really necessary for developing on Servo. I could be wrong on that though
- eatonphil 10y ago
  Well that's exactly the point (concerning autocomplete anyway). It would be nice to have if it worked... but right now it just gets in the way. And it's not even that relevant to the underlying engine, right?
- metajack 10y ago
  The browser.html team works on the frontend, so they are very much interested in improving this. You're right that Servo devs themselves often use an even more stripped down test harness that you supply URLs to on the commandline, but that may change now that browser.html has gotten quite nice :)
metajack 10y ago
We found some weird edge cases with autocomplete last night, but couldn't reproduce them well. If you have some time and can reproduce it, we'd love a bug report so we can try and figure it out.
- eatonphil 10y ago
  I think the issue would much be better solved by not automatically completing and instead showing a grayed out suggestion that can be selected by hitting right arrow. Anyway, what it is doing right now is seeing "http:/" and thinking <Ok, I can just add /sitethatobviouslyhasnorelevanceyet.com and everything will be fine!>. But while it was thinking, I already started typing the second "/" and didn't notice so I got in "lo" before I saw the result. At that point what's in the field is "http:///sitethatobviouslyhasnorelevanceyet.comlo" http:///sitethatobviouslyhasnorelevanceyet.comlo". The issues here are serious enough but it's not entirely surprising you can't reproduce them well.
igozalishvili 10y ago
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 https://github.com/browserhtml/browserhtml/issues/1157 Feel flee to report more browser.html issues here: https://github.com/browserhtml/browserhtml https://github.com/browserhtml/browserhtml We'll do our best to get them resolved promptly.

publicfig 10y ago

I doubt that there's going to be much effort into improving the HTML based browser that they're using as a shell to the engine outside of making sure you can go to a specific URL. Things like hotkeys and autocomplete are nice, but not really necessary for developing on Servo. I could be wrong on that though

eatonphil 10y ago
Well that's exactly the point (concerning autocomplete anyway). It would be nice to have if it worked... but right now it just gets in the way. And it's not even that relevant to the underlying engine, right?
metajack 10y ago
The browser.html team works on the frontend, so they are very much interested in improving this. You're right that Servo devs themselves often use an even more stripped down test harness that you supply URLs to on the commandline, but that may change now that browser.html has gotten quite nice :)

metajack 10y ago

We found some weird edge cases with autocomplete last night, but couldn't reproduce them well. If you have some time and can reproduce it, we'd love a bug report so we can try and figure it out.

eatonphil 10y ago
I think the issue would much be better solved by not automatically completing and instead showing a grayed out suggestion that can be selected by hitting right arrow. Anyway, what it is doing right now is seeing "http:/" and thinking <Ok, I can just add /sitethatobviouslyhasnorelevanceyet.com and everything will be fine!>. But while it was thinking, I already started typing the second "/" and didn't notice so I got in "lo" before I saw the result. At that point what's in the field is "http:///sitethatobviouslyhasnorelevanceyet.comlo" http:///sitethatobviouslyhasnorelevanceyet.comlo". The issues here are serious enough but it's not entirely surprising you can't reproduce them well.

igozalishvili 10y ago

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 https://github.com/browserhtml/browserhtml/issues/1157 Feel flee to report more browser.html issues here: https://github.com/browserhtml/browserhtml https://github.com/browserhtml/browserhtml We'll do our best to get them resolved promptly.