Bug 104317 - [site-issue] Different handling of Javascripts if javascript is enabled globally or if it is enabled site based or adhoc through menu
Summary: [site-issue] Different handling of Javascripts if javascript is enabled globa...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: konqueror
Classification: Applications
Component: khtml ecma (show other bugs)
Version: 3.4
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-21 14:19 UTC by Ingar Pareliussen
Modified: 2012-06-18 14:12 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ingar Pareliussen 2005-04-21 14:20:05 UTC
Version:            (using KDE KDE 3.4.0)
Installed from:    SuSE RPMs
OS:                Linux

When visiting the site http://ask.bibsys.no the search facilities works if you enable javascript globally. However, if you enable Javascript either from the Tool-menu-> HTML-setting->enable javascript or allowing bibsys.no to use javascript it does not work.

It  should be said, I don know if it is important, that the site does not report that javascript is disabled even if it is not turned on globally, which it does if you turn Javascript off completely.
Comment 1 Maksim Orlovich 2005-04-22 04:03:04 UTC
What exactly doesn't work?
Comment 2 Ingar Pareliussen 2005-04-22 08:49:52 UTC
When you try to specify which databases you want to search the submit button acts like a reset button. e.g. The page is reloaded as without your changes, when it should have taken you to the search page. 

If you go to the search page manually and type in the book you want, you get an empty result even though it is in the database.

Btw. a friend tells me that it works in his kde 3.3 on Suse 9.2. While for me on Suse 9.2 with 3.4.0 it does not. 
Comment 3 illogic-al 2007-01-06 23:46:37 UTC
Works in 3.5.5 
Comment 4 Stefan Monov 2007-01-06 23:55:32 UTC
KDE 3.5.5 here.

With JS globally enabled:
I click "Search selected sources". Field appears. I enter "art". I get results.

With JS globally disabled but enabled through menu:
I click "Search selected sources". Page is just rerendered.

Ingar, this is exactly what you describe in your report, so I'm confirming it.
But in comment #2 you give a different description of "does not work". Can you please elaborate?
Comment 5 Jo Øiongen 2007-01-07 00:04:20 UTC
Can not reproduce... Running 3.5.5 But I found a way to crash Konqueror... Filing a new bug:(

Cheers Jo
Comment 6 Ingar Pareliussen 2007-01-07 09:27:51 UTC
Installed Suse 10.2 yesterday with 3.5.5 and I still get the difference in behavior if you enable Java Script globally or locally. 

stefan: I am certain that the second way I describe in #2 is the same bug. To elaborate a bit more: Go to ask.bibsys.no without javascript enabled globally and instead of selecting a search source, press the search button on the page to take you directly to the search field. If you then enter 'art' (or something else) you always get an empty set in return.

I guess we need to know if this is a Suse-bug or not. I know that in my experience this has not worked for me on Suse 9.2, 9.3, 10.0 and 10.2 with KDE 3.4.0-3.5.5.

Just as I was going to submit this comment I enabled debugging and report-error in JS in konqi. I get the error:
http://ask.bibsys.no{snip} line 293: 
ReferenceError: Can't find variable: submitForm2
when I press "Search selected sources".
When I turn on JS globally and reload the page I do not get this error.
Comment 7 George Goldberg 2008-04-20 13:46:24 UTC
In 3.5.9, If I disable javascript globally and then use the tools menu to re-enable it for that page, it still doesn't work. However if I add the site to the list of sites to permit javascript on, it does work.

In SVN trunk r795406, the tools menu is not there, and by adding the site to the allow list, it works correctly.
Comment 8 Myriam Schweingruber 2012-06-18 14:12:26 UTC
Message from the Bugsquad and Konqueror teams:
This bug is closed as outdated, as we do not have the manpower to maintain the KDE3 version anymore.
If you still can reproduce this issue with Konqueror 4.8.4 or later, please open a new report.
Thank you for your understanding.