The JavaScript alert box is appearing without close mark on top right side nor its showing any alert symbol as shown below.
The same in IE8 works fine
Both are running on Windows 7 platform
What you're seeing is how Firefox 4 renders an alert box. They've gone for a minimalist look.
There's nothing you can do about it -- how the alert() function renders its popup is entirely at the discression of the browser, and they all do it slightly differently.
If you want control over how the box looks, you will need to write your own in Javascript, or use one of the hundreds of Javascript and JQuery examples written by other people who have already found they need more flexibility than the standard alert box can give them.
[EDIT]
Here's a blog post where the change to how the alert box works is discussed: http://www.derekallard.com/blog/post/firefox-4-alert-boxes/
There's actually a lot more that's changed than just how it looks; it actually works quite differently too in FF4.
Related
I'm doing my first bit of coding in school, making a simple website. I code in Visual Studio Code and I'm using a mouseevent for pictures. I want the picture to change into another picture and then change back to the original pic when the mouse is hovering over it.
I've tried multiple different ways of doing this, including simple functions and more complex ones. All working perfectly on my live server version of the site. But as soon as I launch the site through Netlify, making it live, the mouse hover function ceases to work.
This is the current way I'm doing it, and as I said, works perfectly in VS Code:
<img src="assets/GrasshopperPapaya.jpg" height="550" width="700" onmouseover="this.src='assets/onionized-jungle-imagen.png'" onmouseout="this.src='assets/GrasshopperPapaya.jpg'"/>
I'm having the same problem using onmouseover and Netlify (while changing menu pictures when mouse moves over menu itens).
I don't know if that couldn't be a browser issue. On this case the problem occurs using onmouseover, but only on Chrome.
Please, let me know if you find an answer.
I need a little orientation regarding Google Chrome debugger.
My application works only in Google Chrome because of well HTML5 support.
How can you pause on every single error/exception detected?
The source of this question it's the fact I'm doing a simple form submit with some Javascript validations.
On clicking the submit button I can see an error appearing in my Dev Tools Errors Frame, but it switch immediately to my PHP called on submit still in development, switching the page and therefore I can't read the error.
I've tried setting breakpoints and I've clicked on that pause on exceptions button, but it's not helping me, I'm doing something wrong.
I do not know completely how to use the debugger.
Have you considered trying to put a break point in a handler function for the window.onSubmit event?
Maybe something like this for jquery:
http://jsfiddle.net/7UZsk/27/
$(window).bind('submit',function(){
alert("submitting");
});
This is the actual DOM event reference:
https://developer.mozilla.org/en/DOM/window.onsubmit
I have C# MVC web app that has some textboxes that in IE9 you can enter in text, but you can't highlight via the mouse or via holding shift and the arrow keys.
I've looked around on the web and i've found other people experiencing this, with no solution.
One site i found claimed it was an issue with IE9 on pages that make multiple AJAX calls, which my site has but, removing AJAX really isn't a solution.
Is there a way via code or via settings in IE9 so that users can highlight text in a textbox? Or is this an outstanding bug in IE9?
Edit:
The website works perfectly fine in chrome
Turns out it was a rogue jquery statement that was
(.someClass).disableSelected()
that was disabling selection on every single textbox in my site. The kicker being that IE and Chrome handled it one way and Firefox a different way making it seem like a different bug
I had the same issue.
Select Tools on the IE bar / F12 developer tools. under the tab ( Document Mode IE9 standards ) check marked Alt+9. Closed the developer box. Closed IE9 opened it back up and everything worked as it should.
Hope this helps.
You know how sometimes you are on a good site and you click a button (like to submit a form) and the form doesn't go away, instead, the foreground becomes transparent and it contains a message of some kind, or another page. The message is at the forefront but the previous page is still mostly visible behind it - how do they do that? I'm assuming it's an Ajax-esque trick.
This is called a light box modal. There are quite a few JS plugins that can do this including Lightbox and the JQuery UI Dialog to name a couple. I just recently started using Fancybox and have been very impressed with its speed and configurability.
Here is a pretty good (not all inclusive) list of them:
http://spoonfedproject.com/jquery/extensive-list-of-jquery-lightbox-modal-plugins/
One way is to use GreyBox. I think this similar to the effect that you're talking about.
I have a dot net nuke site that I have written a custom module for. It a form that users fill out to submit information - no big deal.
On the form, I use the Ajax and the Ajaxoolkit for validation, and a calendar popup. I enable/disable controls based on form data.
Everthing works well in every browser/OS combo that I have tested EXCEPT IE7/Vista.
The page renders with most of the lables and conrols invisible. The controls are there and you can even enter data, you just can see them.
Here is a link: http://www.gpusbc.com/test/tabid/76/Default.aspx
I develop on a Win XP machine with IE7 and FireFox and there are no problems.
FireFox on Vista has no problems.
FYI this doesn't work in IE8 on Vista in regular or in compatiblity mode. This is incredibly weird because the controls are there you can click in them but your textboxes for example if you type you don't see the data.
What I've found is that if you remove the float:left style which is inherited from the .aaInput class that all of your inputs become visible. I also removed your display of
block. Do this on both the labels and your inputs and you should be good.
I tested this with IE8's developer tools in both IE8 mode and compatibility mode.