248731 - IFrame flickers when displaying a DIV over the frame, crashes on trunk [@ nsCutCommand::IsCommandEnabled ]

Status: RESOLVED WORKSFORME

(Core :: DOM: Editor, defect)

Description

[Jorgen Horstink]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8

I think this bug is related to
http://bugzilla.mozilla.org/show_bug.cgi?id=239706, but it is not a dupe. Also
in this case the IFRAME is appended to a floated DIV. But in this case the
IFRAME only flickers if one displays an element over the frame.

See the URL for an example of this problem.

Reproducible: Always
Steps to Reproduce:
1. Set an iframe in a floated element
2. Draw an other element over the iframe

Actual Results:  
The frame flickers

Expected Results:  
The frame should not flicker

Comment 1

[Ian Graham]

Also seen in Mozilla 1.7 and Firefox 0.9 (on Windows XP):
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616)
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040614 Firefox/0.8) 

Comment 2

[Olivier Cahagne]

I see this on Linux using FF 20040625 trunk, additionally, I also crash into
nsCutCommand::IsCommandEnabled when clicking on Editor then Preview a few times:
TB175620M.

Comment 3

[Olivier Cahagne]

Attachment: Stacktrace Mozilla debug build 20040604

Using a debug Linux build from 20040604, I get these assertions before
crashing, steps were clicking once on Preview, then clicking on Editor.

###!!! ASSERTION: Focus events should not be getting thru when this is null!:
'shell', file nsEventStateManager.cpp, line 814
Break: at file nsEventStateManager.cpp, line 814
An error occurred updating the cmd_cut command
An error occurred updating the cmd_copy command
An error occurred updating the cmd_delete command
************************************************************
* Call to xpconnect wrapped JSObject produced this error:  *
[Exception... "Access to restricted URI denied"  code: "1012" nsresult:
"0x805303f4 (NS_ERROR_DOM_BAD_URI)"  location:
"http://www.nextavenue.com/got/nextavenue/bug_1/core.nextavenue.js Line: 365"]
************************************************************

Comment 4

[Olivier Cahagne]

also crashing on Win2k using FF 20040625 trunk.

Comment 5

[Jorgen Horstink]

Okey, this is another bug, maybe someone can track it down. It is possible that 
the current editor object is set NULL. That happens when an exception is thrown 
because e.target.id is empty:

  /**
   * Make sure the current editor will be set if the mouse moves over the IFRAME
   */
  this._addEvent(myFrame, "mouseover", function (e) { 
    if (nextavenue.browser.isIE) {
      nextavenue._currentEditor = e.srcElement.id;
      nextavenue._setFrame(window.frames[e.srcElement.id]);
      
    } else {
      try {
        nextavenue._currentEditor = e.target.id;
        nextavenue._setFrame(d.getElementById(e.target.id).contentWindow);
      } catch (e) {
        nextavenue._currentEditor = null;
        nextavenue._currentEditorObject = null;
      }
    }
  });

So I guess that _currentEditorObject is still null, after the function setFocus
() is called. (setFocus gets the _currentEditorObject and tries to set the 
focus)

I am not able to reproduce the bug. I think this is not dued to the flickering 
issue.

Comment 6

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

Confirming bug, since I see this too.

Comment 7

[Jay Patel [:jay]]

The url is outdated, is there a new testcase for this?  Has anyone seen similar
problems with a recent nightly branch or trunk build?  

I still see the flickering in
https://bugzilla.mozilla.org/attachment.cgi?id=145489 (from bug 239706) with 
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041216

No problems with the same testcase above with: Mozilla/5.0 (Windows; U; Windows
NT 5.1; en-US; rv:1.8a6) Gecko/20041216 Firefox/1.0+

So I wonder if this has been fixed on the Trunk since the last comment from Stephen.

Comment 8

[Martijn Wargers (dead)]

The url is still 404...

Comment 9

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

wfm, since we don't know what fixed this.

build: SeaMonkey 1.5a

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051209 Mozilla/1.0