273471 - Firefox ignores frames when reading Windows Media Player scripts or commands.

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Ben Groeneveld]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10.1

Scripts or commands embedded into Windows Media Player with asfchop look like:

start_script_table
00:00:01.0 URL
http://66.119.37.169/ownerdata/1039/content/3D6D931B-EAB1-99FA-987E43CB76B100B3/NEW
TECHNIQUES IN MIDFACE_2_Slide001.JPG.htm&&presentation
end_script_table

The trailing "&&presentation" is a frame identifier, which appears to be 
ignored or misinterpreted, because all links played in our player show up in the
same frame.


Reproducible: Always
Steps to Reproduce:
Running the example URL provided in IE and then Firefox demonstrates the problem.  
Actual Results:  
You will notice that links sent to the right, bottom frame "branding" never
appear, and instead appear in the main frame "presentation".


Expected Results:  
Links terminated with &&presentation should appear in the presentation frame,
and those appended with &&branding should apear in the branding frame.

Comment 1

[John Dyer]

This is a show-stopper for skins created by ninesystems.com for education and
informational purposes.

Comment 2

[John Dyer]

It might be possible to write some workaround code if Firefox implimented this
NS 7.1 hack for IE scripting support as defined here:
http://developer-test.mozilla.org/en/docs/Windows_Media_in_Netscape

Comment 3

[Gervase Markham [:gerv]]

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/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.