If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
-
2005-08-08
assigned_to: nobody --> warp9pnt9
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
-
2005-08-08
Logged In: YES
user_id=706287
Ok, in Mozilla Firefox 1.0.6, I get no JavaScript errors,
but I do see the GUI error. In IE6, I get two errors,
this.elm.client(Width|Height) is null or not an object. But
it seems to work in IE6? I mean, I click on "SOME TEXT
LOGNER" and I can still scroll in the ViewPane. This might
be related to something I saw a long time ago. Maybe it was
never fixed. I'll look into it. If someone else fixes it
first, by all means submit a patch and reference this bug.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
-
2005-08-08
labels: --> DynAPI 3 API
milestone: --> Verified
priority: 5 --> 6
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
-
2005-08-08
priority: 6 --> 7
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
-
2005-08-08
Logged In: YES
user_id=706287
Hmm, a note about IE6, the script error seems to be
indirectly caused by a browser setting. Checking the
checkbox makes the IE6 specific error go away. But this bug
still applies to Mozilla.
location in 'dynapi/examples/'
Logged In: YES
user_id=706287
Ok, in Mozilla Firefox 1.0.6, I get no JavaScript errors,
but I do see the GUI error. In IE6, I get two errors,
this.elm.client(Width|Height) is null or not an object. But
it seems to work in IE6? I mean, I click on "SOME TEXT
LOGNER" and I can still scroll in the ViewPane. This might
be related to something I saw a long time ago. Maybe it was
never fixed. I'll look into it. If someone else fixes it
first, by all means submit a patch and reference this bug.
Logged In: YES
user_id=706287
Hmm, a note about IE6, the script error seems to be
indirectly caused by a browser setting. Checking the
checkbox makes the IE6 specific error go away. But this bug
still applies to Mozilla.
I opened a low priority bug about this.
https://sourceforge.net/tracker/index.php?func=detail&aid=1254453&group_id=5757&atid=105757