995706 - I am not able to read, compose or send e-mail from my Yahoo Mail accounts (no easy toggle for external protocol handlers)

Status: RESOLVED FIXED

(SeaMonkey :: MailNews: General, defect)

Description

[lianagan]

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25 (Beta/Release)
Build ID: 20140318183706

Steps to reproduce:

After I log in to my yahoo mail account messages are retrieved and downloaded into my inbox, however, when I click on the message or on "Inbox" the message(s) will not open. Clicking on "compose" does not open a blank message window, clicking on any and all folders does not open the folder, clicking on "contacts" does not take me to my contacts page, and hovering the cursor over my name in the upper right corner does not open the usual drop down menu to allow me to log out, and my avatar icon does not appear next to my name. If I click on the name it takes me to the page to set up my profile and only then the icon and drop down menu appears letting me log out. 


Actual results:

Mail messages did not open and nothing else responded to my mouse clicks in the mail program so I clicked on my name to take me to the profile page and logged out


Expected results:

I should have been able to read and reply to messages, file messages, compose new messages and add people to my contacts.

Comment 1

[lianagan]

I have to switch to Google Chrome just to use my Yahoo Mail but I really prefer SeaMonkey. Some of us will be using XP for a little while longer. I don't have SeaMonkey on another computer with a different OS so I don't know if this problem is particular to XP or 2.25.

Comment 2

[poko_poko]

I have Windows 8.1 with Seamonkey 2.25 with the same problem, so it has nothing to do with Microsoft ending support for XP.  I also downgraded to various older Seamonkey releases (2.24, 2.16, 2.3) as well as the latest 2.26 Beta and they all have the same problem with Yahoo Mail.  I am certain that Yahoo Mail worked fine in the past with prior releases of Seamonkey, so the change is with Yahoo Mail recently that made Seamonkey stop working for using Yahoo Mail.  However, Mozilla Firefox continues to work OK with Yahoo Mail so the problem is something specific to Seamonkey and not a problem with the Mozilla engine that both Seamonkey and Firefox share.

Comment 3

[therube]

This only occurs with Yahoo's "New Mail", not with their "semi-Classic" version.
semi-Classic continues to work.

Firefox does work (with New Mail).

Setting a useragent has no affect:

> general.useragent.override;Mozilla/5.0 (Windows NT 6.1; WOW64; rv:28.0) Gecko/20100101 Firefox/28.0
 
 
(I must say, Yahoo's "New Mail" UI is horrid.)

Comment 4

[therube]

Note:

If you disable JavaScript, you are sent to a screen with a link, "Continue without upgrading javascript." that will revert you back to the semi-Classic mode.

Comment 6

[therube]

Work-around for "New Mail":

about:config
right-click context-menu; New Boolean
Name: network.protocol-handler.external.mailto
Value: true

(Thanks to Lemon Juice, http://forums.mozillazine.org/viewtopic.php?f=40&t=2819891&p=13466993)
 
 
Now, is this a DUP of or maybe should be added as a Depends to Bug 995737 - adapt seamonkey for the ab remote content policy change; use permission manager instead of address book property ?

Comment 7

[lemon_juice]

I think this should be marked as a DUP of Bug 995802, where I've explained in detail what the problem really is and made the title that should be clearer and not misleading (since this has nothing to do with MS ending support for XP and it affects both Windows and Linux and probably Mac, too).

Comment 8

[Nagus]

I went to about:config in SeaMonkey tab and went down the list but could not find "network.protocol-handler.external.mailto".  I am missing a step somewhere.  Can anyone help? TIA

I have the same problem with Yahoo Mail where the webpage is missing the small icons for mail forward, reply, delete, spam, etc.  The compose icon doesn't work and I can't open a message to read it.  Using IE to get to my Yahoo Mail now.  This problem just happened end of last week.

Comment 9

[poko_poko]

lemon_juice, thank you for your analysis to pinpoint where the problem was.

therube, thanks for explaining the steps to implement the fix.  I never even knew how to get to about:config but I was able to make the change and Yahoo Mail works fine again.

Nagus, here's some help: You're right, "network.protocol-handler.external.mailto" doesn't exist.  After you go to about:config, you have to add it by right-clicking in the main body, select "New" / "Boolean" with that new Preference Name, and set the value to True.  You probably need to restart Seamonkey after that.  That's what I did and Yahoo Mail is OK again.

Comment 10

[Nagus]

[e-mail],  Thank you very much.  I followed the steps you outlined and it worked.  Question for you, how can we get the developers at SeaMonkey to add that fix permanently to the next release of SeaMonkey,  2.26?  

Thanks again.

Comment 11

[rsx11m]

Modified title as this appears to be coincidental in timing with the end of Windows XP support.

Comment 12

[rsx11m]

(In reply to lemon_juice from comment #7)
> I think this should be marked as a DUP of Bug 995802,

I have confirmed your bug as Core/Networking bug for the suggested backend changes in the handler code. Let's keep this bug here open to define the default preferences for the mail/news handlers for easier modification, which needs to be done anyway. If the Core people decide to won't-fix bug 995802, there is probably not much else that can be done other than making those preferences easier accessible.

Comment 13

[rsx11m]

Attachment: add mail/news handler prefs

This is copy-pasted from browser/app/profile/firefox.js in mozilla-central, but the prefs retained as false by default. In this way, they are made available in about:config without the need to create them from scratch, thus are easier to toggle if an external handler is desired. If they are switched to true, the second set of preferences avoids that the user is prompted, thus showing the same behavior as Firefox has defined by default in these cases.

Comment 14

[Philip Chee]

Comment on attachment 8406516 [details] [diff] [review]
add mail/news handler prefs

(In reply to rsx11m from comment #13)
> Created attachment 8406516 [details] [diff] [review]
> add mail/news handler prefs
> 
> This is copy-pasted from browser/app/profile/firefox.js in mozilla-central,
> but the prefs retained as false by default. In this way, they are made
> available in about:config without the need to create them from scratch, thus
> are easier to toggle if an external handler is desired. If they are switched
> to true, the second set of preferences avoids that the user is prompted,
> thus showing the same behavior as Firefox has defined by default in these
> cases.

Looks reasonable. But IanN is the preferences person (and mailnews) so I'll defer to him.

Comment 15

[lemon_juice]

(In reply to rsx11m from comment #12)
> I have confirmed your bug as Core/Networking bug for the suggested backend
> changes in the handler code. Let's keep this bug here open to define the
> default preferences for the mail/news handlers for easier modification,
> which needs to be done anyway. If the Core people decide to won't-fix bug
> 995802, there is probably not much else that can be done other than making
> those preferences easier accessible.

Thanks. Let's hope the Core people will handle it otherwise we'll have to revert to evangelism, which can have dubious results. network.protocol-handler.external.mailto set to true is still a workaround even if the pref is exposed.

Comment 16

[rsx11m]

Comment on attachment 8406516 [details] [diff] [review]
add mail/news handler prefs

(In reply to Philip Chee from comment #14)
> Looks reasonable. But IanN is the preferences person (and mailnews) so I'll
> defer to him.

Thanks Phil. I was asking for your feedback in case you have any other idea how to solve this which I may have missed. Thus, let's turn this into a review request for IanN as these definitions seem to be necessary either way.

Comment 17

[rsx11m]

(In reply to lemon_juice from comment #15)
> network.protocol-handler.external.mailto set to true is still a workaround
> even if the pref is exposed.

Yes, I know, but it makes life easier for those affected. The only other idea along these lines coming into my mind is to add a checkbox like "Allow external application for mail/news links" in the Helper Application or Mail & Newsgroups preference panes.

Comment 18

[lemon_juice]

(In reply to rsx11m from comment #17)
> (In reply to lemon_juice from comment #15)
> > network.protocol-handler.external.mailto set to true is still a workaround
> > even if the pref is exposed.
> 
> Yes, I know, but it makes life easier for those affected. The only other
> idea along these lines coming into my mind is to add a checkbox like "Allow
> external application for mail/news links" in the Helper Application or Mail
> & Newsgroups preference panes.

I'm all for exposing the pref, I was just pointing out this is not the real fix for the Yahoo issue - but it looks like things are going in the right direction as a concrete patch has been proposed in Bug 995802.

When we are at the pref - there is an ancient Bug 173465 about adding a proper UI for this. I think this is the most proper way of handling this, it would be great if that bug gained some more traction...

Comment 19

[rsx11m]

(In reply to lemon_juice from comment #18)
> I'm all for exposing the pref, I was just pointing out this is not the real
> fix for the Yahoo issue - but it looks like things are going in the right
> direction as a concrete patch has been proposed in Bug 995802.

Yes, this seems to be a bug on our side after all (a typo and replacing "throw" with "log" where the exception is raised).

> When we are at the pref - there is an ancient Bug 173465 about adding a
> proper UI for this. I think this is the most proper way of handling this, it
> would be great if that bug gained some more traction...

I'll have a look, some ideas are already posted in that bug and I've got yet another one where it would fit. Thus, defining the default preferences may be all that's to be done here.

Comment 20

[rsx11m]

Comment on attachment 8406516 [details] [diff] [review]
add mail/news handler prefs

>+// ...but without warning dialogs if switched to external
>+pref("network.protocol-handler.warn-external.mailto", false);
>+pref("network.protocol-handler.warn-external.news", false);
>+pref("network.protocol-handler.warn-external.snews", false);
>+pref("network.protocol-handler.warn-external.nntp", false);

Hmm, looking at http://forums.mozillazine.org/viewtopic.php?p=13473047#p13473047 I'm wondering if the default for those should be "true" rather. In contrast to Firefox we have our own Mail/News protocol handler, which seems to be offered in the warning dialog even when an external protocol handler is defined. In this way, the user is given a choice on a case-by-case basis whether to open the mail/news link in SeaMonkey's component or in the Yahoo site or in another 3rd-party application. I assume that checking "Remember my choice" will shut up the dialog the next time a link is clicked on by adding it to mimeTypes.rdf?

So, this might be a good extra step if it can be done without getting annoying with each invocation. I'd still leave the default prefs intact as defined in the patch (just switched to true) if someone wants to toggle those.

Comment 21

[rsx11m]

Attachment: alternative patch

(In reply to rsx11m from comment #20)
> ... . In this way, the user is given a choice on a case-by-case basis
> whether to open the mail/news link in SeaMonkey's component or in the Yahoo
> site or in another 3rd-party application. I assume that checking "Remember
> my choice" will shut up the dialog the next time a link is clicked on by
> adding it to mimeTypes.rdf?

Ok, so yes and no. The choice is between the system's registered default application (which may or may not be SeaMonkey) and any other registered handlers within SeaMonkey, but not the mail/news component. Thus, setting network.protocol-handler.external.mailto = true is still not an option.

And yes, the checkbox adds an entry to mimeTypes.rdf with alwaysAsk=false.

I'm posting this second patch for you to pick either from, whatever seems better from the user's perspective.

Comment 22

[lemon_juice]

(In reply to rsx11m from comment #21)
> I'm posting this second patch for you to pick either from, whatever seems
> better from the user's perspective.

Hm, I can't really see what the difference is from the user's perspecive regarding true or false for network.protocol-handler.warn-external.XXX. In my installation there is only network.protocol-handler.warn-external-default, which is false by default but I tried going through the process of adding a mailto: handler by visiting Yahoo Mail and then clicking some mailto: links and regardless of the value of network.protocol-handler.warn-external-default the behaviour was the same: on first click I was offered the choice and the checkbox allowed be to suppress further asking. Maybe I'm missing something but I don't really see how network.protocol-handler.warn-external... changes anything for the user.

Comment 23

[rsx11m]

(In reply to lemon_juice from comment #22)
> visiting Yahoo Mail and then clicking some mailto: links and regardless of
> the value of network.protocol-handler.warn-external-default the behaviour
> was the same: on first click I was offered the choice and the checkbox
> allowed be to suppress further asking.

With network.protocol-handler.external.mailto true and network.protocol-handler.warn-external.mailto either missing or true, you should get the box to select the application to open. However, setting network.protocol-handler.warn-external.mailto false with network.protocol-handler.external.mailto true (Firefox's default behavior), the default mail application should be opened right away without the dialog being displayed at least the first time you open a mailto: link. Thus, I think that the second patch might be better to verify that the desired application is taken, then omitting it later.

Comment 24

[rsx11m]

(In reply to rsx11m from comment #20)
> ... . In this way, the user is given a choice on a case-by-case basis
> whether to open the mail/news link in SeaMonkey's component or in the Yahoo
> site or in another 3rd-party application.

Heh, this doesn't quite work as expected when you actually pick SeaMonkey as the protocol handler. You are ending up in an endless loop of a new tab opening and asking you to pick the application, given that network.protocol-handler.external.mailto is still true and hence SeaMonkey isn't supposed to handle the mailto: request itself, even if registered as the actual default protocol handler. :-\

Thus, the only benefit of showing the dialog would be to allow the user to pick between Yahoo or a default mail application other than SeaMonkey. On the other hand, that would be a behavior consistent with picking an application for opening files after downloading them.

Neil, any opinion from the UX perspective what the best default for showing the dialog should be?

Comment 25

[[e-mail]]

My preference would be to default to showing the warning dialog. I don't know where the logic for the warning dialog lives, otherwise I would suggest that the dialog needs somehow to detect that you've selected SeaMonkey and turn off the external mailto: in that case.

Comment 26

[rsx11m]

Comment on attachment 8406516 [details] [diff] [review]
add mail/news handler prefs

Ok, thanks. So, let's go with the version that defaults to showing the dialog.
I'll file a new bug on the loop when SeaMonkey is the external handler itself.

Comment 27

[rsx11m]

Actually, that is pending as bug 198547 already.

Comment 28

[currter]

I am still having problems using SeaMonkey to
access yahoo mail. I have to wait about a minute
before I get the message about it being slow 
and to use Basic mail.
Once I use basic mail it works and I can retrieve
my yahoo email.

Otherwise, I am using Rockmelt and on occasion firefox
more so.  Flock works as well but I have another issue
with some other website with that one whereas before
I would just use SeaMonkey seamlessly and not jump
through hoops or put out fire with this one or using
other browsers.

Well I hope someone can fix this either it is a Seamonkey
problem or a yahoo! problem  due to incompatibility.
Also I have the problem in various Windows versions (8, 7, Vista)
and on Mac OS 10.9... I have not tried Mint Linux in a while
If I ever get to that Linux partition, I will see if same problem
and may report.

Thank you.

Comment 29

[lemon_juice]

currter, the devs already know about it and the fix is on the way so there's nothing more to add - read this http://forums.mozillazine.org/viewtopic.php?f=40&t=2821115 for more information and for a temporary workaround. This problem should be solved in a future SM release - however, I don't know which one exactly.

Comment 30

[rsx11m]

The patch in bug 995802 which fixes the backend problem of throwing an exception has approval already to land for 2.26 beta, Neil only needs to push it there afaict.

Comment 31

[currter]

Okay sorry for being redundant as  all of your
emails are going into my spam folder on aim.com
or aol.com mail.

So i guess I am missing out on the progress of things.

Oh well.

Back to using Rocketmelt or Flock to access yahoo mail.

Monkey see monkey do.

Comment 32

[currter]

Well I am now having problems with Adobe Flash installing or it says it is
not installed when it was working before.
I also tried Seamonkey on Mint Linux and I had the same problems accessing
or reading yahoo! mail.  I tried using 2.24 and then upgraded to 2.25 and
both versions had problems with yahoo! mail.

Well, I am getting tired of using Seamonkey now and I will have to go back
to Firefox.

Let me know when an update is available to fix these problems as Seamonkey was
working quite well up until 2 or so weeks ago.

I even uninstalled the software and reinstalled 2.25  and problems.
Maybe I will just uninstall Seamonkey and not install it ever again as it seems
unreliable and inconsistent.

Comment 33

[rsx11m]

currter, this is not a support forum and neither off-topic posts like "Flash not working" nor the information that you won't use SeaMonkey for the time being is helpful in solving this issue.

Thanks.

Comment 34

[lianagan]

I would like to add some information that might be relevant to this bug. I am using Ad Block Plus in both Sea Monkey and Google Chrome. When I recently started using Google Chrome to access my Yahoo mail I noticed an ad bar at the top of my inbox that wasn't there a few months ago when I had last used Chrome. I had to go into the Ad Block options in Chrome under "filter lists" to un-check the box "allow some non-intrusive advertising". This has just started to happen with Ad Block Plus in Sea Monkey as well, an advertisement in bold type appears in a theme-colored banner at the top of my inbox, so I did the same thing, went to "Options" and un-checked the box. I still can't do anything else with my Yahoo Mail in Sea Monkey.

Comment 35

[currter]

my apologies or just sue me for getting it wrong and
Monkey see still does not work yahoo mail.

I have abandoned it along with that other issue...
I will prepare my lawyer just in case.

Bye!

Comment 36

[currter]

(In reply to rsx11m from comment #33)
> currter, this is not a support forum and neither off-topic posts like "Flash
> not working" nor the information that you won't use SeaMonkey for the time
> being is helpful in solving this issue.
> 
> Thanks.

All I know is I did not have a problem with SeaMonkey 3 or 4 weeks ago and
all of a sudden, things don't work and on all platforms.
So if I find a way to contact yahoo on the issue , I will submit my comments 
to Yahoo! as well and not put all the pressure and blame on SeaMonkey or Mozilla.

What more can I do? I have cleared caches and cleared everything in the browser
resetting it, I have uninstalled it, reinstalled it and I still have the problem.
DO I have to reinstall the entire operating system to get just this one program
to work when other browsers don't seem to have a problem?

That flash issue was a problem under Vista Business edition.

Well back to Rocketmelt on Mac again. For Windows I will just have to use
Firefox or Flock.

bcc: attorney

Comment 37

[currter]

Okay, since one Monkey don't stop no show,
I have filed a complaint of this issue with Yahoo!
the best way I can until I find a better way to 
channel this bug or issue to the appropriate Yahoo
department.

Have a good weekend.
The following is what I have posted thus far.


I am having problems accessing Yahoo! email using the SeaMonkey browser for the past 2 weeks, whereas before there was no issue.
I have file complaints with Mozilla bugs and seamonkey forums.
They don't seem to know what the problem is due to this sudden
incompatibility and they seem to be paralyzed finding a concrete solution for it and I have experienced pushback or a level of indifference. So hopefully Yahoo can figure out the problem
to solve it for Yahoo or Seamonkey.

Thank you.

Comment 38

[rsx11m]

Thanks for filing a complaint with Yahoo. It's certainly a contributing factor from their end that they don't catch the exception thrown in the current SeaMonkey release versions.

As an update, throwing this exception will be removed with bug 995802 (comment #30), and I've just posted some user-interface additions to the preference panes in bug 173465 to toggle the prefs.

Comment 39

[currter]

I will , whenever I execute SeaMonkey as it is almost a memory now,
I will keep applying for the updates... let me check now to see
if any update since 2.25....

....
....
Nope, no new update so I even found another browser for Windows
that works: Maxthon browser... So I am all set with alternative
browsers in both Windows and Mac.

Good luck Seamonkey as I don't have time to be monkeying around. :)

Comment 40

[Frank Wein [:mcsmurf]]

Thanks for your opinion, but it's still off-topic. The issue will be fixed in SeaMonkey 2.26 which will be released in two weeks or so.

Comment 42

[currter]

Well, I must say I have seen some improvement on both Mac and
Windows (surprisingly) and I have not updated to anything after
2.25. I was able to go to yahoo mail and it worked fine it seemed.
Maybe Yahoo has done something on its end.
It is still too early to tell as I have not tested other computers
outside my Macbook (runs both Mac/OS 10.9 and Windows 8). nor have
I checked Linux Mint.

Well things are looking good and back to normal I think.

Keep up the good work with whatever you did or didn't do.

Comment 43

[lemon_juice]

Yes, Yahoo has corrected their script and wrapped the problematic code in a try...catch block so their mail works properly in Seamonkey. However, this should also be fixed in Seamonkey so that similar problems don't happen in the future.

I don't know what is happening to bug 995802 - is there any progress?

Comment 44

[rsx11m]

IanN, Neil: Ping for progress here and in bug 995802 if those are supposed to make the 2.26 release!

Comment 45

[lianagan]

Yahoo mail is still not working in Seamonkey on my PC with the old XP3 so please continue your efforts to correct this. Thank you.

Comment 46

[Nagus]

Yahoo mail was working for a short time this morning on SeaMonkey.  Now it is not.  Yahoo must have changed the script again.

Comment 47

[currter]

I spoke too soon and yes I had problems again with SeaMonkey and Yahoo mail...
I just now got to it about an hour ago but I was handling some other issues
to acknowledge this and respond in time.

Well best of luck you two (SeaMonkey or Mozilla and Yahoo Mail) while you
both wrestling with this.  I am back to RocketMelt for now on Mac and have not
really left it. And Maxthon on Windows when I get to that.

SeaMonkey just now states: Taking Too Long - use Basic Mail.

Comment 48

[currter]

It was good while it lasted I guess. 

Maybe Version 2.26 has better things in store and Seamonkey should
develop fail-safe code for once or a change.
Software should be able to withstand changes or weather the storm... well at least it does not crash
,it just hangs there until that Taking too Long message I guess from Yahoo
not Seamonkey and to use Basic Yahoo Mail..

Comment 49

[currter]

I chose to continue to use SeaMonkey considering all the other
alternative browsers I could choose from that still work with Yahoo mail
because SeaMonkey kind of reminds me of the old Netscape especially 
Netscape 7.2 that had the email feature and the website or web page
development software.

I still use an old version of Netscape Communicator or is it Navigator
9.0 something.  I could use Netscape but there is something weird with the
lay out of some websites or I see overlap and some text covers others
as Netscape is no longer being supported or updated to handle the new
browsing features but one thing, Netscape does work with Yahoo mail now.

Bring back Netscape or merge or link /pair it with SeaMonkey somehow.

Comment 50

[rsx11m]

Netscape has been dead for ages and the later 8.x/9.x versions were based on Firefox anyway (whereas Netscape 6.x/7.x were based on the Mozilla Application Suite = now SeaMonkey). So, if 9.0 still works for you and you don't mind the security holes which are definitely coming with it, fine.

Also keep in mind that SeaMonkey is a mostly volunteer-driven community project with limited resources. Everybody is welcome to throw in a patch for review themselves.

Comment 51

[lemon_juice]

Yes, Yahoo is doing some weird things as they removed the try...catch around registerProtocolHandler(), which was there earlier today. Of course, this causes Seamonkey to throw the error again. I wonder what caused them to withdraw the earlier fix...

Netscape 9 and other ancient browsers are likely to work fine with Yahoo because those browsers didn't even have the registerProtocolHandler() function, for whose existence Yahoo code does check, so there is no attempt to run the function. The problem now is that the check for the existence is positive while the execution results in an error. I hope the fix for Seamonkey will land soon.

Comment 52

[rsx11m]

I think that comm-beta is currently semi-closed as Thunderbird is struggling getting their 29.0 beta out (on the other hand, that shouldn't have an impact on SeaMonkey-only patches, but who knows).

And yes, both SeaMonkey and Yahoo have screwed up here: The former by a too picky implementation of the feature, the latter by not having a fallback if the registration fails with an exception.

Comment 53

[currter]

Good morning, I decided to disable javascript or something and Yahoo Mail works fine.

I guess people have been saying that here... it is just that who wants to be
changing settings and then have to remember to set them back in the future and
remembering which ones were modified?

The browser has so many options that the common user may become confused.

So I guess in the Preferences section , Disable Javascript (Advanced, Scripts/Plugins)...
well hopefully a fix will come soon or that's right I can still use RocketMelt.

Have fun.

Comment 54

[currter]

(In reply to currter from comment #53)
> Good morning, I decided to disable javascript or something and Yahoo Mail
> works fine.
> 
> I guess people have been saying that here... it is just that who wants to be
> changing settings and then have to remember to set them back in the future
> and
> remembering which ones were modified?
> 
> The browser has so many options that the common user may become confused.
> 
> So I guess in the Preferences section , Disable Javascript (Advanced,
> Scripts/Plugins)...
> well hopefully a fix will come soon or that's right I can still use
> RocketMelt.
> 
> Have fun.

of course I had to re-enable Javascript to successfully view and benefit from
viewing some websites...
who has time to be going through these acrobatics with just 1 browser that
is not functioning properly with Yahoo! when all other browsers are not having
the same problems?

So Seamonkey is back in the archived list of applications while Maxthon and 
RocketMelt have been promoted for use... until I see an update to Seamonkey as
I will only execute SeaMonkey to check for its update whenever that is and if
not, close it until further notice.

Comment 55

[Andrea Govoni]

(In reply to currter from comment #54)
> So Seamonkey is back in the archived list of applications while Maxthon and 
> RocketMelt have been promoted for use... until I see an update to Seamonkey

Please Stop Spamming.

Comment 56

[rsx11m]

If disabling JavaScript still leaves the Yahoo webmail site intact while working around the exception issue (obviously, as registering a mail handler requires JavaScript), consider installing the NoScript extension from https://addons.mozilla.org/seamonkey/addon/noscript which allows you to enable scripts for specific websites only (the default is "disabled" thus you'd have to enable it for websites which break without it, but that's easily done from a toolbar menu).

(In reply to Andrea Govoni from comment #55)
> Please Stop Spamming.

Yes, but for a change this information might actually present a helpful workaround for people.

Again, this is not a general discussion forum, so please let's stop the chit-chat now.

Comment 57

[rsx11m]

Comment on attachment 8407963 [details] [diff] [review]
alternative patch

Thanks IanN. In the case that bug 995802 doesn't entirely fix the issue for 2.26, I'm also requesting branch approval (should be safe to land).

[Approval Request Comment]
Regression caused by (bug #): Yahoo
User impact if declined: gives users a better way to toggle the pref to avoid the interoperability with their mail site if problems persists
Testing completed (on m-c, etc.): works on c-c, applies to c-a/c-b
Risk to taking this patch (and alternatives if risky): very low
String changes made by this patch: none

Comment 58

[currter]

(In reply to Andrea Govoni from comment #55)
> (In reply to currter from comment #54)
> > So Seamonkey is back in the archived list of applications while Maxthon and 
> > RocketMelt have been promoted for use... until I see an update to Seamonkey
> 
> Please Stop Spamming.
Whatever, if this **** does not work properly then someone needs to know what does work
!

I am out of here
fix this junk browser if you want. I am tired of this.

Comment 59

[currter]

I am tired of seeing these responses so I will delete this account.
Seamonkey can kiss my $$

Comment 60

[rsx11m]

currter: please grow up - bye!

Comment 61

[currter]

please delete this account. I am not getting email now

so please delete this account I do not want to be bothered by it any more
I found or discovered this problem and you did not work on it as you said
it was a duplicate and it is now 3 or 4 weeks later and the problem still
exists.

Please delete this account!

Comment 62

[currter]

I am so sorry I reported this bug and I am the one to blame here.
I am sorry I reported this please forgive me

DELETE THIS ACCOUNT!

Comment 63

[rsx11m]

(a) you didn't report this bug, that was somebody else, and
(b) I can't delete your account but I've informed the one in charge

Comment 64

[currter]

(In reply to currter from comment #58)
> (In reply to Andrea Govoni from comment #55)
> > (In reply to currter from comment #54)
> > > So Seamonkey is back in the archived list of applications while Maxthon and 
> > > RocketMelt have been promoted for use... until I see an update to Seamonkey
> > 
> > Please Stop Spamming.
> Whatever, if this **** does not work properly then someone needs to know
> what does work
> !
> 
> I am out of here
> fix this junk browser if you want. I am tired of this.

I have been spammed by this forum from the start , emails go to my
spam folder so Please stop spamming me!

Delete this account for me I am so sorry I signed up and reported bugs
when you don't seem to be interested telling whatever I see as a problem
is a duplicate of another bug. Then you should have fixed it if you
knew it was a problem before I discovered it.

Have fun. and stop spamming me or I may contact a lawyer.

Comment 65

[rsx11m]

Just switch off the e-mail notifications in the preference, there is a link to those with every e-mail you get. Be assured that this will be my last comment directed to you. Bye again.

Comment 66

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/comm-central/rev/ca113c2a2e1d

Comment 67

[rsx11m]

Comment on attachment 8407963 [details] [diff] [review]
alternative patch

I'm cancelling the branch requests as Standard8 likely wants to go ahead with the release merge soon (reading the #maildev logs). Now that bug 995802 has landed on comm-beta and another workaround disabling Yahoo's protocol-handler function entirely using the Stylish extension has been posted[1], this patch can probably just ride down the release train the usual way.

If it turns out after next week's SM 2.26 release that issues persist for which providing the protocol-handler preferences by default would be beneficial, we can always renominate for comm-beta at that time.

[1] http://forums.mozillazine.org/viewtopic.php?p=13487405#p13487405

Comment 68

[rsx11m]

SeaMonkey 2.26 is out and reportedly fixes the issue, http://www.seamonkey-project.org/

Thus, hopefully no need for any further action after updating other than resetting the preference if you've toggled it as was recommended as the workaround.