Version: 3.5.2 (using KDE 3.5.2 Level "a" , SUSE 9.2 UNSUPPORTED) Compiler: gcc version 3.3.4 (pre 3.3.5 20040809) OS: Linux (i686) release 2.6.8-24.23-default doc=document.getElementById('warning') //alert(doc.style.background) if (doc.style.background != 'transparent') doc.style.background= 'transparent'; else doc.style.visibility = 'hidden'; This does not work. I had to use 'initial initial initial transparent' in the if condition as following: if (doc.style.background != 'initial initial initial transparent') doc.style.background= 'transparent'; else doc.style.visibility = 'hidden'; and now it does OK as I like :) Ron
So you expect the initial value of background to be 'transparent'? What does other browsers return?
Created attachment 18619 [details] example using the code with the problem
I renamed the 'doc' object to 'war' and SuSE9.2 changed to Kubuntu 6.10 but it does the same. :( dsb=war.style.background alert(dsb.length); alert(dsb); /* a: on transparent button b: on scroll button c: on hide button kubuntu6.10 konqueror 3.5.5: #:len text a:00 // on transparent b:35 'initial initial initial transparent' c:35 'initial initial initial transparent' kubuntu6.10 firefox 2.0 #:len text a:00 b:36 'transparent none repeat scroll 0% 0%' c:36 'transparent none repeat scroll 0% 0%' */
I'm confused: The example in comment #2 contains "initial initial initial transparent" and acts the same way in konqueror trunk and firefox 2.0.0.12, although the texts in the dialogs are different. If I replace "initial initial initial transparent" with just "transparent", then I get different behaviour: * In konq trunk, after clicking the right-hand button twice, its text changes to "hide", and the third click on it hides the main content. * In ff, the button just stays at "transparent" (I think - the button is actually smaller than the text, so I can't read it properly). Reporter, what am I meant to be seeing here?
LOL had this weekend the same problem again. I do have some pages with a warning box on top. If the viewer is scrolling the box stay on the same place and cover partial the content. It's not nice to the viewer but he must be warned for several reasons. The first step is make it transparent but the warning with option buttons stay in place. The second step let the box scrolls away with the content covered by transparent box. The third step is he beliefs me and he can remove the warning box complete. To handle this last step I had to get the obj.style.background value with: // the doc object is the warning box doc=document.getElementById('warning') if (doc.style.background != 'transparent') /* has a color */ doc.style.background= 'transparent'; /* make transparent */ else doc.style.visibility = 'hidden'; /* and now hide it */ from an old javascripts I copied this code and it did not work with konqueror. Konqueror 3.5.2 returns for the .background property: 'initial initial initial transparent' and Firefox at that same date 2006-11-19: 'transparent none repeat scroll 0% 0%' The old script was from a browser with more intelligent behaviour, sorry. The parameters you can set with .background are all different for the atribute IE know that when transparent is given what atribute should change. In konqueror you get three 'initial' words but nowhere is told for in what these words in order stand for. is the first for background or repeat or ? You can say the meaning in order is what firefox shows but that is not through. konq set transparent as last and firefox as first. | In konq trunk, after clicking the right-hand button twice.... You should use the left button, its not a context menu. :) 1'st click) 0, '', text from transparent to scroll 2'nd click) 35, 'initial intial initial transparent', text from scroll to hide 3'th click) 35, 'initial intial initial transparent', box disapears The example does still work now with konqueror 3,5,5. The bad thing is with firefox it can't work because the result of .background differs. Firefox and konqueror claim to be webstandard, how come the differences. :) I should have used? var bg='x'+doc.style.background; if (bg.indexOf('transparent') > 0)
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!