Add an API to better manage the top-header
Bug #1370366 reported by
David Barth
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Oxide |
Fix Released
|
Medium
|
Chris Coulson | ||
Bug Description
Oxide should probably manage how the top-header is presented and adjusts with the webview.
This bug is meant to document the case for the implementation of this additional API.
| Changed in oxide: | |
| assignee: | nobody → Chris Coulson (chrisccoulson) |
| importance: | Undecided → Medium |
| summary: |
- Add an API to manage the top-header better + Add an API to better manage the top-header |
| tags: | added: touch-2014-09-25 touch-2014-10-02 usability |
Revision history for this message
| Chris Coulson (chrisccoulson) wrote | #1 |
| Changed in oxide: | |
| status: | New → Triaged |
| milestone: | none → branch-1.4 |
| tags: | removed: touch-2014-09-25 |
Revision history for this message
| David Barth (dbarth) wrote | #2 |
| tags: |
added: ota-1 removed: touch-2014-10-02 |
| Changed in oxide: | |
| milestone: | branch-1.4 → branch-1.5 |
| status: | Triaged → In Progress |
| Changed in oxide: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
I've milestoned this tentatively to the 1.4 branch for now, based on the assumption that we have a workaround for the current issues with the top header that is good enough for now