Closed Bug 343499 Opened 18 years ago Closed 16 years ago

Flip4Mac (F4M) 2.x renders pages incorrectly and causes text to be offset

Categories

(Camino Graveyard :: Plug-ins, defect)

PowerPC
macOS
defect
Not set
major

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: samuel.sidler+old, Unassigned)

References

()

Details

(Whiteboard: READ COMMENT 27 BEFORE COMMENTING)

Attachments

(2 files)

When using the F4M plugin, version 2.0.2 with Camino, the page is rendered incorrectly. Upon scroll, specifically, the page is whited out. The view is cleared when switching tabs (and back) and eventually you're able to scroll properly.

This is an overall bug which I thought I had filed, but apparently didn't. We should be duping other (and existing) bugs to this one.

Testcase forthcoming...
In the URL field is a testcase. This bug could be either on our end or F4Ms and is reminiscent of what WMP did in Camino.
Isn't it the same as bug 341743? I've recently added a comment there, saying the downgrading to F4M 2.0.1 fixes it (al least the displaying of page contents).
Cheers
This is meant to be a simple central bug with a reliable testcase, which other bugs can be duped to. (see comment 1)
*** Bug 341743 has been marked as a duplicate of this bug. ***
*** Bug 329782 has been marked as a duplicate of this bug. ***
The easiest way to reproduce comment 0 is to scroll using the scrollbar until small artifacts of the plugin content are on the page then scroll to the top and press the space bar. Spacing (and shift-spacing) will add lots of white to the page. This screenshot shows what happens.

The problem above is especially noticeable on MySpace pages which have more than one WMV file on them. It also exhibits itself on other tabs -- showing white area on them as well -- until the offending tab has been closed.

A second (and probably related) issue we have is when changing tabs after playing then pausing content, the plugin content remains fixed in the position it was after switching, freezing the frame. We have a long standing bug with this happening with QuickTime content (iirc), but switching tabs twice clears that one up. No matter how many tab changes you do, the F4M content remains fixed on the screen. The testcase in the URL field will exhibit this as well.

Based on the two above issues, and as a non-developer, I'd guess that F4M isn't being contained to its tab, which causes the layout issues and "freeze frames" mentioned above.

This bug report has been reported to the F4M team.
I don't want to inundate this bug reports with screenshots (especially since it's easily reproducible)... but I just did. ;)  I often see this with the "white around the movie" that this screenshot shows (in addition to the behavior in comment 6's attachment)
(In reply to comment #6)
> Created an attachment (id=227993) [edit]
> Screenshot of bad behavior

This screenshot by itself is almost exactly bug 160435 (or at least from 160435 comment 11 on).  Since WMV is now playing through QT, I bet part of the issue here (the non-white-boxes part) is the same (although we're starting to see some sort of "white box" issues with Flash, which no one understands; see bug 292535 and bug 335974).

> A second (and probably related) issue we have is when changing tabs after
> playing then pausing content, the plugin content remains fixed in the position
> it was after switching, freezing the frame. We have a long standing bug with
> this happening with QuickTime content (iirc), but switching tabs twice clears
> that one up. 

QT, Real, Java; bug 156583, for reference.
Ignore the first part of my last comment; Sam explained I didn't understand what I was seeing.  Sorry.
*** Bug 349036 has been marked as a duplicate of this bug. ***
I'm seeing this even when the plug-in is loaded in a new popup.

My reproducible steps:

1. Go to www.bandit.se
2. Click "Lyssna live" (listen live)
3. A new popup window with the internet radio will appear.
4. Go to a bugzilla bug in the main window, and select some text.

Can we somehow contact Microsoft about this, or is it our bug?
Also, I think finding a regression range here could help (at least trying a few older builds too). Maybe only recent plug-in changes expose the bug.
(In reply to comment #11)
> Can we somehow contact Microsoft about this, or is it our bug?

This isn't a Microsoft bug, it's a F4M bug. As I said in comment 6, this bug has been reported to the F4M team and we've been working with them for some time to try and resolve it.

(In reply to comment #12)
> Also, I think finding a regression range here could help (at least trying a few
> older builds too). Maybe only recent plug-in changes expose the bug.

This isn't a regression on our end. There isn't a regression range as far as we can tell. We've always sucked with F4M for some reason and it's figuring out why and working with them to fix it on one end or the other.
Summary: Flip4Mac (F4M) 2.0.2 renders pages incorrectly → Flip4Mac (F4M) 2.1 renders pages incorrectly
*** Bug 351410 has been marked as a duplicate of this bug. ***
*** Bug 363847 has been marked as a duplicate of this bug. ***
Summary: Flip4Mac (F4M) 2.1 renders pages incorrectly → Flip4Mac (F4M) 2.1 renders pages incorrectly and causes text to be offset
FWIW, this is about a thousand percent better since Cairo landed on trunk.

That doesn't mean F4M shouldn't fix it, just felt that ought to be recorded for posterity since Max and I were talking about it on IRC the other night.
Another test case to reproduce...see www.giants.com and click on one of the videos.  The F4M control bar is blotted out and other tabs render improperly as well, moving text field and/or cursor around.
Yes, that's why the bug is still open. We do not need confirmation that the bug is still open; if it were fixed, we would have marked it RESOLVED FIXED.

Please read

https://bugzilla.mozilla.org/page.cgi?id=etiquette.html

before commenting in bugs.
Whiteboard: READ COMMENT 27 BEFORE COMMENTING
I can also confirm that downgrading fixes it...  It's an unfortunate fix, though, as I didn't have a dmg of a 2.0 version, so I had to go back to 1.0 from Flip4Mac's website to get a pre-2.1 version...
I just got out of a meeting with one of the F4M developers, where we found the source of this bug, so the fix is now understood and should presumably be incorporated into some future F4M update (as their time and release schedule allows).
Summary: Flip4Mac (F4M) 2.1 renders pages incorrectly and causes text to be offset → Flip4Mac (F4M) 2.x renders pages incorrectly and causes text to be offset
Since 4 months later there is still not a fixed version of the F4M plugin available, I would encourage anyone affected by this bug to contact support@flip4mac.com and express your desire to see a release of a version that does not break Camino.
(In reply to comment #39)
> Since 4 months later there is still not a fixed version of the F4M plugin
> available, I would encourage anyone affected by this bug to contact
> support@flip4mac.com and express your desire to see a release of a version that
> does not break Camino.

FWIW, there is some hope, maybe, eventually:
https://bugzilla.mozilla.org/show_bug.cgi?id=426524#c14

> Greg Wishart   2008-04-02 14:40:35 PDT
> FYI: 2.2.0.50 does not contain a fix we're putting in for Camino (that'll be
> released around May '08)
> 

Since the recent F4M release didn't fix this issue, I'm making a stopgap fix available:
http://escapedthoughts.com/camino/f4m.html
The fix was finally released in F4M 2.2.1.7b, so we can finally close this as INVALID.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: