Closed
Bug 193416
Opened 22 years ago
Closed 22 years ago
mailnews start page gets cleared when I open the pref window
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla1.4alpha
People
(Reporter: sspitzer, Assigned: neil)
Details
(Keywords: dataloss, Whiteboard: [fixed1.3.1][adt1])
Attachments
(3 files)
861 bytes,
patch
|
Details | Diff | Splinter Review | |
695 bytes,
patch
|
Details | Diff | Splinter Review | |
2.52 KB,
patch
|
janv
:
review+
jag+mozilla
:
superreview+
|
Details | Diff | Splinter Review |
mailnews start page gets erased
when I open the pref window, my mailnews start page gets cleared out.
is anyone else seeing this?
note, the way browser does the start page pref (in pref-navigator.js and
pref-navigator.xul) is different that how we're doing it.
Reporter | ||
Comment 1•22 years ago
|
||
here's the xul:
<textbox id="mailnewsStartPageUrl" flex="1" preftype="localizedstring"
type="autocomplete" prefstring="mailnews.start_page.url"
searchSessions="history" timeout="50" maxrows="6" class="uri-element"/>
if I remove all the autocomplete related attributes, it works:
type="autocomplete" searchSessions="history" timeout="50" maxrows="6"
class="uri-element"
I'm not sure when this broke. I'd much rather figure out why this stopped
working, and see if there is a good fix, rather than making pref-mailnews.js and
pref-mailnews.xul to be more like pref-navigator, which appears to handle this
pref by hand, instead of using the attributes that nsPrefWindow.js is supposed
to support.
before I dig into this, is anyone else seeing it?
Reporter | ||
Comment 2•22 years ago
|
||
I queried, and didn't see other dups of this.
but I can't imagine I'm the only one.
Keywords: dataloss
Summary: mailnews start page gets erased → mailnews start page gets cleared when I open the pref window
Assignee | ||
Comment 3•22 years ago
|
||
Doh, this is probably another regression of the URL bar hack :-/
Assignee | ||
Comment 4•22 years ago
|
||
Assignee | ||
Updated•22 years ago
|
Attachment #114657 -
Flags: superreview?(sspitzer)
Attachment #114657 -
Flags: review?(jaggernaut)
Reporter | ||
Comment 5•22 years ago
|
||
Comment on attachment 114657 [details] [diff] [review]
Proposed patch
do we have a tracker bug for all the band-aid fixes for #90337? (if so, we
should add this to it.)
Reporter | ||
Comment 6•22 years ago
|
||
hoping for 1.3 final
Assignee: sspitzer → neil
Flags: blocking1.3?
Target Milestone: --- → mozilla1.3final
Reporter | ||
Updated•22 years ago
|
Comment 7•22 years ago
|
||
Comment on attachment 114657 [details] [diff] [review]
Proposed patch
I don't like this patch.
What do we need to do to really fix bug 90337 (and hopefully this bug)?
Attachment #114657 -
Flags: review?(jaggernaut) → review-
Assignee | ||
Comment 8•22 years ago
|
||
In the long term, yes, but what's best for 1.3?
Comment 9•22 years ago
|
||
we'd consider taking a safe fix for this but we're not going to block on it.
Flags: blocking1.3? → blocking1.3-
Assignee | ||
Comment 10•22 years ago
|
||
Comment on attachment 114657 [details] [diff] [review]
Proposed patch
So jag, is this a safe fix for 1.3?
Attachment #114657 -
Flags: review- → review?(jaggernaut)
Comment 11•22 years ago
|
||
Maybe we could take this on the 1.3 branch, but I'm afraid that if we stick this
on the trunk that it's gonna stay there, like so often happens with these hacks.
Comment 13•22 years ago
|
||
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.3) Gecko/20030307
I use 1.3 Candidate for Linux version.
It seems that the start page of Mail & Newgroups will be initialized to the
following timing.
Reproducible: Always
Steps to Reproduce:
1. [Edit (E)] of browser -> mail & newsgroup In the state where it opened [OK]
It pushes.
2. Exit Mozilla.
3. A setup in prefs.js becomes empty.
The following case seems to be satisfactory.
a. Mail & Newsgropus is not opened. [OK] When it pushes.
b. In the state where Mail & Newsgroups was displayed [Cancel].
Please, hoping for 1.3 final !!
Comment 14•22 years ago
|
||
confirming this bug also exists in the latest Mozilla 1.3 test release available
on MozillaZine, released today
(http://www.mozillazine.org/articles/article2963.html). I am also hoping for a
fix in 1.3 final!
Reporter | ||
Comment 15•22 years ago
|
||
if bug #90337 isn't going anywhere fast, I'd rather see this dataloss fixed, and
then backed out (with the other band aid fixes).
varga / jan / neil, suggestions?
No longer depends on: 90337
Reporter | ||
Comment 16•22 years ago
|
||
we shouldn't ship 1.4 with this. (if there is a 1.3.1, I'd want to take a fix
there, too.)
Flags: blocking1.4a?
Whiteboard: [wanted to 1.3.1]
Reporter | ||
Updated•22 years ago
|
Whiteboard: [wanted to 1.3.1] → [wanted for 1.3.1]
Assignee | ||
Comment 17•22 years ago
|
||
This tweaks the band-aid not to cut in if it appears to be unnecessary.
Assignee | ||
Updated•22 years ago
|
Attachment #118026 -
Flags: superreview?(sspitzer)
Attachment #118026 -
Flags: review?(jaggernaut)
Reporter | ||
Comment 18•22 years ago
|
||
what aspect of monster bug #90337 was the original bandaid for?
Reporter | ||
Comment 19•22 years ago
|
||
neil tells me it was for this
(http://bugzilla.mozilla.org/show_bug.cgi?id=90337#c120)
"Hide the Navigation toolbar with the menuitem.
Close the browser.
Reopen and Show the Navigation toolbar.
Nothing in the URL bar works anymore."
neil, does your new bandaid still fix that problem?
Reporter | ||
Comment 20•22 years ago
|
||
I wrote to neil:
> if your new bandaid still fixes that issue, and the pref dataloss issue, and
> doesn't regress any other autocomplete consumers (compose, mailing lists) I'll
> gladly sr it.
neil wrote:
> Better than that, you could even back out your patch to bug 190153!
can you come up with that complete patch then?
Status: NEW → ASSIGNED
Assignee | ||
Comment 21•22 years ago
|
||
Comment 22•22 years ago
|
||
Comment on attachment 118037 [details] [diff] [review]
Patch with backout to fix to bad band-aid
r=varga
please test it well
Attachment #118037 -
Flags: review+
Reporter | ||
Updated•22 years ago
|
Target Milestone: mozilla1.3final → mozilla1.4alpha
Reporter | ||
Updated•22 years ago
|
Attachment #118026 -
Flags: superreview?(sspitzer)
Attachment #118026 -
Flags: review?(jaggernaut)
Reporter | ||
Updated•22 years ago
|
Attachment #114657 -
Flags: superreview?(sspitzer)
Attachment #114657 -
Flags: review?(jaggernaut)
Reporter | ||
Updated•22 years ago
|
Attachment #118037 -
Flags: superreview?(jaggernaut)
Comment 23•22 years ago
|
||
Comment on attachment 118037 [details] [diff] [review]
Patch with backout to fix to bad band-aid
sr=jag
Attachment #118037 -
Flags: superreview?(jaggernaut) → superreview+
Reporter | ||
Comment 24•22 years ago
|
||
I'm going to triage to adt1 / nsbeta1+, since this is dataloss.
thanks for the fix, neil!
Reporter | ||
Comment 25•22 years ago
|
||
fix tested and landed.
thanks again neil.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 27•22 years ago
|
||
back ported to 1.3.1
Updated•22 years ago
|
Whiteboard: [wanted for 1.3.1][adt1] → [fixed1.3.1][adt1]
Comment 28•22 years ago
|
||
Trunk build 2003-04-10: WinXP, Mac 10.1.5, Linux RH 8.0
Verified Fixed.
Status: RESOLVED → VERIFIED
QA Contact: esther → nbaca
Comment 29•22 years ago
|
||
Mozilla 1.3.1 Release Candidate Builds
http://ftp.mozilla.org/pub/mozilla/nightly/latest-1.3.1/
Linux RH 8.0:
Linux RH 7.2:
Verified Fixed.
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•