188620 - When scrolling window, QT movie (with hidden controller) paints incorrectly during playback

Status: RESOLVED DUPLICATE of bug 160435

(Camino Graveyard :: Plug-ins, defect)

Description

[Chris Petersen]

build: 2003-01-09-04
platform: OS X 10.2.3

Expected Results: QT movie should "pause" at the current frame while user
scrolls the window. After the user has moused up, the movie should begin playing.

What I got: Two things happen: The movie 'flashes' as I scroll and artifacts
paint on the page. This is most noticeable when the movie's controller is hidden.

Steps to reproduce:

1) Go to url
2) Click on "See the keyboard in action" to start movie
3) As the movie plays, grab and drag the window's scroll bar up and down (slowly)
4) Notice the "flashing" effect as the movie is playing. Artifacts are also
painted around the movie during the scrolling of the page.

5) This "flashing" issue isn't occuring in either IE 5.2.2 or Safari beta. I
noticed that when you click and drag the scroll bar, the movie appears to
"pause" at the current frame. When the user has stop scrolling and moused up,
the movie begins again. This might be something we might consider doing.

Comment 1

[Chris Petersen]

Attachment: Reduced test case from url

Test case uses the embed element that specifies the following:
CONTROLLER=FALSE AUTOPLAY=TRUE. Movie automatically plays with no controller.

Scroll page up and down to notice issue described.

Comment 2

[Jasper]

This is still a major issue in Camino. I really agree with Chris that Camino
should pause the Quicktime movie as long as the user is holding the scrollbar.

Why? When the user is going to scroll he/she is looking for something that
(partially) isn't visable. So the priority of the user isn't with the movie that
is visible but other content.

Comment 3

[Simon Fraser [no longer active]]

Here's what Apple said about this bug:

Some time ago you reported a problem with QuickTime and Real Video plugins (see
below) in Chimera. I ended up filing a bug report on this (ID 3120292), and I've
now gotten a diagnosis of the problem from our engineer. Here's what he said:

"Using the -[NSView scrollRect:by:] method will not work with accelerated
surfaces. The developer will need to move the actual view around the window by
changing a containing view's bounds (.i.e. using NSClipView or NSScrollView).
This way, when the view moves, it notifies QT and QT updates a 'surface'
location which CG uses to determine where to render."

Comment 4

[Bruce Davidson]

Looks like a dupe of bug 160435.

Comment 5

[Simon Fraser [no longer active]]

Yeah.

*** This bug has been marked as a duplicate of 160435 ***