Bug 1135954

Summary: [Usability]Add the confirm dialog box when reload page
Product: [Community] Bugzilla Reporter: Rony Gong 🔥 <qgong>
Component: Bugzilla GeneralAssignee: PnT DevOps Devs <hss-ied-bugs>
Status: CLOSED WONTFIX QA Contact: tools-bugs <tools-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.4CC: mtahir
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: 2016-09-01 08:39:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Confirm dialog box none

Description Rony Gong 🔥 2014-09-01 10:03:40 UTC
Created attachment 933289 [details]
Confirm dialog box

Description of problem:
[Usability]Add the confirm dialog box when reloading page
It isn't easy for user to recover back the default field value by just refeshing current page, it happens in many pages like:

Simple search
Advanced search
google search
bug datail/entry page

Version-Release number of selected component (if applicable):
Always

How reproducible:
4.4.5025

Steps to Reproduce:
1.Open a bug detail page, do some update to the bug, like edit summary, assignee, add comment, don't click save button.
2.Then reload current page by click the browser's reload button

Actual results:
The field value of this page keep same as before reload page.

Expected results:
prompt a confirm dialog(like in attachment):
1. Leave on Page:  reload page and set all fields value to default
2. Stay on page: don't reload page.

Additional info:
we suggest all bugzilla pages support this feature except for the pages that can't do input action.

Comment 1 Jason McDonald 2014-09-02 01:17:54 UTC
For pages inherited from upstream, the change should be made upstream.

Comment 2 Jeff Fearn 🐞 2015-07-21 07:25:07 UTC
I would *really* hate this, so it should be a user setting, which makes it more effort than it's worth IMO.

Comment 3 Jeff Fearn 🐞 2016-09-01 07:47:09 UTC
This is browser specific behavior and IMO we should not be addressing it. Some browsers "help" users by not changing back to the original values when the user reloads a page, on those browsers you need to do a "hard" reload.

e.g. in Firefox holding down shift and clicking reload does a hard reload and the original values are loaded in to the form fields.

It's not a bug in Bugzilla, it's a choice by browser vendors on how their browser behaves.

Comment 4 Rony Gong 🔥 2016-09-01 08:08:22 UTC
(In reply to Jeff Fearn from comment #3)
> This is browser specific behavior and IMO we should not be addressing it.
> Some browsers "help" users by not changing back to the original values when
> the user reloads a page, on those browsers you need to do a "hard" reload.
> 
> e.g. in Firefox holding down shift and clicking reload does a hard reload
> and the original values are loaded in to the form fields.
> 
> It's not a bug in Bugzilla, it's a choice by browser vendors on how their
> browser behaves.

This isn't a bug for bugzilla, it is a feature request and with low priority and low severity.

Comment 5 Jeff Fearn 🐞 2016-09-01 08:39:51 UTC
Cool. I don't want to spend resources trying to bypass deliberate decisions by browser vendors.