are you sure you've saved your files in utf-8 charset format since you are so eager in instructing the interpreter what chaset is to be used when parsing your content?
and found that Firefox 15.01 will play the ogg, but not the mp3. IE8 won't play anything. Chrome (Version 22.0.1229.92 m) will play both.
That's ironic because the following will play in any Internet Explorer, say version 0 through IE10 if you like.
Without even having to make use the <bgsound> element, I will demonstrate here the posibility of playing audio files without plug-ins using plain <img> tag; to (among other multimedia files) also play a separate audio file (mp3 in this demo). The supported formats are limited only by the number/variety of formats your current OS can play independently.
activate : syncAttr(lineTop.style, "backgroundColor", menu.children);
function syncAttr(t, a, x){
function cS(x){return getComputedStyle(x,0)||x.currentStyle};
var L = x[0] ? x : [x], i = 0, z,tm;
while(L[i]){
L[i].onmouseout = function(){t[a]="";clearInterval(tm)};
L[i++].onmouseover= attSync;}
function attSync(){z=this;
tm=setInterval(function(){
if(/rgba|tran/.test(cS(z)[a])){ t[a]=cS(z)[a];
}else{ t[a]=cS(z)[a]; clearInterval(tm) }},8)}
}
but even this can stand a trial for further optimizations.
***
The following JavaScript function can do your thing, - if you agree to remove css transitions...
activate : syncAttr(lineTop.style, "backgroundColor", menu.children);
function syncAttr(t, a, x){
function cS(x){return getComputedStyle(x,0) || x.currentStyle};
var L = x[0] ? x : [x], i = 0;
while(L[i]){
L[i].onmouseover= attSync;
L[i].onmouseout = function(){t[a]=""};
i++;}
function attSync(){t[a] = cS(this)[a]}
}
The code is assuming that: <div class="linha"></div> has an id=lineTop. That is <div id=lineTop class=linha></div>.
But as mentioned; Will not work with css transitions enabled.
This is not impossible to do with CSS if the elements are next to each other. It's not recommended to rely on that though in case elements get moved around but here is how it's done just as an FYI:
True, but you should warn about browser compatibility; -not all versions support pseudo-classes on ordinary elements;
Hmm... Not sure what that mean... :( Too vauge... Anyway, the example I made is just to show a very simple wayt to change background color using mouse event of each element. May not be a solution. :)
The sentence: "trying to change an element background color when my mouse goes over another element." would usually mean: I need to change the background of element B, when element A is hovered :p
My Spartan (universal property toggle) happens to be the right tool for the job since it is not bound to the event source element, therefore its action can arbitrarilly target any element on the document, on an iframe, on a popup window; including itself. ;)
I totally agree, but I was trying to make a point that: - it is always a better choice to eliminate mistakes instead of fixing them with aditional code. Say, correct the textbox "... value=null>" which is wrong, with a proper type ... value=""> instead.
...the default value of a textbox should always correspond to, at least the type of an expected value -which in this case, is a string(""); Strings can contain numerals also, but not objects. And null is exactly that, -a* Typeless Emty Object*, but nonetheless an object; of which parseFloat is not very found of, since it expects a string containing numbers or at least an object of that type Number. -Anything else will fail on conversion and return a "not a number" Number object.
NaN is a javascript object returned when a value treated as a number fails to convert to number. Basically it is not a number. Whereas the type of NaN it self, is - a number container that has no value. (It's not even a zero).
It's a box of numbers alright - but it's empty. Therefore (another) NaN is never equal to (previous/following) NaN, because it's a different box.
You cannot check if( Number("1.a") == NaN ) That's why isNaN() function was needed.
Though NaN==NaN >> is always false! It's not a Voodoo..., since NaN is an Object;
It's the same as with other empty objects, say: []==[] >> false! They mey be equal in the sense of emptyness and type etc, alas, they are not the same "box". They are different instances of that type of objects.
Contrary to abstractions that can be equal, say 1==1 > true, -since all the 1's of the world are that same 1 (one). That is, the same abstraction. They (NaN's), will be compared by instances, not by values { as in say Number(1)==Number(1) >> true}, because there is a value of the same type that can be compared there. And since they belong to the same abstraction (1) they are the same. >> true!
p.s.: There are a lot of highly "professional coders" that don't understand the half of it. And ask questions like: why is the typeof NaN >> "number" - …
you are comparing a string literal type of data (like: "", " ", "abc", "123") against dynamic data type of a numeral 0, or a Boolean(false) in HEX mode; -Which will always evaluate to false.
if( "" < 0 ) //will aways return false because [""] is greater than [0].
yes it would. check for the >>line<< and >>source<< of the "error code" and go get that string corrected. p.s.: you don't even need the error console to tell you where to look, because its the file and the line of code you or someone else added or modified just before this error ocurred.
Don't worry about var module = instance || {};. It's just defensive programming.
I understand you concern, but module EQ instance OR {}, is a perfect EMT ( error-masking-tool ), it defends your eyes from seeing some otherwise pretty obvious errors. Nothing beneficiary from that.
This line: "var Parousia = {};" is fundamental. So if for some unknown reason it went missing while having thee "defensive programming" line of code in place - there'll be no way to find out why is the whole app - "a sudden fail!?" - because you will be getting some completely unrelated error on some perfectly sound line of code which will confuse you even more or make you loose it completely.
Doing "var module = instance || {};" will not guard anything! In case of a missing global - You will be operating on a totally inaccessible local object instead of your targeted Parousia.
Now back to troubleshooting...
You have, from what I can see there, a property definition such as:
... so, in order to solve possible problems with this I suggest you do some scripting for cross-browser normalization like
var text = document.body.textContent ? "textContent" : "innerText";
// which will enable you to access and modify the text content using:
oElement[text]; >> "this element plain text content"
// or assign
oElement[text] = "this element new plain text"
And of course mark the thread solved. p.s.: (Prototyping it, -is currently a no go.)
Nice.., in case you don't want the whole message, except the "good morning" salutation when time is less than 10, -you can move your script element up again, and of course: mark the thread solved!
Your question was: "... if the time is more than 10.. the page will be directed to a another specific page .... anyone can help on this ?" The answer is
<html>
<body>
<p>This example demonstrates the If statement.</p>
<p>If the time on your browser is less than 10, you will get a "Good morning" greeting.</p>
<p>Otherwise it will navigate you to a different page.</p>
<script type="text/javascript">
var d = new Date();
var time = d.getHours();
if (time > 10 )
{
location.href = "http://www.yourdomain.com/theOtherPage";
}
else
{
document.write( "<b>Good morning</b>" );
}
</script>
</body>
</html>
Script element is moved under the content to prevent overwriting your message.
The only browser that doesn't support the original innerText property and method is firefox. It's not IE's fault that someone else took its feature and called it "my invention" by changing its original name. Never mind that it will cause the web to break! Which in return is its exact aim and the reason of renaming your tools in the first place.
Anyhow: Using the innerHTML as an alternative to innerText was always possible but not always safe. It depends on what you are trying to do. If you are using it as a property or as a method which makes the main difference. Let's exemplify the distinction:
some div content: "div with a [B]bold[/B] element" used as properties of the element will return:
div.innerText >> "div with a bold element"
div.innerHTML >> "div with a <b>bold</b> element"
whereas, using them as methods for the same content "div with a <b>bold</b> element" will give you a:
div.innerText = "div with a <b>bold</b> element"
>> "div with a <b>bold</b> element"
div.innerHTML="div with a <b>bold</b> element"
>> "div with a [b]bold[/b] element"
So it is safe to use, as long as the tool you are using, will do what you are aiming to.
And probably have no idea where did; nor when did xhtml4.0 came out neither?! Mark the thread as solved and stop spamming the forum. IE will forgive an omission or two but will not tolerate the ignorance of an evil man.
So how do you translate this to English than?cite: "I want to know if it is possible (and if so, how) to trigger the click event that displays the enquiry form on the contact page if the page is accessed via the above link?" Anyways, thanks for sharing with the community. In javascript at least, you don't need to call for triggers, you simply do element.click(); and its clicked, which is so much cleaner.
But once again [just for the sake of curiosity ] Trigger click event if page loaded from a certain referring URL how do you translate this question into what you are saying now without some powerful trans-mutational alchemy?
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 4.0 Strict//EN">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<a id='cart' href='/tires/cart'> Your Cart - (empty)</a><head>
<title>Tires - Wholesale</title>
Why is that (red) line of code sitting there. Syntax Error report is absolutely correct 2 line <a> tag in the document head; Did you do this deliberately? Because I'm pretty sure you did...
should not break a thing ever. its an amulet-like syntax that will always guard you from unepected js voodoo.
() [parens] can interact in a great distance and some comment might be fooling you that the line break is an established fact, but it might just so happen that an external script at the end of all lines didn't have a line terminator and might have even been omitted knowing that its the end of the file that will terminate not only the line but the script as a whole. But that's not the case -because external scripts will all be appended as if residing in one single and uninterrupted document. So if another js file begins with (... without a leading ; it will be considered a function call of some end-declaration from the previous file.
3. Why don't you try correcting the:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 4.0 Strict//EN">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
into
<!DOCTYPE html>
<html lang="en">
first, -and see what happens... Anyway, you'll need some patience because this error will not be easy that to locate...;
in jquery-ui.min.js I've noticed an unnecessary line termination in code
...[0].offsetWidth,
height:d[g]...
which depending on the parser - might also cause problems.
http://i44.tinypic.com/dr9vlh.png I cant even see the "show more" anywhere on your supposedly working browser let alone be able to fix it in explorer.
p.s: 1. linked scripts on the header load async., you slideto.js may be loading faster! 2.I suggest you always use ";" in front of self invoking functions, - I mean always. i.e:
;(function($){ $.fn.slideto = function(options) { //and its never ever a bad idea to also finish it with one );
I'm saying this for the first time in public and its a great advice.
3. and lastly -please check if the jQuery file is in the right place. {now that I've checked, none of them are ! They are missing, try moving them on your own domain ajax google apis are either refusing to serve you, or are down or perhaps IE is refusing to load cross-domain scripts. But the same is happening with chrome: Failed to load resource https://ajax.googleapis.com/ajax/libs/jqueryui/1.8.18/jquery-ui.min.js ... }
Nope that's not really true -just came back from your http://stmarytheboltons.org.uk/hall/index.html -and the code is working perfectly, on all browser modes quirks/standard (ie7 ie8 ie9) you name it. Other visitors can confirm this too. p.s.: since you are using .html extension please hold the shift-key while pressing F5 to refresh the page.
you have an image with an ID = "next" on your document collection and you are not declaring it as a variable, meaning you are referencing to an already defined existing image object and trying make it a string on the fly, you cannot nullify that image and reassign a string instead. Secondly, you are using an obsolete doctype for the document. Correcting this will suffice...:i.e: <!DOCTYPE HTML>
now you see how easy it was, you should be more patient when asking people for help giving nothing in return, so even if their given code may prove to be wrong - never go "eeekkk" on them because even then, they've done it with their best intentions and were only trying to help by offering the best they've got. 'Cause you see, you didn't even bother to mark the tread as solved, even though there is no other method for changing the color of the string in place and on the fly, so that others may benefit too.
so what? I never gave you the green code version for you to go "ekkkkk" -how hard can it be to simply replace content from this:
document.write("<br>3+2 = "+answer1+" is incorrect! - "+("The correct answer is 5.").fontcolor('red'));
to this:
document.write("<br>3+2 = "+answer10+(" The answer is correct ").fontcolor('red'));
or removing the parens altogether since they may be confusing instead of helping
document.write("<br>3+2 = "+answer1+" is incorrect! - "+"The correct answer is 5.".fontcolor('red'));
document.write("<br>3+2 = "+answer10+" The answer is correct ".fontcolor('red'));
What do you mean by: form.elements.value = input; (me confused!?!) or, which element exactly?
And you won't need this: "grade = Math.round((grade * 0.2));" unless you are interested to return F on all inputs from 100 down to 0, (at least not with the route taken).
Anyway, you can try this : (it should work if I understood the task correctly; and for a better user experience you might want to split your function in two )
function calcGrade() {
var form = document.getElementById("form");
var finalGrade = document.getElementById("final-grade");
var field = form.elements['test1'];
var input = field.value, grade, max = 100, min = 0;
if(input = parseInt(input, 10)){
field.value =
grade = input > max ? grade = max :
input < min ? grade = min :
input;
finalGrade.value =
(grade < 60) ? "F" :
(grade < 70) ? "D" :
(grade < 80) ? "C" :
(grade < 90) ? "B" :
(grade <100) ? "A" : "!";
}
}
