dinkmeister wrote: >It's kinda hard to believe Mozilla will suffer a huge performance loss >by making the text un-jiggly. They did it for the larger font(s) right? :) >
Well the problem is this, on OS/2 a fonts character position can be a partial pixel, but it can only start on a pixel boundary. So when you see wiggly text, it is because the character you are trying to select starts on a partial pixel boundary... and when it redraws the text it is using the new pixel boundary (and not the one at the start of the line). The only fix that I can see to this is (without redesigning the mozilla rendering system), redering each character seperately. So no matter what character you select it will always be on a pixel boundary. This is where the performance hit would come in. Entering the Gpi for each character to be rendered (instead of one entry for the entire string) would create a significant performance hit. For this reason, Mike Kaply set this bug to WONTFIX. Because the performance hit by doing this was unacceptable. The mozilla portable runtime was basically designed for the Windows API which does not allow characters to take partial pixels. Which isn't a problem on most other platforms because they simply don't support that feature. The problem comes from OS/2 lack of an ability to *start* on a partial pixel boundary. It's an unusual problem to which I don't see a good solution. Unless someone else can see something that we can't. :) cya... Brian
