Next generation web browser.

The LuneOS web browser, which will be the default web browser for the WebOS Ports LuneOS project.

The LuneOS web browser is built completely in QML on top of Qt WebKit and enables the user to browse the web.

The LuneOS web browser uses luneos-components, make sure to have these available, you can get them at http://github.com/webos-ports/luneos-components

Features:

1. Loads pages.
2. Creates browser history.
3. Private browsing feature via Tweaks (doesn't create history).
4. Ability to add bookmarks.
5. Can go back and forward.
6. URL prediction based on browser history & bookmarks
7. UI similar to legacy 3.0.x browser.
8. Support for both tablet (landscape) and phone (portrait) layout.
9. Custom UA strings in order to improve compatibility with websites.
10. Show/hide vkb using button which can be enabled in Tweaks.
11. Launching via Just Type :)
12. Has a settings page
13. Multiple tabs

Known bugs:

1. After closing bookmarks/history/downloads panel, tapping on URL bar doesn't bring up Virtual Keyboard.
2. URL suggestions only looks in browser history, not in bookmarks yet.
3. Bookmarks panel is empty on loading.
4. Search doesn't always work yet.
5. Various layout and rendering issues.
6. Page gets added to browser history, even when not loaded (for example when there's no network connectivity).
7. Progress bar doesn't always behave properly.
8. Share dialog not working yet.
9. Cannot select cursor location in URL bar
10. Dropdown for search engine in Settings not working yet
11. Tapping on App Menu when visible doesn't hide it.
12. Authentication dialog doesn't look good on N4
13. Error message is not correct when no network connection is available.
14. Selection markers are not displayed at the correct location for long URL's.
15. Long URL's running behind stop/reload icon on address bar
16. Text in addressbar needs some spacing
17. Opening URL's 1 and 2 via luna-send will open URL 1 twice.

To do:

1. Add FocusScope to addressBar to see if that solves the VKB focus issue.
2. Fix the creation of browsing history for only properly loaded pages.
3. Add bookmarks in URL suggestions as well.
4. Create settings page to replicate settings from legacy.
5. Add additional browser Tweaks (look at legacy to see what's interesting).
6. Add launch parameters + handling
7. Add icons for bookmarks (investigate legacy's handling).
8. Add "search in page" See http://developer.blackberry.com/native/documentation/cascades/ui/webview/loadingwebcontent.html
9. Add select, copy & paste where possibleCompleted for address bar, available in nightlies
10. Fix share dialogAvailable in nightlies
11. Flexible User Agent implementation, see Ubuntu approach.
12. Add possibility to delete individual bookmarks/history/download items (swipable or otherwise).
13. Investigate search suggestions to see if those are possible from QML with our luna calls.
14. Add possibility to edit bookmarks.
15. Add authentication dialog.
16. Add password manager.
17. Add cookies support.
18. Look into https everywhere (probably need to use sqlite DB created by https://github.com/EFForg/https-everywhere/tree/master/utils because to use 16000 XML files is a no-go).
19. Confirmation dialog for Clearing Downloads.
20. Further make the preferences actually do something in the app.
21. Make separate layouts for phones (portrait) and tablets (landscape) due to limited real estate in portrait mode, we want to reduce the number of buttons and find a solution for thos.
22. Fix layout of address bar on TP. Anchoring seems off a bit sometimes.
23. Add scroll bar and style it webOS-y.
24. Clean up code and make separate QML files for components.
25. Add additional share options, based on check to see if certain app is installed?Shelved for now, pending a "Sharing Manager" implementation
26. Add divider for History items (as per legacy)
27. Add "Input"->"File" support
28. Add further experimental support (minimal fontsize, viewport, device pixel ratio etc)

If you want to contribute you can just start with cloning the repository and make your contributions. We're using a pull-request based development and utilizing github for the management of those. All developers must provide their contributions as pull-request and github and at least one of the core developers needs to approve the pull-request before it can be merged.

Please refer to http://www.webos-ports.org/wiki/Communications for information about how to contact the developers of this project.