Open Bug 282018 Opened 20 years ago Updated 2 years ago

View Source is blank with a page rendered from a javascript function.

Categories

(Toolkit :: View Source, defect)

1.7 Branch
x86
Windows XP
defect

Tracking

()

People

(Reporter: Cloink_Friggson, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007

This *may* be related to bug 204779. I get the impression Moz, instead of
keeping a local copy (whether on disk or in mem) of a dyn-gen'd page, it tries
to re-execute the function that created the page and show the result of the
function call, but doesn't have correct scoping to 'find' the function.

Here's my error message - in the javascript console - when I try View Source for
my dyn-gen'd page:

Error: top.UI_Render is not a function
Source File: javascript:top.UI_Render("GTC");
Line: 1

And yes, UI_Render *is* a function in my top-level window!

Incidentally, this only happens for an embedded frame which has js-gen'd html.

(Bit late, but the keen-eyed will have noticed this is my fourth bug filed
today. All of them apply to Firefox 1.0 as well. I did say on the first, but
forgot to mention on the second and third. 282012/15/16.)

Reproducible: Always

Steps to Reproduce:
1. FRAMESET top-level document. e.g.
    <FRAMESET>
        <FRAME NAME=main SRC=logon.html>
        <FRAME NAME=temp SRC=javascript:top.TestWin()>
    </FRAMESET>

2. Create the html for a frame from a js func (whether from
SRC="javascript:js_func()" in the frameset-ing doc, or from
location.replace('javascript:js_func()') at some later point).

3. Open js console.

4. Right-click > This Frame > View Frame Source.

5. View Source window blank, js error shows in console.

Actual Results:  
Step 5!
Dupe of/related to Bug 60426.
No, not dup of that, and not related to that.

More or less a dup of bug 206531, however.
Depends on: 206531
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
Status: UNCONFIRMED → NEW
Ever confirmed: true
==> viewsource
Assignee: general → mrbkap
URL: n/a
Component: General → ViewSource
QA Contact: general → doronr
Version: unspecified → 1.7 Branch
Assignee: mrbkap → nobody
QA Contact: doronr → view-source
SeaMonkey trunk is now using toolkit viewsource.
Product: SeaMonkey → Toolkit
QA Contact: view-source → view.source
I'm not a developer of the product, I'm a user -- I don't know what that last comment means.  The last time I tried (a few weeks ago, with a recent version), I still got a blank View Source window.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.