Blocks #20

acceptance criteria: an architecture diagram that clearly defines functional and UI components

acceptance criteria:
able to see the page with static entries to top sites. (UI only)

acceptance criteria:

1. able to display the history panel, and scroll up/down to navigate. Historical links are sorted by time of visit.
2. able to open link from history panel
3. able to clear history one by one
4. able to clear history all at once

Acceptance criteria:

1. Including the living document having data collection fields addressed.

acceptance criteria:

1. (P1) support external storage for downloads
2. (P2) support external storage for cache

testing depending on download function (#34)

acceptance criteria:

1. able to see the three floating buttons on top of the web page area.
2. Buttons automatically hide as user scrolls up and down.
3. Search button triggers the search panel; menu button triggers the menu panel; home button triggers to home page.

Follow up Bug for #18

acceptance criteria:
display a list of site info including: security, permission. Note that permission is that configurable here.

STR:

1. Click search FAB
2. Press back to hide the keyboard
3. repeat step 1-2

Expected result:
UrlFragment is added only once.

Actual result:
UrlFragment is added for multiple times, to get back to Top site several back press is needed.

ac:
leverage the tracking blocker from Focus

STR:

1. Login to any page such as Facebook, then swipe Zerda away from task bar.
2. Open Zerda again.

Expected result:
Login session is still valid.

Actual result:
Login session is (mostly) invalid.

--

Cookies are stored in the memory and is stored into the persistent store every five minutes. (Source: https://developer.android.com/reference/android/webkit/CookieSyncManager.html) (Note that the class is deprecated so we may want to verify if the condition still holds. My current observation aligns to this claim.)

So we might want to do something like
public void onPageFinished(WebView view, final String url) {
...
CookieManager.getInstance().flush();
}
to flush cookie after each request. like proposed here, but using the not-deprecated api: https://stackoverflow.com/a/8390280/3591480

We may want to make sure this does not have a performance regression before committing this. We may find a way to flush only the request is cookie related too.

This is needed because Focus does not position itself as a works-for-everything browser. We probably don't need this. Remove it just to make structure cleaner! We can easily roll back if we actually need this (or at least see what needs to be add back from the commit message if the structure is already too dramastically changed).

UI piece is in #34

STR:

1. Open bottom sheet
2. Click preference
3. hit back
4. Crash

acceptance criteria:
able to bring up the menu panel with a list of icons (non-functioning)

Depends on: #62, #67, #68, #69, #70

#2 skip the testing. Add them back with Adjust release token.

function piece is covered in #43

Depends on: #12, #43, #75

Blocks: #20

This is needed because Focus is a privacy browser. We probably don't need this. Remove it just to make structure cleaner! We can easily roll back if we actually need this (or at least see what needs to be add back from the commit message if the structure is already too dramastically changed).

acceptance criteria:

1. string table includes the error messages

We have some privacy cleanups that we don't need in out design. Let's back them out so we can have consistent sessions.

blocking: #8

acceptance criteria:
Functions including cookies, URL bar, navigation, media playback, context menu (system UI for text;share/copy for hyperlinks ;share/save for images; not handling video)

dependent: #8, #23

acceptance criteria:

1. search suggestion included; no search history

Site info is removed, remove site info action when visual is ready.

Blocks: #20

P2

UI piece is in #34

acceptance criteria:

1. able to handle location

acceptance criteria:
able to bring up the search panel with a list of icons (no real search functioning).
Works as a URL bar for now.

acceptance criteria:
when website requests, prompt the dialog to end user for accepting or denying (not functioning).

acceptance criteria:

1. the top sites will be based on users' browsing frecency (whenever available) instead of default ones