| Summary: | Web UI Status Not Updating Properly | ||
|---|---|---|---|
| Product: | [Retired] Beaker | Reporter: | Sean Waite <swaite> |
| Component: | web UI | Assignee: | Raymond Mancy <rmancy> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 0.8 | CC: | bpeck, dcallagh, ebaak, jburke, jnicolet, mcsontos, rmancy, stl |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-08-09 08:06:38 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Sean Waite
2012-02-14 16:23:11 UTC
this is because we are using a form to display the status as well as let you change it. Are you hitting reload? If you load the page new it will "correct" itself. Looks like we should add autocomplete=off to the form element http://stackoverflow.com/questions/4862606/when-using-html-select-tag-changed-selected-value-not-displayed-in-firefox I'm entering "F5, " or hitting the reload button, both of which will do a reload. It's possible that a Ctrl-F5, which clears the cache and forces a reload, will fix it, but otherwise a simple reload does not. Just confirmed. Reload will not clear it, but Cache Clear + Reload (Ctrl + F5 in Firefox will) This is a browser feature, I don't think we should be trying to work around it. Especially not by wholesale disabling autocomplete, which is generally quite useful. (In reply to comment #4) > This is a browser feature, I don't think we should be trying to work around it. > Especially not by wholesale disabling autocomplete, which is generally quite > useful. Maybe its time we separate the edit from the display then? Currently we display everything in a form and allow users with the correct permissions to change it. But most of the time you aren't interested in changing it, you're just looking for the current status/values. We could simply have an edit link to make any changes to the system? (In reply to comment #5) +1 to this. I think it makes sense to display system info in an ordinary table, and have a separate form for editing. moving to 0.9.2 so we can implement like comment #5 While we're here and commited to seperating the view from the editing does anyone have any ideas about how we might like to change the view of the system details? Off the top of my head: * Date created * Last checkin * Serial number * Last modification * Notify CC. Do people want to be able to see these? Why not have a simple toggle 'button' that can show these details if the user wants, otherwise it keeps them hidden. I'm going to guess the most common complaint will be the one extra click if you want to see all the details, and that the layout between the view and the edit would now be different. For the time being I'm just going to hack it up to use the same display that we currently do. One day when someone who knows more about UX that I comes along and has some input, we should look at fixing it properly A minor issue identified during testing: the Condition Report field is no longer being hidden for working (i.e. Automated or Manual) systems on the system page.
This js in system_form.kid will need slight tweaking:
if ($('#form_status :selected').text() == 'Manual' || $('#form_status :selected').text() == 'Automated') {
(In reply to comment #12) Apart from that, this works really well and is a huge improvement to the system page IMHO. (In reply to comment #12) > A minor issue identified during testing: the Condition Report field is no > longer being hidden for working (i.e. Automated or Manual) systems on the > system page. > Dan, I believe we do not want it hidden for Automated or Manual. For example the system can be Automated and loaned to a person. We wanted to use the condition field to say who/why (ticket number) the system was loaned. Best, Jeff Hi Jeff, This 'Condition Report' was designed around the Broken status. In fact it is cleared if you move the system from Broken -> Automated/Manual. Ray, I understand. I only mention it because I have an outstanding issue that I brought up at the stakeholders meeting a few weeks ago. This BZ seemed relevante to that issue. Sorry to add confusion. [] Bug 733347 - RFE: Add ability to update the "Condition Report" when a system is loaned in Beaker. * This would go a long way in helping us track why systems are loaned out. Best, Jeff Beaker 0.9.2 has been released. |