New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UI bugs connected to subdatatables #4536
Comments
Thanks for the report! |
Bugs 1 and 3 from the ticket description should be gone now. Please let me know when the demo is updated so that I can test the exact steps mentioned in the description. |
I think this ticket should be done now. As I said, I'd like to test it on the demo before closing it. Please guys, test as much as you can. It is really hard to get this right. Open and close subtables (both tables like the pages report and tables like the search engines report) randomly and see whether you can spot another error. |
Nice changes! Timo we now have the demo running latest git master at http://demo2.piwik.org |
demo2 doesn't have the same data so I can't test the exact steps described above. I could reproduce the issues with data from my local environment and the problems are gone there. So I guess the bugs mentioned above are fixed now. I'd still like to try it on the regular demo but that's not urgent. When do you think it will be updated the next time? |
In next couple days will be updated with the RC we are preparing. Btw I noticed a regression:
|
Is .entityTable the right selector to use? Please review the CSS change and test again. |
I can confirm that all three bugs from the description are now gone on the demo. |
A commit above broke the screenshot UI tests. I have also asked this on [[https://github.com/piwik/piwik/commit/6148bb1532fb88da4d21e8a4c1f2903a715e4c5e#commitcomment-5330187|github]]: Who determines what is expected and how can the expected screenshots be changed? documentation] doesn't help much. Is there more documentation on the subject? |
I have updated these screenshots: [[https://raw.github.com/piwik/piwik-ui-tests/master/expected-ui-screenshots/UIIntegrationTest_customalerts_list_triggered.png|alerts history], [[https://raw.github.com/piwik/piwik-ui-tests/master/expected-ui-screenshots/UIIntegrationTest_customalerts_list.png|alerts]]. The [[http://builds-artifacts.piwik.org/ui-tests.master/1622.1/screenshot-diffs/diffviewer.html|diff]] contains more but they are not related to this ticket. I guess the UI tests will still fail. Regarding the new [[https://github.com/piwik/piwik/blob/master/tests/README.screenshots.md#using-screenshots-tests|documentation]]: Thanks for adding this. The second bullet point (Click on the latest failed build) confused me a little. What is the latest failed build? I clicked on the "build failing" icon in the readme. Is that correct? Maybe the documentation could be clearer. |
I'll go ahead and close the ticket. As I said, the UI was changed slightly. If there are objections to the changes (see screenshots above), reopen the ticket. |
…ubtables are opened or closed, reset the odd/even labels. otherwise, two subsequent odd or even rows are possible.
…th-child. this way, striping works properly on nested data tables (e.g. the search engines report). also, make the css overrides more effective (e.g. add :hover).
…in a subtable. fixes bug 2 from the ticket description.
Great work Timo on the other changes, it looks clean & smooth... beautiful!
Here's how to reproduce some bugs (tested in Safari and Chrome).
Go to http://demo.piwik.org/index.php?module=CoreHome&action=index&idSite=1&period=week&date=2014-01-10#module=Referrers&action=getSearchEnginesAndKeywords&idSite=1&period=week&date=2014-01-10
Bug 1:
(Now, refresh)
Bug 2:
(Now, refresh)
Bug 3:
The text was updated successfully, but these errors were encountered: