Closed Bug 289452 Opened 20 years ago Closed 19 years ago

Slow resizing / image handling

Categories

(Core Graveyard :: GFX: Gtk, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: islewind, Assigned: blizzard)

References

()

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050325 Firefox/1.0.2 (Debian package 1.0.2-1)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050325 Firefox/1.0.2 (Debian package 1.0.2-1)

Gecko is visibly slower than khtml and opera on X11 when rendering this
xhtml+css+js based panning image viewer. When turning of the navigator panning
a large image becomes better but it still is not interactive speeds.
Rendering speed reported to be ok on win32.

Reproducible: Always

Steps to Reproduce:
1.visit page
2.press go
3.explore photograph


Actual Results:  
User left webpage, claiming rich media belongs in flash and not xhtml+css+js

Expected Results:  
Impress the user with a blazingly fast rendering engine, caching images when
neccesary, and using whatever hardware accelleration is available.
Assignee: roland.mainz → blizzard
Component: GFX: Xlib → GFX: Gtk
QA Contact: xlib → ian
You did test a trunk build, not the outdated thing that is 1.7 branch (and
Firefox 1.0.x) right?

Note that Opera 8 doesn't even allow panning on that testcase, so I can't
usefully compare our rendering to Opera's....
(In reply to comment #1)
> You did test a trunk build, not the outdated thing that is 1.7 branch (and
> Firefox 1.0.x) right?

For both branches the update interval falls far below acceptable interaction
speed on this 1ghz machine with ati radeon.
For some reason, we aren't clipping anymore..

For example, nsImageWin::Draw is getting a srcRect=(0,0,9097,1771) and a
dstRect=(-8777,-1581,9097,1771)

Layout (nsImageFrame?) should be telling draw srcRect=(8777,1581,320,190) instead
If it did, we'd completely fail to draw right on Unix.  See
http://lxr.mozilla.org/seamonkey/source/layout/generic/nsImageFrame.cpp#1383 and
bug 254659.
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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.