The open-dialogboxes doesn't support ~user as a valid input.
~user should switch to "user"'s homedir.
~user is a bash-ism, possibly other shells also implement it.
'~' in the filepicker DOES go to the user's home directory.
'~jg' complains that /home/jg/jg doesn't exist, which is correct.
Don't see why this is a UI bug. More like filepicker, re-assigning to bryner and
setting severity to enhancement, also updating summary.
Really re-assign to bryner.
even though ~subdir doesn't work, ~/subdir does work for me.
The handling of ~someone is not surposed to enter a subdir in YOUR homedir, but
enter "someone"'s homedir. ~/dir correctly switches to a subdir in YOUR homedir.
oops, duh! thx, i forgot about that...
Is this only covering the save dialog and such, or also file:// in the address bar.
It's very annoying to have to type in my full home directory path to load
~/x.html, when I'm doing a simple test case.
That is a completly different bug ;)
File it! Please ;)
I know some of these conventions are shell conventions, so is there a way for
the UNIX verions to ask the OS to do conversions (or maybe read the user shell
and do the conversion?).
Futuring until someone suggests a decent way of doing this that works across all
unices and does not require parsing /etc/passwd entries or something ridiculous
No plans to work on this any time in the foreseeable future, so to default owner.
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
Works fine now (seamonkey uses GTK file dialog now).