i'm currently developing a web application with the goal, that
everything should work in as many browsers as possible. im using
prototype and the first barrier is IE (as expected). The problem ist
the following:
...
scroll = document.viewport.getScrollOffsets();
...
throws: "Object does not support this method"
another problem is that:
...
e.up(1).getElementsBySelector('li.menu').each(function(i)
{i.removeClassName('active');});
...
doesn't work, but:
Element.up(e, 1).getElementsBySelector('li.menu').each(function(i)
{i.removeClassName('active');});
works fine...
As usual everthing works fine in firefox and other "better" browsers.
Can anybody give me a hint?
Regards
Daniel
on 2008-06-13 16:46
on 2008-06-13 16:59
You have an element that isn't extended. Wrap your e element in a $(): $(e).up(1).... On Fri, Jun 13, 2008 at 9:46 AM, danielMitD@googlemail.com < danielMitD@googlemail.com> wrote: > {i.removeClassName('active');}); > > works fine... -- Science answers questions; philosophy questions answers.
on 2008-06-13 19:05
Besides what Fred said, #getElementsBySelector has been deprecated -
use #select instead.
$(element).up(1).select('li.menu').invoke('removeClassName',
'active');
- kangax
On Jun 13, 10:46 am, "danielM...@googlemail.com"
on 2008-06-16 09:50
thanks for quick response, after extending the element everything works. But why does the viewport function not work?
on 2008-06-16 09:58
> But why does the viewport function not work?
Usually this is because you're trying to use it before Prototype is
loaded or before the DOM is ready. Can you post a trimmed-down
example demonstrating the problem?
--
T.J. Crowder
tj / crowder software / com
On Jun 16, 8:49 am, "danielM...@googlemail.com"
on 2008-06-16 10:46
unfortunately its an intranet application and i can not post an example.. i tested if the function exists by using: alert(document.viewport.getScrollOffsets); and the function would be alerted as seen in prototype.js and more confusing is that the getDimensions() method would be called without any error just a line before getScrollOffsets(). prototype is the first js file that is been loaded: <script type="text/javascript" src="/scripts/prototype.js"></script> <script type="text/javascript" src="/scripts/global.js"></script> <script type="text/javascript" src="/scripts/subwindow.js"></script> <script type="text/javascript" src="/scripts/actions.js"></script> and the problem lines are located in subwindow.js Regards Daniel
on 2008-06-16 18:00
Hi, > unfortunately its an intranet application and i can not post an > example.. That shoudln't prevent your creating a stripped-down example demonstrating the problem; we don't need to see your app, just something showing the problem you're having. I'm suggesting this for two reasons: 1. Usually, if you go through the steps necessary to create a simple test case, you find the problem. :-) 2. If you don't find the problem, you can post your code so folks can help you out. For me, easily 75% of the time, I find my own answer at Step #1 and don't have to move on to Step #2. FWIW. -- T.J. Crowder tj / crowder software / com On Jun 16, 9:45 am, "danielM...@googlemail.com"
on 2008-06-17 08:37
okay i understand thats hard to find a error if theres no example other problematic code. but the problem is that there are to many conditions to make a small example. i checked the function it self, and as you mentioned above the problem seems to be that the document is not loaded 100%, even if the browser says its done. i found a workaround and maybe i'll find the problem it self too. thanks for helping regards daniel