Closed Bug 1280366 Opened 9 years ago Closed 5 years ago

Search Bar text undo is broken after its position was changed

Categories

(Firefox :: Search, defect, P3)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1620050
Tracking Status
firefox47 --- affected
firefox48 --- affected
firefox49 --- affected
firefox50 --- affected

People

(Reporter: JuliaC, Unassigned)

Details

(Whiteboard: [fxsearch])

[Affected versions]: - latest Nightly 50.0a1 (2016-06-15) - latest Aurora 49.0a2 (2016-06-15) - 48.0b1 build2 (20160606200529) - 47.0 build3 (20160604131506) [Affected platforms]: - Windows 10 x64 - Ubuntu 14.04 x86 - Mac OS X 10.11 [Steps to reproduce]: 1. Launch Firefox with a new profile 2. Go to Search Bar and perform several random searches 3. Focus the Search Bar and hit Ctrl+z several times - inspect the Search Bar content 4. Go to Search Bar and perform several random searches 5. Go to Hamburger Menu -> Customize and move the Search Bar from its default position 6. Go to Search Bar and perform several random searches 7. Focus the Search Bar and hit Ctrl+z several times - inspect the Search Bar content [Expected result]: - (steps 3 and 7) Search Bar displays the previous inserted sequences, regardless of its current or previous position [Actual result]: - (step 7) Search Bar doesn't display the previous inserted sequences anymore after its earlier position was changed [Regression range]: - This issue is _not a regression_, as it's reproducible all the way back to Fx 29.0. [Additional notes]: - A similar situation is encountered for Location Bar, too.
Priority: -- → P3
Whiteboard: [fxsearch]
Summary: Search Bar doesn't display the previous inserted sequences after its position was changed → Search Bar text undo is broken after its position was changed

The issue here is that input elements don't keep their history when moved around the DOM. Therefore marking as a duplicate of bug 1620050 which has a good description of the issue.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.