I found myself today and for all I know they don't know about it, so I should probably report it to them, right?
Just didn't know how to do it the right way since I started up in a Tacos component problem witch ended up in a dojo bug.
On 5/1/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Well, every once in a while Jesse updates our
dojo package with the latest from their svn - so I guess
this is gonna get resolved when the update hapens.
In general, you'll be ok if you use either dojo from their svn
or from ours. What could be problematic is using tacos with
earlier dojo releases (even 0.22)
From Pedro Viegas <[EMAIL PROTECTED]>:
> Hi there.
> Been digging in the Editor component.
> I noticed that it didn't render the popup color editors correctly when the
> page needed to scroll.
> If a page fitted in the container space, all OK, if not then the coordinates
> for the popups would always be relatively to the page size and not the
> client visible area.
>
> I investigated the dojo source to see where the problem came from and saw
> that it was due to the following:
>
> In dojo's ColorPalette.js the...
>
> showDialog: function (e) {
> dojo.widget.html.ToolbarColorDialog.superclass.showDialog.call(this,
> e);
> var x = dojo.html.getAbsoluteX(this.domNode);
> var y = dojo.html.getAbsoluteY (this.domNode) +
> dojo.html.getInnerHeight(this.domNode);
> this.dialog.showAt(x, y);
> },
>
> ...is the code that activates the popup color dialog.
> The dojo.html.getAbsoluteX and dojo.html.getAbsoluteY are the ones that
> calculate the coordinates, but they are not instructed to take into account
> the scroll feature.
> The code should be:
>
> showDialog: function (e) {
> dojo.widget.html.ToolbarColorDialog.superclass.showDialog.call(this,
> e);
> var x = dojo.html.getAbsoluteX(this.domNode, true);
> var y = dojo.html.getAbsoluteY(this.domNode , true) +
> dojo.html.getInnerHeight(this.domNode);
> this.dialog.showAt(x, y);
> },
>
> ...and it works perfectly.
>
> Since Tacos does not use the latest dojo package, I thought I should post
> this here.
> What should I do with this info? Have you allready noticed this? Will you
> pick it up from here?
>
> I created a workaround in my own Editor component since I wanted a normal
> input like component and not an AJAX listener based one, but the problem
> affects both implementations.
>
> Regards,
>
>
> --
> Pedro Viegas
>
--
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Tacos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tacos-devel
--
Pedro Viegas
