Merge lp://qastaging/~linaro-infrastructure/linaro-android-frontend/rearrange-tabs-changes into lp://qastaging/linaro-android-frontend
Proposed by
Georgy Redkozubov
Status: | Merged |
---|---|
Approved by: | Milo Casagrande |
Approved revision: | 305 |
Merged at revision: | 295 |
Proposed branch: | lp://qastaging/~linaro-infrastructure/linaro-android-frontend/rearrange-tabs-changes |
Merge into: | lp://qastaging/linaro-android-frontend |
Diff against target: |
905 lines (+669/-109) 4 files modified
android_build/frontend/views.py (+6/-0) android_build/templates/index.html (+315/-59) group-fixture.json (+72/-0) static/index.js (+276/-50) |
To merge this branch: | bzr merge lp://qastaging/~linaro-infrastructure/linaro-android-frontend/rearrange-tabs-changes |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Milo Casagrande (community) | Approve | ||
Review via email: mp+141326@code.qastaging.launchpad.net |
Description of the change
This branch rearranges tabs and adds new according to the BP https:/
It uses the same approach and codebase as current http://
New groups were created in LP based on discussion with Vishal. To be able to view appropriate builds user needs to be a member of corresponding group.
All existing builds are accessible under "Engineer Builds" tab (Daily+Release tabs) but in future will contain new engineering builds. "Archive Bulids" tab contains also all builds and in future will contain "old" builds.
To post a comment you must log in.
Hello Georgy!
All in all changes look good.
A couple of things though: /ec2-23- 22-101- 107.compute- 1.amazonaws. com/), and I try to open one of the link at the bottom of the (like the last one), the page scrolls all the way to the top of the table. It happens if I click or right click on a link in that position: more or less after half the length of the table. Firefox version is 17.0.1.
- As said on IRC, with Chrome (23...), I cannot see the tabs, I just see plain search entry boxes, cannot understand if it is not loading the CSS or a problem with the JavaScript. I correctly see everything with Firefox. Might also be related to bug 1085007.
- The second strange behavior I see is with Firefox: if I scroll all the way down on the page (https:/