Ingolme

Like I said, you can only load files that are on your same domain. Unless this file is on computerlabs.co.uk it's not going to work.

Use Google, search for MP4 converter.

The XML DOM tutorial teaches you how to open and read XML files with Javascript. Javascript can only read XML files from the current domain, but you can use a PHP proxy to load XML from other domains.

You didn't mention any server-side languages so I figured it was purely a Javascript application. Seeing that you're using databases there are also server-side languages involved.

Browsers don't do that, as far as I know.

Who is the one declining? Are any messages showing up?

I've never heard of any of those frameworks before. They aren't required to develop applications. Judging by the languages you're mentioning, I guess you're intending to make a client-side application.

It's valid XML, there's nothing gramatically wrong with it. How the attributes are interpretted depends on the software that is reading the file.

Because those applications make pages wrong and don't always look right in all browsers. People who make templates for content management systems need to know HTML. HTML is also crucial for search engine optimization. Knowing HTML is the first step in web development, after learning HTML, CSS, Javascript and a server-side language you will be ready to develop applications yourself.

Which part of the tutorials are not explained well enough?

In PHP you can load data from another file using include() but if you want a redirect, you can use a location header: header('Location: http://example.com/');exit; The specifications say URLs in the location header must be absolute and prepended by the http: or https: protocol.If you send a location header, it must be sent before any HTML or printed content.

$services and $pricelist are always set because you've passed them as parameters to the function. I'm sure it's been mentioned earlier already, you should be using isset() directly on $_POST[] array elements.

PHP has had Object-oriented programming since version 4.

The answer was much simpler than using a table, this works: <a href="index.html" class="auto-style1">Appetizers | Nachos | Soups | Seafood | Steak </a><a href="index.html" class="auto-style1">Appetizers | Lunch | Desserts | Kids | Texmex | Tacos </a> Much less mark-up and semantically correct.And some CSS which takes care of the purpose the <strong> tags had:[code[.auto-style1 { font-weight: bold; }[/code]

The <p> tag is what is preventing the links from appearing next to eachother. <p> elements are blocks and therefore force adjacent elements to go above and below them. The <strong> tag should be omitted because you can use CSS on the link itself to make the text bold.

Just remove the <p> and <strong> tags. Use CSS to add style properties to the link.

Just remove the float property and they'll all be stacked vertically.

It's called collapsing margins. vertical margin of an element will be applied to the ancestor. The easiest way to solve it is to add overflow: hidden to the container.

From what I'm reading in the article you showed, ::-webkit-scrollbar-button:decrement:vertical will target the up button, :increment:vertical targets the down button, :decrement:horizontal targets the left button, :increment:horizontal targets the right button. Is there anything specific you want to do? I can interpret the article for you if you need it.

Blocking right-clicking doesn't work. There are so many other ways to grab your content besides right-clicking. Right-click blocking scripts were abandoned by decent web developers a decade ago. function blockRightClick(e) { e = e || window.event; if (e.which && e.which == 3 || e.button && e.button == 2) { if(e.preventDefault) e.preventDefault(); return false; }} Then apply a mousedown or mouseup event on the element: element.onmouseup = blockRightClick;

-webkit is a proprietary prefix and doesn't mean it's part of the standard, which is why W3Schools doesn't have it on their site. It's not that great if it only works on webkit browsers anyways.

Flash was, for a while. These days a combination of HTML 5 and Javascript can do basically everything applets were used for.

It sounds like your professor is not very knowledgable. XHTML is an old standard which is becoming obsolete.

The audio element is valid HTML 5, it isn't valid HTML 4.01, are you sure your page has the HTML 5 doctype?

How an applet works doesn't depend on the browser, just on the Java version that the user has and the operating system that Java is running on. The problem with applets is that they're outdated, and with recent Java security issues a lot of people have Java disabled. Firefox provided an update that automatically disables Java.