I understood you perfectly well. :)
The overlap is because it's dynamically displaying the exception page within
a dialog client side widget because the exception happened during an XHR
request. If you copy and paste the css rules I gave you into either a .css
file you include in your app or directly in your page within <style></style>
tags you'll be able to read the messages more clearly.
On 5/30/07, Heping Zhang <[EMAIL PROTECTED]> wrote:
Oh thank you. But maybe I don't express it correctly. My page is the left
and when error happened Tapestry will generate a page like the right. When
I
don't use ajax, it works well, first the original page and then error
happened and it turns to the right. But when using ajax, or more exactly,
dojo, the two pages overlaped. Just image the right moved horizontally to
left and laps over the original page. That's what I see in firefox. The
first page doesn't disappear when the second appears. So they overlap and
that makes me cannot read the error message. That's my problem. When I ask
I
thought its a common problem and you can understand what I say easily. But
it seems only me encounter this problem. So, if there is no solution, on
my,
left it to me. There is still a solution. I can read the source file of
the
html page and get the imformation I need. But still thank you!
___________________________
| error message such |
_______________ | as Object $BaseComponent |
| | | [Home/$Border] does not |
| the page | | implement a listener |
| when errors | | method named 'showDialog' |
| happened. | | blah blah... |
|_____________| | blah... |
| blah...
|
| blah...
|
|_________________________|
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
