Web Development. W3Schools Online Web Tutorials. W3Fools – A W3Schools Intervention. SELFHTML 8.1.2 (HTML-Dateien selbst erstellen) SELFHTML stellt seit 1995 eine deutschsprachige Dokumentation zu HTML und verwandten Technologien zur Verfügung.
Wir möchten dabei besonders … Anfängern die Grundlagen vermitteln und Kurse in deutscher Sprache anbieten Fortgeschrittenen ein Nachschlagewerk bereitstellen Everyone’s a publisher/wiki/SELFHTML#Everyone.E2.80.99s_a_publisher SELFHTML gehört seit vielen Jahren zu den bekanntesten Dokumentationen über das Erstellen von Web-Seiten. Fertige Content Management Systeme, soziale Netzwerke und andere Plattformen bieten dafür ebenfalls Mittel an.
Wollen Sie aber eine individuelle Webseite gestalten, müssen Sie sich mit den grundlegenden Werkzeugen vertraut machen. Für Fragen zum Inhalt und Diskussionen steht das SELFHTML-Forum zur Verfügung. 10.4 Cross-document messaging. Cross-document messaging Web browsers, for security and privacy reasons, prevent documents in different domains from affecting each other; that is, cross-site scripting is disallowed. While this is an important security feature, it prevents pages from different domains from communicating even when those pages are not hostile. This section introduces a messaging system that allows documents to communicate with each other regardless of their source domain, in a way designed to not enable cross-site scripting attacks. 9.4.1 Introduction This section is non-normative.
For example, if document A contains an iframe element that contains document B, and script in document A calls postMessage() on the Window object of document B, then a message event will be fired on that object, marked as originating from the Window of document A. Var o = document.getElementsByTagName('iframe')[0]; o.contentWindow.postMessage('Hello world', ' 9.4.2 Security 9.4.2.1 Authors 9.4.2.2 User agents. 9 Web workers. 10 Web workers 10.1 Introduction 10.1.1 Scope This section is non-normative. This specification defines an API for running scripts in the background independently of any user interface scripts. This allows for long-running scripts that are not interrupted by scripts that respond to clicks or other user interactions, and allows long tasks to be executed without yielding to keep the page responsive. Workers (as these background scripts are called herein) are relatively heavy-weight, and are not intended to be used in large numbers.
Generally, workers are expected to be long-lived, have a high start-up performance cost, and a high per-instance memory cost. 10.1.2 Examples There are a variety of uses that workers can be put to. 10.1.2.1 A background number-crunching worker The simplest use of workers is for performing a computationally expensive task without interrupting the user interface. The main page is as follows: <! The worker itself is as follows: View this example online. Here is the HTML page: HTTP Archive. Web Workers. Abstract This specification defines an API that allows Web application authors to spawn background workers running scripts in parallel to their main page. This allows for thread-like operation with message-passing as the coordination mechanism. Status of This document This section describes the status of this document at the time of its publication.
Other documents may supersede this document. A list of current W3C publications and the most recently formally published revision of this technical report can be found in the W3C technical reports index at If you wish to make comments regarding this document, you can enter feedback using this form: You can also e-mail feedback to public-webapps@w3.org (subscribe, archives), or whatwg@whatwg.org (subscribe, archives). Implementors should be aware that this specification is not stable. E-mail notifications of changes Browsable version-control record of all changes: Table of Contents 1 Introduction 1.1 Scope 1.2 Examples <!
<! <! <! <!