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.
In PS you press CTRL+T on new layer. 9 handles appears an then you can stretch/rotate/move that layer. Looking just for that stretch & rotate functionality with dotted/dashed retangle outline. That is, there should be 8 handles on rectangle boundarys and then rectangle should be rotated & stretched via those points. & moved via nineth center point.
I have an application that draws a selection rectangle over a map image. I can get it to work fine in IE and Opera, but not Firefox/Netscape.
I've thrown the following small example together to illustrate the problem - the problem being that FF/NE initially draw my rectangle before the icon changes immediately to the black no-entry icon. Then, when I let go of the mouse, the rectangle continues drawing, but it doesn't stop as the mouseup has already fired of course.
IE was doing the same, but I found the ondragstart/cancelDragDrop solution to that. I can't find what appears to be a similar solution for FF/NE.....
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....
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 am retrieving titles from a database and then displaying them on screen. However when I display them I must make sure that they fit inside a certain rectangle. If it deosn't fit then i must reduce the font size and recalculate until it fits. The title is in two parts Code:
In slideshow running on xp_pro/ie8, after the last slide is displayed, a small white rectangle (approx w:60px h:20px) at the top left positionwhere the1st slide is about to re-appear. The 1st slide then displays correctly, as doall the slides, but I can't keep the rectangle from showing up.
I want to create a rectangle with a line in the middle with the canvas object. The problem is that the line in the middle gets bigger than the rest of the rectangle. How do I solve this? I believe it has something to do with shadows. If so, how do I turn them off.
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()?
I have a webpage with a form. Depending on user selections at the top of the page, the page will disable sections of the form. My plan is to put each section between a <div></div>. Each section contains some collection of form elements.
So if the user does not select some criteria, the related section of the form gets disabled. In a typical Windows type of application these elements get disabled and greyed out. What's the best way to do this in a webpage? Can Javascript determine what form elements are in a div section and disable these elements through a loop for example? I know I can disable each element if I know its it but is there a way to find out all the IDs of elements for some div section?
I am using the following code for disabling Ctrl-N in IE7. It disables the Ctrl-N feature of IE which opens a new window containing the same page as the 'active' window. The code works great (at first glance). However, I noticed that, if you click anywhere inside the browser window and THEN press Ctrl-N, the new window will open. If you don't click anywhere inside the window, the following code works. Can anyone see an improvement to the following code so that clicking inside the browser window doesn't bypass the javascript?