-
Notifications
You must be signed in to change notification settings - Fork 37
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
Improve monitor section in the last blog post #217
Conversation
Deploy preview for openbuildservice ready! Built with commit 76196b3 |
On Dienstag, 19. Februar 2019, 10:43:44 CET Dany Marcoux wrote:
dmarcoux commented on this pull request.
> @@ -26,12 +26,14 @@ The comments from a superseded request are now under a
> tab, next to the request'
## Improvements for the Project Monitor Page
-We improved the usability of the filters.
-They previously closed whenever checking/unchecking one of their
checkboxes. -This is fixed.
-
-The datatable had rendering errors when used in combination with the
`table-sm` _Boostrap_ class due to a bug in the JavaScript library we use.
-As good open-source users, we reported it
[upstream](mkhairi/jquery-datatables#17). +In the
monitor page, we fixed a regression in performance that made that for some
projects it took too long to load.
A bit too many `that` IMHO.
You should not announce that monitor atm IMHO, it is really not usable since
it became bootstrap (I have the anonymous browser window always open to use it
since last year)
openSUSE/open-build-service#7007
…--
Adrian Schroeter
SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
email: [email protected]
|
We are just letting users know we worked on it in the last weeks and we are continuing working on it. It is not a last version. The issues you mention are not related with the ones that were fixed (at least not all of them). |
Add some more details and mention the help we got from upstream.
Add some more details and mention the help we got from upstream.
Sorry I didn't add this before. I had RAM problems in my computer when trying to get the performance numbers. We decided not to mention the numbers, as this page is faster than before but still there is place for improvement and it is slower than the old one (because of the improvement in usability - Nice table with first column fixed instead of a broken table)