Sure, there is an open bug on the firefox bugzilla. https://bugzilla.mozilla.org/show_bug.cgi?id=215055
Which has been open for 6 years. Firefox uses a 16bit api in windows to render elements with scroll bars. However the 16bit api runs out of numbers after 16384. So the rest of the box is not drawn, since windows doesn't know how to address these values with a 16bit space. The bug report at mozilla explains it better than I can though. I know there are some people who have this issue on linux as well, but it doesn't occur on mac os, and while I originally punted on the first ticket opened as it is a 'browser' bug and kind of out of my hands. I've rethought that course, and am going to do my best to work around the issue. -Mark On May 15, 2:27 pm, Brendon Kozlowski <[email protected]> wrote: > Say what? LOL. Sorry Mark, I truly am interested to understand what > the issue was, I just don't think I really understood your > explanation. Would you be willing to explain it further? A "nope" > will suffice too, of course. :) > > On May 15, 2:21 pm, mark_story <[email protected]> wrote: > > > > > The issue with Firefox is bound to Windows only. Its an issue with > > how windows actually functions. Because the UI elements are 16bit > > they cannot exceed the pixel dimensions of the 16bit space. So > > mozilla is bound by shoddy windows widgets, and the Api was bound by > > that implementation. I'm going to be redesigning the source code > > output to fix this issue. Seeing as there is a better chance of > > glaciers to destroying my house before Microsoft fixes 16 bit api's. > > > -Mark > > > On May 15, 2:03 pm, Matt Curry <[email protected]> wrote: > > > > I had the same problem with FF cutting off the model page at line > > > 1820. Disabling Firebug for the API pages fixed it for me. > > > > -Matthttp://www.pseudocoder.com > > > > On May 15, 6:27 am, John Andersen <[email protected]> wrote: > > > > > Hi Burzum > > > > > Can you open the following location in FF 3.0.10 (which I have), as I > > > > do have the problem that the code disappears after that line! > > > > > "http://api.cakephp.org/view_source/model/#line-1820"; > > > > > Then return and tell me what you got! > > > > John > > > > > On May 15, 12:18 pm, burzum <[email protected]> wrote: > > > > > > I agree with AD7six, the tickets are bad, you don't even mention the > > > > > exact version number of the browsers. That's how i expect end users to > > > > > report a bug, not a developer. ;) I never had any problems with the > > > > > API documentation and i regularly update FF, my current version is > > > > > 3.0.10, it works also in Opera 9.64 and every version i used before. > > > > > Also the IE8 shipped with the Win7 RC does its job. I guess that you > > > > > can't see the source view is caused by a bad extension that filters or > > > > > manipulates something.- Hide quoted text - > > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
