Closed Bug 264709 Opened 20 years ago Closed 18 years ago

Location bar has not focus when using openurl(, new-window)

Categories

(Core Graveyard :: X-remote, defect)

x86
Linux
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: FelixWiemannBugs, Assigned: blizzard)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041017 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041017 Firefox/0.10.1

When opening a new window using 'openurl(, new-window)' as a remote command, the
location bar does not have the focus.  This is a little bit annoying for
keyboard users.

Workaround: Use 'openurl(about:blank, new-window)'

Reproducible: Always
Steps to Reproduce:
When do you use the command 'openurl(, new-window)' ? In a website that makes
popups? Not sure I understand the user scenario here.

The description of this bug is not clear. I'm about ready to close it unless I
see that this is really a problem.
Component: Disability Access → Keyboard Navigation
It's needed when opening a new empty window from a script.  Like this:

gnome-moz-remote --remote='openurl(, new-window)'
This should be filed in bugzilla.gnome.org, I think.

Let's check with the OS integration component and see.
Assignee: aaronleventhal → bugs
Component: Keyboard Navigation → OS Integration
QA Contact: bugzilla → firefox.os-integration
Timeless agrees, file this in Gnome's bugzilla.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
No, now he says to check and see if it's a bug in xremote.
Status: RESOLVED → UNCONFIRMED
Component: OS Integration → X-remote
Product: Firefox → Core
Resolution: INVALID → ---
Version: unspecified → 1.0 Branch
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago19 years ago
Resolution: --- → EXPIRED
This bug is still present in 1.0.7.  It is reproducible with:

mozilla-xremote-client 'openurl(, new-window)'  # no focus (wrong)

mozilla-xremote-client 'openurl(about:blank, new-window)'  # focus (right)
Status: RESOLVED → UNCONFIRMED
Resolution: EXPIRED → ---
Probably a change in assignee, and not just in product/component, would have been helpful.
Assignee: bugs → blizzard
QA Contact: os.integration → blizzard
Version: 1.0 Branch → Trunk
This bug is probably obsolete because the behavior changed:

$ firefox -remote 'openurl(, new-window)'
Error: Failed to send command: 500 command not parseable

(Closing and marking as invalid.)
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago18 years ago
Resolution: --- → INVALID
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.