From 238e45482cf928d89093043948a1c37a56ae961a Mon Sep 17 00:00:00 2001
From: Conrad Irwin <conrad.irwin@gmail.com>
Date: Wed, 18 Mar 2009 00:45:47 +0000
Subject: [PATCH] Fix bug #189, <tab><cr> now uses first completion

On discussion with maxauthority this is probably the best way of doing
things for now.
---
 common/content/ui.js | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/common/content/ui.js b/common/content/ui.js
index d01f2a2c..a23e5de7 100644
--- a/common/content/ui.js
+++ b/common/content/ui.js
@@ -1298,8 +1298,15 @@ function CommandLine() //{{{
                 // user pressed ENTER to carry out a command
                 // user pressing ESCAPE is handled in the global onEscape
                 //   FIXME: <Esc> should trigger "cancel" event
+                //   FIXME: This should not be waiting, some kind of callback mechanism on completion would be better.
                 if (events.isAcceptKey(key))
                 {
+                    while (completions.context.incomplete)
+                    {
+                        liberator.threadYield(true);
+                        command = this.command;
+                    }
+
                     let mode = currentExtendedMode; // save it here, as modes.pop() resets it
                     keepCommand = true;
                     currentExtendedMode = null; // Don't let modes.pop trigger "cancel"