Slashdot Mirror


Konqueror's Javascript Continues To Improve

ElitusPrime writes "Konq's Javascript support may have been regarded as weak in the past, but 3.0 is a huge improvement. As an example, DHTML Lab has just released a Konqurer supported version of their popular HierMenus product. These cross-browser, backwards compatible pop-up menus are very complex, using all sorts of Javascript and DHTML tricks. Konq now supports them out of the box!"

3 of 173 comments (clear)

  1. Re:Why is it every time I use KDE by foonf · · Score: 3, Informative
    within ten minutes the font has changed itself to arioso system wide?


    When the font configuration data gets reset, or it can't find the default font (such as, if you are using bitmap helvetica as your font (which is the default), but using Xft rendering which does not support bitmap fonts), it goes to whatever is alphabetically first among the fonts it is aware of. Sometimes it ends up being Arial, which is ok (although its usually the wrong size), on my computer it typically chooses an absolutely horrid looking font called "Agate".
    --

    "(Man) tries to live his own life as if he were telling a story. But you have to choose: live or tell." --Sartre
  2. Ultimate Dropdown Menu by KodaK · · Score: 4, Informative


    If anyone's interested: www.brothercake.com has a JS menu, UDM, that works very well cross-browser.

    And it's free-as-in-the-guy-who-wrote-it-says-so. Gimme-credit-ware.

    I use it on the main page and the web-store for navigation. It can be slow on some browsers, but it's actively developed and gets better every day. I just checked it with konq 2.2.1 and Opera 5.0, no problems. In mozilla it's slow as hell, but I haven't tried moz 1.0 yet.

    --
    --J(K) DOS is like Unix in exactly the same way that a pinto is like an aircraft carrier.
  3. Re:Not stoned by The+Cat · · Score: 3, Informative

    DHTML menus depend on no events but the onmouseover and onmouseout events, which are the EXACT same in every popular browser since Netscae 3.0

    Sure, as long as they are registered in the HTML. But if you try to register them in Javascript, you have the W3C "AddEventListener" method, and then you have the MS "AttachEvent" method.

    There is no reason you should have empty divs in your code to begin with. Why are they there?

    Who cares? The standard supports it, it shouldn't be broken, and it worked in IE5 and IE5.5 but broke in IE6. Far as I'm concerned, if it works in Mozilla it should work everywhere else.

    I have no idea what bug this is. Vertical scrollbar bug?

    Use window.open to create a pop-up. Set scrollbars=no. Create a background image that is the same size as the window client area. In IE there will be an empty, useless vertical scrollbar on the right side. The only way to get rid of it is to set scroll="no" in the element (a mind-bogglingly non-standard field), BUT then it leaves a fat hole in the page where the scroll bar used to be, so you have to set "margin:0" in the style sheet as well.

    That bug took weeks to research and fix.

    It doesn't affect DHTML menus directly, but it is an example of why it is such a gigantic pain to do DHTML anything, and why web sites cannot get past HTML 2 after four generations of browsers.

    Hopefully Mozilla will fix this.