Closed Bug 563030 Opened 14 years ago Closed 14 years ago

setting data member of object tag in javascript does not load the url specified

Categories

(Core Graveyard :: Plug-ins, defect)

Product:
Core Graveyard
Component:
Plug-ins
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: mike.polyakov, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.1.2) Gecko/20090805 Firefox/3.5.2
Build Identifier: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8.1.4) Gecko/20070611 SeaMonkey/1.1.2 Mnenhy/0.7.5.666

When setting the 'data' member of OBJECT tag to a new url, nothing happens. The object frame is still displaying the url that was loaded initially.

Reproducible: Always

Steps to Reproduce:
1. Write this html:
<html>
  <body>
    <head>
    </head>

    <object id='theobject' onload='loaded()' data="http://www.yahoo.com/" type="text/html" width=300 height=200>
    </object>

    <script>
      var x = document.getElementById('theobject');
      x.data = 'http://www.google.com/';
    </script>

  </body>
</html>

2. load the page
3. observe that the object frame remains on yahoo.com, and does not switch to google
Actual Results:  
object frame didn't switch to google.com

Expected Results:  
I expect that setting the 'data' member of object will switch to that url right away
I see that User-Agent says Firefox. I submitted the bug report using Firefox, but the bug itself is in seamonkey with specified build id. Thanks.
Which version of SeaMonkey?
Component: General → Plug-ins
Product: SeaMonkey → Core
QA Contact: general → plugins
> Which version of SeaMonkey?

1.1.2, like comment 0 says.

> the bug itself is in seamonkey with specified build id.

Yeah.  That's using an ancient Gecko from back in Augus 2005 or so, with security fixes only.  This bug was fixed in late September 2005 as part of the checkin for bug 1156.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Depends on: 1156
Resolution: --- → FIXED
And I strongly recommend updating to Seamonkey 2.0.4 today, since Seamonkey 1.1.2 is no longer supported even with security fixes.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.