[ 
https://issues.apache.org/jira/browse/TAPESTRY-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507747
 ] 

Jesse Kuhnert commented on TAPESTRY-1560:
-----------------------------------------

I'm not ignoring it, it just isn't relevant to me as I'm using Tapestry 4.1.2.  
The jars are available and location of them documented on the web site.   

So, don't know what to say really.  If you want it resolved in 4.1.2 but aren't 
willing to test it against 4.1.2 then I'd say your chances are looking rather 
grim.  If it really was critical you'd be trying harder.  The 4.1.2 release is 
as good as done now anyways so at the very least you can find out whether or 
not you'll be disappointed:

http://people.apache.org/~jkuhnert/tapestry_releases/

> Dojo Dialog initialilsation renders dialog inline before hiding it in firefox
> -----------------------------------------------------------------------------
>
>                 Key: TAPESTRY-1560
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1560
>             Project: Tapestry
>          Issue Type: Bug
>          Components: XHR/dhtml/Ajax
>    Affects Versions: 4.1.1
>         Environment: Tapestry 4.1.1
> Firefox 2.0.0.4
>            Reporter: Paul Stanton
>
> I have 2 dojo dialogs, hidden by default which have been working fine.
> <div jwcid="[EMAIL PROTECTED]" hidden="ognl:true">dialog</div>
> I've now added a component to the page which delays the load time for the 
> page somewhat and in firefox causes a funny render issue for the dialogs.
> The dialog's content is momentarily displayed (inline) at the bottom of my 
> page, and the page's background colour is the transparent grey of the dialog.
> It seems to be only for the short period between when the page is rendered 
> and onload event is triggered. when the page is finished loading it goes back 
> to normal and everything functions fine.
> If I set the style of the dialog to display:none; the dialog does not behave 
> properly, it does not display when dojo.html.show is called on it. This is 
> because dojo caches the initial display setting when it first hides the 
> component.
> I've looked at the code that dojo runs in the onload event hander:
> tapestry.widget.synchronizeWidgetState("myDialog", "Dialog", 
> {"bgColor":"black","bgOpacity":0.4000000059604645}, false);
> dojo.widget.byId("myDialog").hide();}); 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to