Closed
Bug 98764
Opened 24 years ago
Closed 24 years ago
-remote 'openURL("xyz")' while no browser window up causes an unchromed browser window to display
Categories
(Core Graveyard :: X-remote, defect)
Tracking
(Not tracked)
CLOSED
FIXED
People
(Reporter: leary, Assigned: blizzard)
References
Details
(Whiteboard: [xremote])
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3+) Gecko/20010907
BuildID: 2001090708
launching:
/path/to/mozilla/mozilla -remote "openURL($url,new-window)"
via a script (where $url is one) only resets the open browser to a fresh, blank
browser, wiping out the page you were looking at, disabling the back button, and
not launching the URL.
Reproducible: Always
Steps to Reproduce:
I'm using url_handler.sh, but this should repro just by using commandline
similar to above.
Actual Results: see description
Expected Results: old window is OK
new window has URL
Comment 1•24 years ago
|
||
->blizzard
Reporter: X-remote is being completely re-written. look at bug 98603 for
details. I haven't seen it broken as badly as you describe. The worst I've
seen it get is the way i described in bug 94289. Is that what you are talking
about?
Assignee: asa → blizzard
URL: http://n/a
Severity: critical → normal
Component: Browser-General → XP Miscellany
Reporter | ||
Comment 2•24 years ago
|
||
bug 94289 is probably related, but is not what I'm seeing. What I see looks
like a fresh, normal browser instance with a blank document area. It's a
working browser, but if I'd had any data in a form, it would be gone. That's
data loss == critical.
Depends on: 98603
QA Contact: doronr → sairuh
Summary: mozilla -remote "openURL($url,new-window)" badly broken → -remote 'openURL("xyz")' while no browser window up causes an unchromed browser window to display
Assignee | ||
Updated•24 years ago
|
Whiteboard: [xremote]
Assignee | ||
Comment 3•24 years ago
|
||
Fixed.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•