Closed Bug 292272 Opened 20 years ago Closed 20 years ago

view marked source doesn't work anymore

Categories

(Core Graveyard :: View Source, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: mail, Assigned: mrbkap)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.7.7) Gecko/20050414 MultiZilla/1.7.0.2b
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.7.7) Gecko/20050414 MultiZilla/1.7.0.2b

View the marked source doesn't work anymore in Mozilla 1.7.7. It works well in
Mozilla 1.7.6 --> regression!

Reproducible: Always

Steps to Reproduce:
1. View any HTML page
2. mark any part of it using the mouse
3. click the right mouse button and choose something like "view marked source"
(german version: Auswahl-Quelltext ansehen)

Actual Results:  
nothing happens

Expected Results:  
The source of the view page should appear in a new tab or window, with the
source of the marked part marked
That would appear to be more a MultiZilla bug than a Mozilla bug: with a fresh
1.7.7 install, view selection source works fine; install MultiZilla 1.7.0.2d and
it fails with 

Error: uncaught exception: [Exception... "Illegal operation on WrappedNative
prototype object"  nsresult: "0x8057000c (NS_ERROR_XPC_BAD_OP_ON_WN_PROTO)" 
location: "JS frame ::
chrome://multiviews/content/multizillaContextMenuOverlay.xul :: anonymous ::
line 97"  data: no]
(In reply to comment #1)
Well, I used the same Multizilla version with Mozilla 1.7.6 (Mozilla/5.0
(Windows; U; Windows NT 5.1; de-AT; rv:1.7.6) Gecko/20050319
MultiZilla/1.7.0.2b), and it worked fine.

Does Multizilla make some assumptions about Mozilla which are not true anymore
with version 1.7.7? Where to put this bug?
look at the multizilla mozdev page perhaps.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Well /I/ don't know whether Mozilla (accidentally) changed a documented API, or
Multizilla relies on something it shouldn't.

However, I created a Multizilla issue:
http://www.mozdev.org/bugs/show_bug.cgi?id=10029
Verified.  What changed in 1.7.7 is that some some forms of DOM access which
lead to major security issues have been disallowed.  Apparently Multizilla was
using one of those....
Product: SeaMonkey → Core Graveyard
You need to log in before you can comment on or make changes to this bug.