Bug 1376833 - Hitting back resets selects populated by ajax
Summary: Hitting back resets selects populated by ajax
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: User Interface
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
low vote
Target Milestone: 5.0
Assignee: Jeff Fearn 🐞
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-16 14:20 UTC by Viliam Križan
Modified: 2018-12-09 06:29 UTC (History)
3 users (show)

Fixed In Version: 5.0.3-rh8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-11 01:04:20 UTC


Attachments (Terms of Use)

Description Viliam Križan 2016-09-16 14:20:12 UTC
Description of problem:
If I fill up all required fields, but for example fill a bad CC email (e.g. `thisemail.exist`) then I get to the Match Failed page. The page advises to go back to correct my error. However, if I go back, I see that the component field, that was pre-filled before, is *empty*.

I haven't tried if the subcomponent is going to be emptied too, but I suspect it would. Since it looks like a same widget.


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

How reproducible:
(see description)

Steps to Reproduce:
1. Fill up bug report with wrong CC email address
2. Submit
3. Go back

Actual results:
`component` field is emptied

Expected results:
`component` field is pre-filled from browser's cache (as it was before submitting).

Comment 1 Rony Gong 🔥 2016-10-09 07:36:02 UTC
Tested on QA environment(5.0.3-rh8)
Result: Pass
Steps
1. Go to enter_bug page of any product
2. select a component
3. input a non-exist user into cc, input string into summary, submit this bug
==>Jump to new page of the cc doesn't match anything
4. click the return back button of browser
==>This origin component still show as selected


Note You need to log in before you can comment on or make changes to this bug.