What steps will reproduce the problem?
1. Create an HTML page that loads a larger image and displays it as a smaller
image.
2. Render this page in FLying Saucer
What is the expected output? What do you see instead?
The expected outcome is that bilinear interpolation will be used to avoid
aliasing issues, but instead nearest-neighbor is used, causing serious aliasing.
What version of the product are you using? On what operating system?
9.0.7 on Windows 8
Please provide any additional information below.
The resizing code does not make use of bilinear interpolation/anti-aliasing
rendering hints which are available in Java 6. The architecture of the
resource loader also includes many cross-class calls of protected
members/classes, and therefore requires a large amount of duplicated code in
order to change this, which is an odd decision for what is supposed to be a
replaceable component.
Original issue reported on code.google.com by sdbayn...@gmail.com on 12 Nov 2014 at 1:10
Original issue reported on code.google.com by
sdbayn...@gmail.comon 12 Nov 2014 at 1:10