simply disableFlashStorage: true solves this...
andyhot wrote:
> 100% a css issue in Opera... can you selectively disable css files in
> Safari,
> to see if that's also the case there?
>
> andyhot wrote:
>
>> Both that and the final release use dojo0.3.1
>> I can't get Safari access, but I ca
I'll see if I can spend some time on this tonight. Also, keep in mind
that it's not just the date picker icon but all On-Click events that
failed to get connected to their propper elements.
On 8/25/06, andyhot <[EMAIL PROTECTED]> wrote:
> well, using firefox and firebug, and
> http://www.opencompo
well, using firefox and firebug, and
http://www.opencomponentry.com:8080/tacos/bugs/Bug91.html
i gathered the ajax response... it looks ok, but the datepicker icon isn't
working.
Don't know if it has to do with order of execution.
I also like to do 'View generated Source' in firefox,
once when the
Any idea as to the potential cause of this bug that might help me
debug and fix myself?
On 8/25/06, andyhot <[EMAIL PROTECTED]> wrote:
> you're right...
> Just talked with Jesse and ... tacos will shortly switch to jira :)
> we can wait till then I guess!
>
> Daniel Tabuenca wrote:
> > I tried but
100% a css issue in Opera... can you selectively disable css files in
Safari,
to see if that's also the case there?
andyhot wrote:
> Both that and the final release use dojo0.3.1
> I can't get Safari access, but I can get blank pages in Opera9 :)
>
> Which means (if the problem is the same) I may
you're right...
Just talked with Jesse and ... tacos will shortly switch to jira :)
we can wait till then I guess!
Daniel Tabuenca wrote:
> I tried but the wiki tells me I don't have enoguh priviliges. I tried
> to create an account but it says I don't have priviliges for that
> either. What is th
With PartialFor and direct="ognl:true" only the first dropdown works,
just like regular For.
Interestingly, with PartialFor and direct="ognl:false" NEITHER dropdown
comes up (but the search listener gets called in both cases).
So I guess the only thing that works with both autocompleters so far i
I tried but the wiki tells me I don't have enoguh priviliges. I tried
to create an account but it says I don't have priviliges for that
either. What is the proper way of creating an account to report the
bug?
On 8/25/06, andyhot <[EMAIL PROTECTED]> wrote:
> didn't have time to enter this in...
>
I meant that it ONLY checks for PartialFor
andyhot wrote:
> Also, when our response builder tries to render a component
> with direct="ognl:true", it first checks what the containing components
> are...
> 'cause perhaps it needs to render those first...
>
> However, up to now, it also checks for P
didn't have time to enter this in...
Can you report it? Simply copy paste your (or mine) emails...
Daniel Tabuenca wrote:
> What is the new bug number for this? Where can I go to comment on the
> bug if I find new information?
>
>
> On 8/24/06, andyhot <[EMAIL PROTECTED]> wrote:
>
>> hmm, look
Also, when our response builder tries to render a component
with direct="ognl:true", it first checks what the containing components
are...
'cause perhaps it needs to render those first...
However, up to now, it also checks for PartialFor components containing your
component. I don't see why we can
What is the new bug number for this? Where can I go to comment on the
bug if I find new information?
On 8/24/06, andyhot <[EMAIL PROTECTED]> wrote:
> hmm, looks like
>
> http://tacoscomponents.jot.com/BugReporter/Bug91
>
> was for another issue, but the test to reproduce it simply demonstrates
>
Ok, I see now in the docs that the Direct service should not be used if
the Autocompleter is in a loop. So maybe the only real problem here is
that the Tapestry @FieldLabel component throws that error on every
search. I have a workaround where I am using a regular HTML
element with the @Any compon
Interesting, I have always used direct="ognl:true" on Autocompleters to
speed things up but I tried turning that off as in your example and now
both dropdowns work. But now it spits out a stack trace in the console
every time a search gets run:
"Field [EMAIL PROTECTED]/autocompleteField] has
alrea
Doesn't this work?
http://opencomponentry.com:8080/tacos/bugs/Bug58.html
It has 2 autocompleters in a loop (of 2 iterations)
Here's the source:
https://svn.sourceforge.net/svnroot/tacos/tacos-4.0/trunk/demo/docroot/WEB-INF/bugs/Bug58.html
https://svn.sourceforge.net/svnroot/tacos/tacos-4.0/trunk/
I just tried upgrading our app to Tacos 4.0 final. I’m
glad to see the new ‘parameters’ parameter for the Autocompleter, this
makes it much easier to use in a loop. The problem I’m running across now
though is that I have two Autocompleters being rendered in a loop and drop-down
values only
Both that and the final release use dojo0.3.1
I can't get Safari access, but I can get blank pages in Opera9 :)
Which means (if the problem is the same) I may be able to resolve this...
Funny thing is that it's working nicely on Konqueror...
Perhaps it's a css issue after all... in Opera when i s
FYI, this issue was also present using tacos4-beta-3-20060710-1929-lib.jar.
v.
On 8/25/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
> Ok. Has to be dojo version then.
>
>
> On 8/25/06, Viktor Szathmary <[EMAIL PROTECTED]> wrote:
> > Nope, those apps are fine. The Tacos demo isn't, and other apps
Ok. Has to be dojo version then. On 8/25/06, Viktor Szathmary <[EMAIL PROTECTED]> wrote:
Nope, those apps are fine. The Tacos demo isn't, and other apps I haveembedded Tacos4 into are also borked in Safari.
v.On 8/25/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:> Does this happen on any of these p
Nope, those apps are fine. The Tacos demo isn't, and other apps I have
embedded Tacos4 into are also borked in Safari.
v.
On 8/25/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
> Does this happen on any of these pages?
>
> http://tapestry.apache.org/tapestry4.1/demos.html
>
>
> On 8/25/06, Viktor
the workbench and timetracker demos are fine on safari. but i too get the blank page for tacos on safari 2.0.3 mac os x 10.4.5On 8/25/06, Jesse Kuhnert
<[EMAIL PROTECTED]> wrote:Does this happen on any of these pages?
http://tapestry.apache.org/tapestry4.1/demos.html
On 8/25/06,
Viktor Szathmary
Does this happen on any of these pages?http://tapestry.apache.org/tapestry4.1/demos.htmlOn 8/25/06,
Viktor Szathmary <[EMAIL PROTECTED]> wrote:
Hi,Here's a bug report - I was unable to file this on jotspot (jotspotdoesn't seem to work with safari either, and when using firefox, i gotsome access ri
Hi,
Here's a bug report - I was unable to file this on jotspot (jotspot
doesn't seem to work with safari either, and when using firefox, i got
some access rights issue - so posting it here):
Visiting any page that includes Tacos components results in a
completely blank page using the Safari brows
Very nice work. Tried the demo in the latest FireFox and these are the
errors I got
Dojo/Tabs
Tabs show up but no content. When you click on the tab the tab becomes
selected but no content shows up.
Dojo/LayoutContainer
Scrolling does not seem to work
Apart from that everything else works
24 matches
Mail list logo
