115118 - RFE: dynamically expanding/contracting URL bar for low res users

Status: RESOLVED EXPIRED

(SeaMonkey :: Location Bar, enhancement)

Description

[Aaron Kaluszka]

Here's an alternative to bug 49543.
How about having the address bar expand onmouseover/onfocus and contract 
onmouseout/onblur (Enter key hit).
This could be triggered only when the address bar is below a threshold width.
The bar would either float above the buttons or right below the buttons.
I would recommend this as a customization option.

Comment 1

[sairuh (rarely reading bugmail)]

urlbar

Comment 2

[Joe Hewitt (gone)]

sounds like accessibility to me, aaron what do you think?

Comment 3

[Aaron Leventhal]

Nah, if we're going to implement our own auto magnification, we should do it all
over the product, for every XUL widget, etc. That's a ton of work that no one is
thinking of doing now.

In the mean time, users will be able to try Mozilla with Zoomtext or Lunar Plus.

Comment 4

[Aaron Kaluszka]

This isn't magnification.. this is expansion: urlbar width changes only.
REOPENing based on reason for WONTFIX.

Comment 5

[Aaron Leventhal]

Okay, sorry.

In that case this is really a general usability issue, not an accessibility issue.

Over to UI design for comment.

Comment 6

[Felix Miata]

Incorporating comment: http://bugzilla.mozilla.org/show_bug.cgi?id=154772#c6

Comment 7

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 8

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420