@mryellow: Closed without a fix? If that's so, then what are these, exactly?
fix 1: http://thechaw.com/api_generator/commits/view/192582d9a64ff881610b2326d2ba3ad3f3f56d39 fix 2: http://thechaw.com/api_generator/commits/view/58d31c777ef7834158d38a1fedc44207878420db If you'll take note of the timestamps, the issues that you flagged were fixed within a matter of hours of you posting them (a full two *days* ago, might I add), and markstory's comment clearly indicates that "This has been fixed in the head branch and will be updated soon". Now, what part of that is ambiguous? The part about "fixed", or the part about "will be updated soon"? If you had any doubts as to the veracity of his statement, it would have taken you all of 35 seconds to saunter over to the api project page http://thechaw.com/api_generator (which markstory also mentioned in his first response to your ticket) and see that the project timeline clearly indicated that the two issues you noticed had been addressed. Just because you could not see them on the live server does not immediately mean that your tickets were disregarded; we have procedures for deploying code to production servers like every one else. Thanks for filing those tickets, but next time you can keep the attitude to yourself. -jperras. http://nerderati.com/open-source-is-not-a-democracy On May 17, 6:31 am, Mr-Yellow <meisteryel...@gmail.com> wrote: > Just remove the overflow attribute from the CSS and the window will no > longer have a hidden overflow or scrollbar and thus will work. > The bug is in your CSS not in the api documentation software. > > So the tickets are closed....... I guess by closing the tickets that > makes your site work. > > Look I can get around this by using 2 browsers, just thought you'd > like to improve your site for other visitors, I don't care either way. > > So...... I'm not going to chase this around to other software vendors > posting the bugs in the "proper" places. > > You have a problem with your site, I wrongly assumed you'd like to fix > it. > > Continue to drive potential users away with a site that doesn't work, > it doesn't concern me in the slightest if you don't see that as an > issue. > > -Ben > > On May 17, 6:43 am, mark_story <mark.st...@gmail.com> wrote: > > > 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 <brendon...@hotmail.com> 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 <mark.st...@gmail.com> 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 <m...@mcurry.net> 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 <j.andersen...@gmail.com> 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 <bur...@doomzone.de> 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 cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
