I have a parent page that opens a popup (chat) i wont that where someone send a msg to a user the popup to get focused.
I have a function on popup window that runs everytime a user get msg I put "self.focus()" on that function and this work fine in IE but not in Firefox.
I have a scrolling div that I am changing text color and background color on a mouse over of a marker on a map. I also want the div with the proper ID to come to the viewable area of the scrolling div when I mouse over the marker on the map. Code:
I have a problem where there is an onBlur check for a valid entry. The javascript checks the entry and if it is incorrect it does an alert and then puts the focus back onto the incorrect field, so valid data has to be entered.
This is a generic function so it uses 'this' - onBlur="chkMonthDob(this);"
The function then checks it and puts the focus back on 'this' if it is wrong. This all works fine in IE but in Firefox it does not put the focus back.
Using the Firefox getaround :- setTimeout("document.orgsp.d1_org_dob_mth.focus()", 1); works, however, when it is called with 'this' as a parameter you don't know what the field is to be focussed on, so I had hoped that putting :-
var focusField = myField.id; setTimeout("document.getElementById(focusField).focus()", 1);
would work - but Firefox say focusField is undefined.
I'm trying to get a popup to keep focus when it is re-clicked. The script below is supposed to produce this exact behaviour, however it doesn't work, at least on firefox 1.0.7 and moz 1.7.12 (linux kubuntu). It does work with konqueror....
When setting the tabIndex property for an element, Firefox also displays, like IE, a dotted rectangle around the focussed element. With IE you can set hideFocus=true, which does not work with Firefox.
I have a frame set (as per MS FrontPage 2000). It has a contents and a main frame. The contents frame has a menu bar written with with javascript (in the context of a table). In IE6.1 everything works fine as it also does in firefox if I call the contents frame directly (i.e. outside of its frameset). However, if I call my main page (index.html) which invokes the frame set, the contents frame javascript menubar onmouseover function doesn't seem to work though if I reload the contents frame directly it then does. Code:
I know there are some issues trying to use .focus() and .select() within another.eventhandler (for the same object) in firefox. What I don't know is, howto workaround?
I'm trying to create a control which when the mouse button gets pressed on one div an absolute positioned div pops up in place of the cursor. From there the cursor should interact with the dialog before the mouse button is released. In other words one element will catch onmousedown, display the popup, and the popup element will catch onmouseup. This works fine in IE as the popup automatically accepts following events, but my problem is in Firefox.
In Firefox everything behind the popup still receive events even though they can't be seen (hidden by the popup). I have to release the mouse button and then click on the popup again before it accepts the onmouseup event.
I also used a different cursor on the popup to see if Firefox recognized it was there at all. Still the cursor doesn't change until I release themouse button and move the cursor across the popup element.
I've tried focus/blur, timeout delays, hiding the first element (the one which receives onmousedown) but nothing works.
The only thing that works is hiding the entire body and then using setTimeout to show the entire body again 1ms later. Obviously though that is very ugly.
I'm currently making a web application which needs to be fully compatible with iPad. The functions I've implemented so far work perfectly on Firefox, Internet Explorer and other browsers. However, the iPad itself responds a bit different. After a certain action, I want to put focus on a textfield with the help of Javascript. Again, this works perfectly with the normal browser, the iPad browser however seems to be blocking the focus. The reason I'm not posting any code is because it's basically irrelevant. All I do is:
Is there a reason why setting focus to a textbox input, also gives focus to a submit button on the page, to where if you click enter in the text box, the submit button will be clicked.
The default behaviour of focus() method is displaying the cursor at start of the char(In FF focusOffset is 0(zero) and anchorOffset is 0(zero)). I need to display the focus at end of char after calling focus() method.
I think the problem is cause by my lack of understanding of how the browser (firefox 3.6.3) handles focus.A simplified version of my problem is:I've defined the function
function two_focus() { document.getElementById("two").blur();
Is there a way to set the focus on a form field without using focus()? I use ajax to build the form and if I try to set the focus using focus() an error is generate because of the form hasn't been built by ajax. So, it would be nice if I could set the focus() as I built the form.
Is there any way to tell the difference between when this anchor is focused by a user (perhaps by tabbing to it) as opposed to when I programatically do it via anchor_node.focus()?
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"/> <title></title> <script type="text/javascript"> function TextScroll(scrollname, div_name, up_name, down_name, top_name){ [Code]...
When I use mouse wheel in Firefox to scroll contents of the DIV, memory usage in Firefox goes through the roof. Code above is a fully working page, if anyone would like to see what's up, just load it up, and start moving your mouse wheel in the area with text. You don't actually have to scroll the text, just moving the wheel back and forth in that DIV will do. Memory usage will start going up quite fast, and after you stop moving the wheel, it will finally come down a bit after a short while. I've highlighted in red the line where mousewheel event is registered for Firefox. I'm not sure if it's really a problem, but since Opera and IE don't have any strange memory usage, and Firefox does, maybe I did something wrong. In everyday use it shouldn't matter [don't expect to have kilometers of content to scroll], but anyway, it is a bit unsettling.
if ((window)&&(window.netscape)&&(window.netscape.security)) { // OK, this is Gecko/Firefox or someone mimicing it so well // that there is no way to catch it on the act. }
But I need Firefox *1.5 or higher* or another (but sure) way to know that this browser has native SVG support. Here I'm stock.
It seems there is window.navigator.productSub and on my Firefox 1.5 it's 20051111
But I'm not sure: this "build version" is going up guaranteed or it's random like CLASSID? Also is the same Firefox release has the same build for all platforms or not? mozilla.org seems silent.
When I validate a form on submission I use the javascript focus function to scroll the page to the location of the form error e.g.
document.[Form Name].[Field Name].focus();
If you happened to have the page scrolled above where the error field is then the page will scroll so that the error field is at the very top of the window. If you happened to have the page scrolled below where the error field is then the page will scroll so that the error field is at the very bottom of the window. Neither of these is very desirable. Any way to get the error field to the middle of the window?
e.g. in javascript after the focus statement, can one test the location of the error field and then either add half a windows worth of pixels to it if it is at the top of the screen or subtract half a windows worth of pixels to it if it is at the bottom of the screen?
If in the textarea (textarea3), the value is not "abc", and the user uses "Tab" to go to the next textarea (textarea4), it will alert an error message...and the focus will return to the textarea (textarea3) again...
It works in Internet Explorer, however in firefox it does not work? Anyway have any ideas why & how? Code:
If I use the following construct in the frame "main" for a link to an extern site:
<A HREF="http://www.any.xy" TARGET="extern">
the Browser is creating the window "extern", loading the page www.any.xy an setting the focus to "extern". But when I go return to "main" without closing "extern", a click to an other link (e.g. www.2nd_any.xy) on "main" does not setting the focus to "extern".
For setting the focus to "extern" in the second case, I have used the following construct:
<A HREF="http://www.any.xy" TARGET="extern" onClick="setTimeout('extern=window.open('','extern');fr emd.focus();',500);"> an example</A>
This construct has worked very well for a few years, but since about one year, the sesult was the same as using <A HREF="http://www.any.xy" TARGET="extern">
In this year, I have changed: win 95 --> win 2000 modem 56k --> DSL Netscape 4.5 --> Netscape 7.1
Can anybody tell me a possibility setting the focus to "extern" in the second case? Is the changing of my configuration the reason, that the construct has failed?
Neglecting the annoyance factor for a moment, is it possible to keep one browser window at the screen forefront (in front of all other browser windows) but still be able to interact with a window directly beneath it? How would this be pulled off in JS?
I encountered some strange behaviour when using focus()
I use a form with several input-fields. A user can enter stuff. After entering I want to check the value, i.e. that a number is only a number etc. I therefore started editing a Javascript. For test purposes it only popup a message and sets the focus. In fact this is what I want to do, but the scipt isn't it doing right.
I'm trying to do default focus on checkbox,its work fine but the problem is that the user cannot know where is the focus (there isn't visual sign and on the other hand if you press on the tab button there is a visual sign).