4 ms·
I know that this is just a demo, but it featured a very laggy map on Android, an ugly menu bar and scrollbars on Windows, and perhaps more importantly, UIs on d
by comex 13y ago
I know that this is just a demo, but it featured a very laggy map on Android, an ugly menu bar and scrollbars on Windows, and perhaps more importantly, UIs on desktop that looked like nothing but scaled up phone UIs. To the extent that this is representative of the real thing - which, again, could be 'not very much' in the future - useful in a pinch, but not something I'd want to use on a daily basis. (I don't think there is even currently an API to populate the menu bar...)
- fzzzy 13y agoYou are correct that there is currently not an API to populate the menu bar. Regarding app scaling, It's up to each app developer to do the required work to have a responsive design, using existing web techniques.
- deno 13y agoFirefox already supports native context menus[1][2][3] so it shouldn’t be that difficult to extend this to top level menu bar. Of course they should fix them first: 1) don’t show the browser options otherwise it’s completely useless 2) (optionally) if you want the browser options/extensions etc. use something like the clipboard/dnd api to set the application specific mime type on right click and connect that to web intents. [1] http://davidwalsh.name/html5-context-menu http://davidwalsh.name/html5-context-menu [2] http://www.whatwg.org/specs/web-apps/current-work/multipage/interactive-elements.html#context-menus http://www.whatwg.org/specs/web-apps/current-work/multipage/... [3] http://caniuse.com/#search=menu http://caniuse.com/#search=menu
- wfwalker 13y agoI used my own app in the demo video; as you point out, it is hardly a paragon of responsive design! I think you'll find that properly written apps will behave a lot more as you hope/expect