[
https://issues.apache.org/jira/browse/TAPESTRY-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507758
]
Jesse Kuhnert commented on TAPESTRY-1560:
-----------------------------------------
When it does get released it will be available on the official
http://tapestry.apache.org/download.html page like every other release.
What I pointed you at is an early peak at us prepping the files for release and
not something the general public is expected to know about.
The page you pointed out is actually the more correct place to grab the jars
from. (ie
http://people.apache.org/repo/m2-snapshot-repository/org/apache/tapestry/ ) I
suggest you use it - as documented - next time. Obviously I know what pages
link to what and am well aware of what they contain but thanks for pointing it
out belligerently anyways. Perhaps you'd like to ask me when 4.1.2 will be
released while you're at it? d
> 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]
