Closed Bug 554713 Opened 15 years ago Closed 15 years ago

Custom cursors less than 32x32 do not render properly on Mac

Categories

(Core :: Widget: Cocoa, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: vlun, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.3a4pre) Gecko/20100324 Minefield/3.7a4pre Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.3a4pre) Gecko/20100324 Minefield/3.7a4pre Custom cursors finally works on Firefox and Mac. However, if the cursor is less than 32x32, it appears to render incorrectly, the bottom half the image is corrupted. Reproducible: Always
Blocks: 286304
Component: General → Widget: Cocoa
Product: Firefox → Core
QA Contact: general → cocoa
I need an example. Every cursor I tested with was smaller than 32x32 so whatever is happening is probably more subtle.
You can look at the example I posted at the following url. http://www.ideasunplugged.com/test/firefoxtest.php The pngs are test26x26.png test64x64.png test100x100.png and test260x260.png at the same path as above. It's essentially the same image at different sizes. 26x26 is only partially rendered and the full size 260x260 isn't rendered at all. What is the maximum size allowed? This was tested on the Wednesday build. BTW: If you look at the example, there is nothing between the End of experiment and the body of the html but I'm seeing an extra DIV??? Should I report this as a separate bug?
Thanks. There's a limit of 128x128 pixels, which is the same as the Windows build. I see the problem with the 26x26 cursor in last night's nightly build but actually, not in the version built with the fix for bug 529910 included. This was checked in this morning, so can you try tomorrow's nightly please (i.e. the 3/26 build of 3.7a4pre) and see if it is fixed. I think it should be.
Please update the MDC documentation when 3.7 is released because there is no mention of the 128x128 limitation. Thanks for the quick response. I have verified it has been resolved.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
(In reply to comment #4) > Please update the MDC documentation when 3.7 is released because there is no > mention of the 128x128 limitation. Will do
You need to log in before you can comment on or make changes to this bug.