Firefox AVIARY only, `Resolving host xyz.foo.bar...' should be `Looking up xyz.foo.bar...'

RESOLVED FIXED

Status

()

--
trivial
RESOLVED FIXED
15 years ago
15 years ago

People

(Reporter: tmeader, Assigned: tmeader)

Tracking

({fixed-aviary1.0})

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040614 Firefox/0.8.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040614 Firefox/0.8.0+

This is the Firefox analog to bug #105892, to summarize (from the other bug):

------------------

To reproduce:
1.  Go to a Web site on a server you haven't been to in a while (such that it's
    not in your DNS cache).
2.  Look at the status bar.

What you see:
*   `Resolving host nameOfServer...'

What you should see:
*   `Looking for nameOfServer...'

Q & A from bug 97028 (from which this bug is spun off):

Why not `Resolving host'?
    Because only a miniscule proportion of the population knows what a `host'
    is, let alone what it means to `resolve' it. `Looking for' is much more
    understandable, while still being correct.
Why not `Looking up' instead of `Looking for'?
    For the same reason. Most people are unaware that IP numbers are stored in
    an index, so `Looking for' makes more sense while still being correct.
Eventually, we need to design several UI behaviors, tailored to various users.
    Uh, this is a Web browser's status bar, it's not a wedding dress. Even in
    the highly unlikely event that we wanted the status text to be themable
    independently from the rest of the browser, that's waaaaay outside the
    scope of this bug.
I know, let's redesign the status bar text for every networking state before we 
change anything!
    Uh, no. Firstly, it would take a long time to spec, and even longer to
    implement. Secondly, no matter what the status text for the other states
    ends up being, `Looking for {serverName}...' will be the status text for
    the initial domain resolution. (I will do a spec, once someone sends me a
    list of all those networking states.) And thirdly, `Resolving host' is the
    most obvious status text currently (especially on a high-speed connection),
    so its disturbing obfuscation should be fixed promptly.
Won't changing this string confuse Networking QA people?
    I think they're smart enough not to be confused by this, really. And
    anyway, Networking QA people make up a positively microscopic proportion of
    users of Mozilla distributions.

------------------

I'll just add that this is the same wording ("Looking up") that IE uses, which
would be much more familiar.

Reproducible: Always
Steps to Reproduce:
(Assignee)

Comment 1

15 years ago
Make that "Looking for"... hehe ;)
Whiteboard: AVIARY only (trunk should pickup fix from related bug)
(Assignee)

Comment 2

15 years ago
Created attachment 150733 [details] [diff] [review]
Patch from the Mozilla Suite side, same networking backend though

Here's the patch. Like I said, the trunk builds should be fine, but if anyone
wants this in 1.0, this'll have to be patched here.

Thanks.
(Assignee)

Comment 3

15 years ago
Comment on attachment 150733 [details] [diff] [review]
Patch from the Mozilla Suite side, same networking backend though

Setting to blake for review.
Attachment #150733 - Flags: review?(firefox)

Comment 4

15 years ago
Tim, you meant "Looking up" rather than "looking for", right?
Summary: Firefox AVIARY only, `Resolving host xyz.foo.bar...' should be `Looking for xyz.foo.bar...' → Firefox AVIARY only, `Resolving host xyz.foo.bar...' should be `Looking up xyz.foo.bar...'
(Assignee)

Comment 5

15 years ago
Thank you, yes, the final patch did end up with "Looking up", forgot about that.

So to anyone looking at the patch... yes, It's "Looking up xyz.foo.bar..." not
Looking for.

Updated

15 years ago
Attachment #150733 - Flags: review?(firefox) → review+

Comment 6

15 years ago
Not sure this needed a separate bug, but now you've done it, confirming this.

I see that blake has reviewed the patch, so it just needs checking in.
Assignee: firefox → tmeader
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: AVIARY only (trunk should pickup fix from related bug) → needed-aviary1.0
checked in on branch
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Keywords: fixed-aviary1.0
Resolution: --- → FIXED
Whiteboard: needed-aviary1.0
You need to log in before you can comment on or make changes to this bug.