On Sun, May 17, 2009 at 8:59 PM, Mr-Yellow wrote:
>
> They might be, I'm an asshole for sure :-)
No need to explain. We get it.
> Thing is I wasn't the person who decided I wanted to work for fame and
> recognition. I'm on the cash side of things rather then the open-
> source side of things, I
@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 ti
They might be, I'm an asshole for sure :-)
Thing is I wasn't the person who decided I wanted to work for fame and
recognition. I'm on the cash side of things rather then the open-
source side of things, I realise open source people do it for
different reasons, but really that's their problem. I c
On May 17, 12:31 pm, Mr-Yellow 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
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 ca
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 no
I'm seeing it in FF3.0.10/linux (I guess that's what I get for being a
linux fan-boy)
On Fri, May 15, 2009 at 2:21 PM, mark_story 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 exce
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 wrote:
> The issue with Firefox is
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 goin
I'm offended that you think that's how I would respond to the tickets.
Firstly you put them in the wrong place, secondly, they've been fixed.
So there.
-Mark
On May 14, 11:58 pm, Mr-Yellow wrote:
> Anyone want to place bets on how long it is before the tickets are
> deleted and ignored?
>
> -B
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.
-Matt
http://www.pseudocoder.com
On May 15, 6:27 am, John Andersen wrote:
> Hi Burzum
>
> Can you open the following location in FF 3.0.10 (which I have), as I
> do have
On Thu, May 14, 2009 at 11:49 PM, Mr-Yellow wrote:
>
> Yeah guys dropping IE is the best bet. Seeing FF doesn't work either.
>
> What I should really do is stop testing in the browser that the VAST
> majority of my surfers use.
>
> Take your browser fanboy crap elsewhere, I just want the document
It does not fail for me. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-
US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729)
As suggested, perhaps it's caused by a rogue extension?
On May 15, 7:29 am, "oliver.pra...@googlemail.com"
wrote:
> "http://api.cakephp.org/view_source/mod
"http://api.cakephp.org/view_source/model/#line-1820"; Fails by me as
stated
Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.0.10) Gecko/
2009042316 Firefox/3.0.10
Oliver
On May 15, 12:27 pm, John Andersen wrote:
> Hi Burzum
>
> Can you open the following location in FF 3.0.10 (which I ha
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 wrote:
> I agree with
LOL IE support.
--~--~-~--~~~---~--~~
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...@googl
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 i
On May 15, 8:56 am, AD7six wrote:
> On May 15, 5:58 am, Mr-Yellow wrote:
>
> > Anyone want to place bets on how long it is before the tickets are
> > deleted and ignored?
>
> How about we place bets on how long until:
>
> 1) You create them in the right place
> 2) You submit patches
Btw. work
On May 15, 5:58 am, Mr-Yellow wrote:
> Anyone want to place bets on how long it is before the tickets are
> deleted and ignored?
How about we place bets on how long until:
1) You create them in the right place
2) You submit patches
AD
--~--~-~--~~~---~--~~
You
Anyone want to place bets on how long it is before the tickets are
deleted and ignored?
-Ben
On May 15, 1:57 pm, Mr-Yellow wrote:
> New Tickets:
>
> API Documentation fails in IEhttps://trac.cakephp.org/ticket/6376
>
> API Documentation fails in FFhttps://trac.cakephp.org/ticket/6377
>
> -Ben
New Tickets:
API Documentation fails in IE
https://trac.cakephp.org/ticket/6376
API Documentation fails in FF
https://trac.cakephp.org/ticket/6377
-Ben
On May 15, 1:49 pm, Mr-Yellow wrote:
> Yeah guys dropping IE is the best bet. Seeing FF doesn't work either.
>
> What I should really do is
btw there were tickets for this but I guess they were deleted months
back when this error was first reported.
-Ben
On May 15, 1:49 pm, Mr-Yellow wrote:
> Yeah guys dropping IE is the best bet. Seeing FF doesn't work either.
>
> What I should really do is stop testing in the browser that the VA
Yeah guys dropping IE is the best bet. Seeing FF doesn't work either.
What I should really do is stop testing in the browser that the VAST
majority of my surfers use.
Take your browser fanboy crap elsewhere, I just want the documentation
fixed so it can be viewed in a browser, any one will do.
I've also noticed problems with the source view in FF where it's
impossible to scroll (using the scrollbar, mousewheel, or keyboard).
It seems a bit like a Heisenbug, though. I've had it happen when
viewing a particular method, then it won't happen another time.
Anyway, the quick solution is to di
James, that's a poor response for IE. However, what should be said
instead would be:
If you have some possible fixes for the CSS and IE, you can try and
submit a ticket at the API Generator's project page on TheChaw(.com).
On May 13, 11:13 am, James K wrote:
> I have no problems viewing the API
I have no problems viewing the API in Firefox 3.5 or Firefox 2.x,
Chrome, or Opera 9.x under Windows.
As for IE stop using IE?
- James
On May 13, 12:54 am, Mr-Yellow wrote:
> For months now the API documentation site has not been accessible to
> IE.
>
> The search button is stretched over
For months now the API documentation site has not been accessible to
IE.
The search button is stretched over the navigation area.
The site is also not usable in FF as the source view loads in a div
with hidden overflow which bugs.
Only way to use the site is o first navigate using FF then switc
27 matches
Mail list logo
