When using onbeforeunload function, I don't want to show warning message for submit button and some other buttons also inside my form. I am checking boolean[T/F] condition to fire it. It works with IE, but it seems not checking the condition in FireFox. It is showing problem.
Can somebody help.
Thanks
I am not 100% sure I understand what you mean, but it appears you just trying to do something you shouldn't.
If I understood correctly, you are trying to use the onbeforeunload event without a warning message.
Think about it for a moment. You'll probably see that see that someone that does not have your best interest at heart could keep you at his site and make it impossible for you to leave. That's why firefox doesn't allow you to do it - and that's something to be happy with!
This technique worked for me in IE and Firefox. You aren't trying to bypass the warning message as another answer suggested, you just don't want the warning message on the buttons which makes perfect sense.
Related
This is a question with the same title as here:
VBA Active-X buttons getting bigger with every action
I guess the problem is the same.
The question is nevertheless from 2014!!! and it does not really have an answer.
In my case the buttons were NOT created programatically, but just clicking in insert activeX control, button, and then click for writing the VBA behind.
In order to better illustrate the problem I made a video with my handy:
https://www.youtube.com/watch?v=hBiu2FfRxQU
IN the video you can see how every time a button is clicked it gets bigger.
as note aside I have to say that this only happens when I connect remotely with my computer via a think client. Nevertheless both screens are the same (i.e. have the same resolution).
This is of course very annoying because it makes almost impossible to use home working since connecting to my excel at work makes all the buttons go crazy in size.
As #TimStack and #jvdv has pointed out this is a known issue of Microsoft, i.e. a BUG, there since many years.
Hence there is no solution but workarounds.
So stay away from controlX if you don't want to get surprises.
I had faced this issue today itself. And found very strange solution to this problem.
I just tried to resize the button where I was facing the issue and it was solved.
Hope this works with you.
I've had this issue several times and usually I can just shut down the program and restart it. But this time I have a bunch of windows open and I don't want to restart Dreamweaver.
My problem is that Dreamweaver brought up a code hint, but the code hint box now won't go away. It just sits there floating in the middle of the page. It doesn't matter if I click to Preview or any other tab in Dreamweaver, it still just sits on top of everything.
I'm working on a Mac, Dreamweaver CC (cloud, fully updated). Anyone else have this problem???
This has been a HUGE PAIN for me as well! You can make the code hint disappear though by finishing out an element that is in the code hint box. For instance if the code hint box appears and you can see class in the drop down... create a <div class="xyz"> real quick and the code hit box will dissipate after you close the quotes on the class because you used an element in that box. As to why this continually happens on the Mac version I have no idea, but I hope they fix it soon!
It's a known bug since years as you can read here: https://forums.adobe.com/message/7745689
Someone suggests as a workaround to set the Coding Hint delay to 0 (as said here: https://forums.adobe.com/message/7745689#7745689) but for me, in Dreamweaver CC 2015 Windows fully updated via cloud app, this bug still occurs while I code JS files.
Awaiting for a final fix, I hope this suggestion can be useful for you on Mac. :)
Recently I decided to write a very simple Google Chrome extension. All it's going to do is to hide some DOM-elements from the web-page using JavaScript when user presses the extension's button.
Since I knew nothing about Chrome extensions, I started reading tutorials, and I came across this Google's sample: A browser action with no icon that makes the page red
This sample is really close to what I want to make. The problem is that I can't make it work. Whenever I load the extension in Chrome, I can see the button of this extension, but when I press it - nothing happens. Sample doesn't work, probably I should know something I don't know yet.
And before you started asking me:
Yes, I tried restarting the browser;
I use the newest version of Chrome.
Thanks for help.
If you open up the sample zip... find backgrond.js... edit.
Find the line that says:
null, {code:"document.body.style.background='red !important'"});
and remove the "!important". so it should read:
null, {code:"document.body.style.background='red'"});
That is it. just save and reload the extension, should work (unless the page has an !important flag set to the background).
I am afraid I don't know why the "!important" tag doesn't work but I have never been able to get it to work in an extension. Hopefully someone else here will be able to give an explanation and maybe a work around.
I think I can help bring some clarification to the "!important" override attribute causing the extension to break. Though I am not 100% I believe that this attribute is not allowed for issues involving security complications. I have a link to another SO thread that may help clarify this as well.
My CSS is not getting injected through my content script
I'm assuming from reading this article that you must either use the !important override when content scripts specified in the manifest file. Otherwise if the css is being injected !important is not required. Again not 100% on this.
Do anyone know why FocusOut event is not working on linux?
I have 1 enabled textbox and 3 disabled combobox.
I bind the textbox with FocusOut event where it will call a proc that enables or disables the 3 combobox.
It works perfectly on Windows. However, it doesn't seem to trigger the FocusOut event when this action is done on Linux. One weird thing is that if I click on buttons, FocusOut event seems to be triggered.
Could it be because my combobox are disabled?
But why does it work on Windows?
I really hope someone can help me please.
Thanks in advance.
I have observed in the past that some window managers steal the focus temporarily from Tk on each button click before setting it back; I suspect that this has to do with the way that key event handling works, but I am unable to check at the moment (due to being on OSX, where things are different). Because of the complexities involved, I'd suggest that if you bind to <FocusOut>, you should also check whether you get a <FocusIn> event shortly after; a little extra delay (e.g., 0.1s) before doing the update of the buttons' disabled status will not hurt.
Or you could hang the code to do the disabling off the entry widget validation engine, perhaps like this:
.e configure -validation focusout -validatecommand doButtonEnableDisable
The validation interface is the same for both the old style entry and the new style ttk::entry widgets. It's also supported by spinboxes. Just be aware that you need to return a boolean true from doButtonEnableDisable or you'll reject the change to the entry, and you should take care to ensure that your code does not produce an error or it will disable itself; the docs list the things to watch out for.
when checking the PJAX live demo - http://padrino-pjax.heroku.com/
The history (back button) don't work!
I can not find any documentation about it, it seems useless if it craps the history functionality.
Can anyone tell me if this is how it should be?
What I did to check was go through the 3 links (don't forget to check the "use PJAX" box)
then clicking back and seeing it went to the first one instead of the second.
thank you
it's works fine. you need to enable it first via checkbox ;)
I suggest to check the original code, what you posted is a porting of the original demo founded here: https://github.com/defunkt/jquery-pjax/tree/heroku