Hey it's back! Thanks Jesse.
J
On 6-Jun-07, at 6:58 PM, Jesse Kuhnert wrote:
Never mind I'm a liar.....Guess I broke it the other day with a
different
change. Is fixed now and will be deployed whenever I run out of
bug fixing
steam.
On 6/6/07, Julian Wood <[EMAIL PROTECTED]> wrote:
Hmm, well I removed all my css, and it still happens. Then I removed
all my own Dialog components, and it is still wonky. I'll have to try
making a tiny testcase to see what is really going on, I think.
I only see the dojoDialog class applied to the dom node for the
dialog itself, not for the underlay (it gets dialogUnderlay), if
that's any help to you.
Thanks,
J
On 6-Jun-07, at 4:43 PM, Jesse Kuhnert wrote:
> I've been getting nice orange dialog exceptions still. Got a few
> today as
> a matter of fact. :)
>
> Do you think it's possible someone changed a style rule somewhere
> else in
> your project? There has been something fishy happening with
dialogs in
> general as I've been seeing this weird "dojoDialog" css class
> applied to the
> rendered widget dom node of dialog underlays and I'm pretty damn
> sure that
> wasn't happening before.
>
> I'm assuming it is something related to the recent 0.4.3 dojo
version
> upgrade but haven't tried to track down the root of the problem
yet.
>
> On 6/6/07, Julian Wood <[EMAIL PROTECTED]> wrote:
>>
>> For a while any exception you got back from an async request would
>> fade out the page, and then overlay it with the normal tapestry
blue
>> and yellow. The problem was that the transparent overlay was
>> impossible to read against the background of your web page. The
next
>> problem is that it was impossible to scroll to the top of the
error
>> (the stack trace moves with the scroll). Then after a while we
got a
>> nice orange dojo dialog box in the middle of the page which was
quite
>> useful. But about a week ago or so it changed back to the original
>> (this is the tap 4.1.2 snapshot timeline I'm describing). I
figured
>> it would probably change again, but it hasn't. Am I the only
one who
>> gets this exception display? Or does everyone go roll their own
>> straight away? This is FF2, btw.
>>
>> Thanks,
>>
--
Julian Wood <[EMAIL PROTECTED]>
Software Engineer
Teaching & Learning Centre
University of Calgary
http://tlc.ucalgary.ca
