Closed Bug 418005 Opened 16 years ago Closed 16 years ago

Opening m3u Files broken with iTunes 7.6

Categories

(Firefox :: File Handling, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 236389

People

(Reporter: goocky, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12

Looks like a CONFIRMED PROBLEM!!! 

Hope FF + Apple will fix this:

<http://www.google.com/search?hl=en&q=firefox+m3u+mac&btnG=Search> 

<http://support.mozilla.com/tiki-view_forum_thread.php?comments_parentId=4438&forumId=1> 

<http://discussions.apple.com/thread.jspa?messageID=6497480> 

TEMP FIX WORKS, but no fun!!!

<http://www.jforsythe.com/jforsytheblog/2008/01/24/ApplescriptITunes76AndFirefox20011M3uFileUnfcker.aspx> 



Reproducible: Always

Steps to Reproduce:
1.
2.
3.



PLEASE FIX THIS!
http://discussions.apple.com/thread.jspa?messageID=6497480 claims this is a bug in iTunes, and was introduced in iTunes 7.6.  (iTunes apparently rejects m3u files with a 'creator'.)  So why are you demanding that Firefox be changed?

Does this work correctly on in Firefox 3 Beta 3?  I think it might because of the patch for bug 236389.
Hi Jesse! 

This is AMAZING! I didn't expect to hear from anyone, never mind this fast!!! 

I am not looking to point the finger, I just want it to work. Where do I get this FF Beta? If you are on Mac, and have that Beta 3, please let me know this works!

If it does, it'll be probably faster for FF to help this issue than Apple.. Just a guess:) 

THANKS 4 YOUR QUICK REPLY!
Thanks Jesse, 

Can I use 3 an my current one back and forth, or do I need to Delete my Current one? Will Using 3 mess up my Current FF? 

Or should I just wait till it's Fixed? Again, I am not pointing finger, I just am trying to figure out who's at fault here... Safari is obviously handling this M3U Format differently, cause it works with iTunes 7.6... 
Switching back and forth between Firefox 2.0.0.x and Firefox 3 betas might cause problems.  If you think you'll be switching back to Firefox 2.0.0.x after trying the beta, you can instruct the beta to use a different profile.  Instead of double-clicking on it, run it from the command line with the -P parameter.  (e.g. "/Applications/Firefox 3 Beta 3.app/Contents/MacOS/firefox -P")
Oops... Command Line, Terminal -- way over my head!!!:)!

So I guess I'll have to wait?! So, how will I know this was fixed? Will FF Folks anounce it, or should I just keep checking if it works with each FF2 Updater, or iTunes Updater? Any suggestions?

BTW, JESSE, you ROCK with your quick replies! Are you one of the Developers for FF? I am not sure how that FF Open Source thing works... But, it works! AMAZING! 
You can CC yourself to bug 236389 and see if the patch there gets accepted on the Firefox 2 branch.  I don't think that's especially likely; that branch mostly gets fixes for security holes and regressions in Firefox (rather than regressions introduced by other software such as iTunes).

I do a little bit of Firefox development, but I mostly look for security holes and triage bug reports (like this one :)).
Summary: FIREFOX M3U BROKEN WITH ITUNES 7.6 MAC - CONFIRMED PROBLEM → Opening m3u Files broken with iTunes 7.6
 Your comment was:

    Matthias Versen (matti)   2008-02-16 17:56:05 PST

    *** Bug 416736 has been marked as a duplicate of this bug. ***

    This is beginning to look like a Forum?! Looks like others are having the same
    issue!

    "- Comment #8 from Jesse Ruderman <jruderman@gmail.com>  2008-02-16 17:58:45
    PST ---
    You can CC yourself to bug 236389 and see if the patch there gets accepted on
    the Firefox 2 branch." 

    I am no Newbie, but I can't figure out the Anatomy of this Exchange, on this
    page... Can someone provide a Quick Explanation in PLAIN ENGLISH, please:)!

    Either way, BRAVO!!!!!!!!! I am so impressed by THIS PAGE, CONCEPT,
    ECHOSYSTEM!!!

You have the following choices: 
This is no Forum and this is no end-user support system, it's a developer tool.
Please avoid useless comments that doesn't contain new informations that are needed for the bug itself.
If you have questions about bugzilla you may find informations on http://www.bugzilla.org/, if you need end-user support please go to http://support.mozilla.com/

There is only one additional comment needed here: Does this work with Firefox3beta because bug 236389 is fixed ?
Thanks for the Links. 

Does this: 

There is only one additional comment needed here: Does this work with
Firefox3beta because bug 236389 is fixed ? 

mean that this issue is solved? If so, do I re-download FF, or do I just need to wait for the next Update? 

Thanks!
bug 236389 is only fixed in the trunk and not in the branch.
The trunk is the current Firefox3 development tree, the branch is the old Firefox2 development tree. (see http://en.wikipedia.org/wiki/Branching_%28software%29)
It's unconfirmed that bug 236389 fixed the issue, I would mark this bug as dupe of bug bug 236389 in that case.
You have to wait for Firefox3, it this get fixed on the branch (unlikely) then you have to wait for the next Firefox release such as 2.0.0.13.
AK, we're asking *you* to test whether the patch in bug 236389 fixed the problem for Firefox 3, by trying out a beta :)
Guys, 

I can't try FF 3, since I don't know that Command Line stuff you mentioned earlier (see  above). I am concerned about messing up my FF, cause I would need to go back to FF 2... 

If you guys want to try FF3, I'd love to hear about that, but I am not a developer like you. 

Sorry, and of course THANK YOU for your help! I guess I'll just wait like the rest of the world:)!? 
I had confirmed that this worked with Fx 3.0 and Safari back on Jan. 18th when I submitted bug 412991 which is ironically now duped to this bug which was reported a month later.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Thank you everyone! 

I'll just wait, cause I don't want to switch back and forth between FF 3 and 2. 

Hope FF Developers are reading these pages! 
GOOD NEWS: iTunes 7.6.1 has fixed this. 

Thank you, the author of m3u-un-fcker for the temp fix. Hope we don't need your help with this again... 

In retrospect, instead of m3u-un-fcker, it would have probably been easier to Command Tab/Switch to Safari, rather than do m3u-un-fcker, then drop it into iTunes... But, to each their own workflows!  

Thanks to all who posted here! 

You need to log in before you can comment on or make changes to this bug.