260953 - View message source (ctrl-u) doesn't work anymore

Status: RESOLVED WORKSFORME

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Mitch]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a4) Gecko/20040918
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a4) Gecko/20040918

It appears that View->Message Source or Ctrl-U doesn't work anymore. You get a
blank window popup. 

Errormessage in javascript console as follows:

Error: uncaught exception: [Exception... "Component returned failure code:
0xbfffc86c [nsIWebNavigation.loadURI]" nsresult: "0xbfffc86c (<unknown>)"
location: "KS frme :: chrome://navigator/content/viewsource.js::viewSource::line
177" data: no]

Reproducible: Always
Steps to Reproduce:
1. Open mailnews
2. Select a message
3. View source using Ctrl-U key combination or View->Message Source from the
menu bar

Actual Results:  
Blank window popus up

Expected Results:  
Window with message source

Comment 1

[Calum Mackay]

Yup, seeing this too, with a 20040920 build of Thunderbird, linux/x86

Comment 2

[David :Bienvenu]

this works on a tbird windows trunk build from this morning...could this be
linux-specific? It doesn't seem like a key-binding issue since we seem to be
getting to the view source code...

Comment 3

[Mitch]

I rebuilt mozilla on Linux again just now and same behavior (with javascript
error show) so it's not fixed in cvs. Maybe be Linux specific.

Comment 4

[Calum Mackay]

confirmed with a rebuild of Thunderbird linux/x86 from a checkout this morning
(GMT):

Error: uncaught exception: [Exception... "Component returned failure code:
0xbfffc88c [nsIWebNavigation.loadURI]"  nsresult: "0xbfffc88c (<unknown>)" 
location: "JS frame :: chrome://global/content/viewSource.js :: viewSource ::
line 134"  data: no]

Comment 5

[Stephen Donner [:stephend] Not actively reading bugmail]

Isn't this just bug 261043?

Comment 6

[Mitch]

*** This bug has been marked as a duplicate of 261043 ***

Comment 7

[Kyle Yuan]

Can you explain what the relationship between this bug and bug 261043?

Comment 8

[Mitch]

Kyle, i believe bug 261043 deals with shortcuts not working and sounds like a
dup. I've not tried the patch yet myself however. Do you believe it is not the
same ?

Comment 9

[Mitch]

Kyle is right. This probably has nothing to do with bug 261043 since the view
message source doesn't even work from the menu (i.e.not the key shortcut). Reopening

Comment 10

[Tracy Walker [:tracy]]

This is also happening on Mac.  

On Windows View Message Source works as expected.

requesting blocking1.8a4

Comment 11

[Asa Dotzler [:asa]]

If we can get a regression window on this and it's a recent problem, let's try
to find the problematic checkin.

Comment 12

[Tracy Walker [:tracy]]

This has been broken since at least 2004-07-30.

Comment 13

[Calum Mackay]

Seems to be working, as of today's build, for me, 20040927 Linux/x86.

Comment 14

[Calum Mackay]

and since bug 261043 landed (for Linux) just before I did my build, I think that
suggests that this was a dup, after all.

*** This bug has been marked as a duplicate of 261043 ***

Comment 15

[Christian :Biesinger (don't email me, ping me on IRC)]

no it wasn't. comment 12 says this was broken at 7-30 already, while bug 261043
started on 8-21. additionally, the patch only addressed the context menu key and
shift+f10, it is not a general shortcut problem bug.

bug 261098 seems like a much more likely bug, because it has an error code
that's similarly trashed.

reopening to mark as worksforme.

Comment 16

[Christian :Biesinger (don't email me, ping me on IRC)]

(although bug 261098's regression range does not match either)

Comment 17

[David :Bienvenu]

*** Bug 261810 has been marked as a duplicate of this bug. ***