Closed
Bug 304477
Opened 20 years ago
Closed 20 years ago
Release notes should mention that -remote is broken/deprecated
Categories
(www.mozilla.org :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: akkzilla, Assigned: rebron)
Details
(Keywords: relnote)
Someone on #developers mentioned Asa's name in connection with release notes.
Sorry, Asa, if you're not the right assignee.
Bug 280725, implementing auto-remote, broke -remote: it no longer handles urls
containing commas, as described in bug 298960. I'm assuming -remote is
deprecated if that's not going to be fixed, though that's a policy decision
someone should probably make.
This should be releasenoted (if it's not going to be fixed) since a lot of
people use -remote and will wonder why sometimes it no longer works reliably.
Suggested placement: under Known Issues. I'm not sure if -remote should be under
Linux/Unix or All Systems -- did it work everywhere? Probably it's mostly
linux/unix users who care about it.
Suggested wording (or at least a start):
firefox -remote (mozilla-xremote-client) no longer works on urls containing
commas, and is deprecated. Use firefox /url/ instead: it will automatically use
any currently running firefox to open the url according to the tab preferences.
firefox -new-window /url/ will open the url in a new window. There is no
-new-tab option as yet.
Updated•20 years ago
|
Component: Help Documentation → Product Site
QA Contact: help.documentation → product.site
Reporter | ||
Comment 1•20 years ago
|
||
-new-tab works now! Please change those last two sentences to:
firefox -new-window /url/ will open the url in a new window; firefox -new-tab
/url/ will open the url in a new tab.
Setting the flag for b4 hoping this will get incorporated into the release notes.
Flags: blocking1.8b4?
Updated•20 years ago
|
Flags: blocking1.8b5?
Flags: blocking1.8b4?
Flags: blocking1.8b4-
Comment 2•20 years ago
|
||
Rafael owns the release notes. By itself this isn't a stop ship bug since it
isn't related to the code at all. But we should maek sure our release notes are
correct.
Rafael, maybe you could update the beta 1 release notes and then we can mark
this bug as fixed since changes there should get picked up for the final release
notes.
Assignee: asa → rebron
Flags: blocking1.8b5? → blocking1.8b5+
Target Milestone: --- → Firefox1.5
Updated•20 years ago
|
Flags: blocking1.8b5+ → blocking1.8b5-
Reporter | ||
Comment 3•20 years ago
|
||
Rafael: ping? Any chance of getting the release notes updated before the final release?
Comment 5•20 years ago
|
||
This is fixed for 1.5 release. Please reopen if you disagree.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Comment 6•19 years ago
|
||
--> Websites :: www.mozilla.com so timeless can close out Firefox :: Product Site.
Component: Product Site → www.mozilla.com
Flags: blocking1.8b5-
Flags: blocking1.8b4-
Product: Firefox → Websites
Target Milestone: Firefox1.5 → ---
Version: Trunk → unspecified
Updated•19 years ago
|
QA Contact: product.site → www-mozilla-com
Updated•13 years ago
|
Component: www.mozilla.org/firefox → www.mozilla.org
Updated•13 years ago
|
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in
before you can comment on or make changes to this bug.
Description
•