SharpKit.Html Namespace

Classes

	Name	Description
	AbstractView	A base interface that all views shall derive from. See also the Document Object Model (DOM) Level 2 Views Specification. @since DOM Level 2
	AbstractWorker
	ApplicationCache
	Attr	The Attr interface represents an attribute in an Element object. Typically the allowable values for the attribute are defined in a document type definition. Attr objects inherit the Node interface, but since they are not actually child nodes of the element they describe, the DOM does not consider them part of the document tree. Thus, the Node attributes parentNode , previousSibling , and nextSibling have a null value for Attr objects. The DOM takes the view that attributes are properties of elements rather than having a separate identity from the elements they are associated with; this should make it more efficient to implement such features as default attributes associated with all elements of a given type. Furthermore, Attr nodes may not be immediate children of a DocumentFragment . However, they can be associated with Element nodes contained within a DocumentFragment . In short, users and implementors of the DOM need to be aware that Attr nodes have some things in common with other objects inheriting the Node interface, but they also are quite distinct. The attribute's effective value is determined as follows: if this attribute has been explicitly assigned any value, that value is the attribute's effective value; otherwise, if there is a declaration for this attribute, and that declaration includes a default value, then that default value is the attribute's effective value; otherwise, the attribute does not exist on this element in the structure model until it has been explicitly added. Note that the nodeValue attribute on the Attr instance can also be used to retrieve the string version of the attribute's value(s). In XML, where the value of an attribute can contain entity references, the child nodes of the Attr node may be either Text or EntityReference nodes (when these are in use; see the description of EntityReference for discussion). Because the DOM Core is not aware of attribute types, it treats all attribute values as simple strings, even if the DTD or schema declares them as having tokenized types. See also the Document Object Model (DOM) Level 2 Core Specification.
	BarProp
	BaseException
	BeforeUnloadEvent
	Blob
	BooleanArray
	ByteArray
	CanvasGradient
	CanvasPattern
	CanvasPixelArray
	CanvasRenderingContext2D
	CaretPosition
	CDATASection	CDATA sections are used to escape blocks of text containing characters that would otherwise be regarded as markup. The only delimiter that is recognized in a CDATA section is the "]]>" string that ends the CDATA section. CDATA sections cannot be nested. Their primary purpose is for including material such as XML fragments, without needing to escape all the delimiters. The DOMString attribute of the Text node holds the text that is contained by the CDATA section. Note that this may contain characters that need to be escaped outside of CDATA sections and that, depending on the character encoding ("charset") chosen for serialization, it may be impossible to write out some characters as part of a CDATA section. The CDATASection interface inherits from the CharacterData interface through the Text interface. Adjacent CDATASection nodes are not merged by use of the normalize method of the Node interface. Because no markup is recognized within a CDATASection , character numeric references cannot be used as an escape mechanism when serializing. Therefore, action needs to be taken when serializing a CDATASection with a character encoding where some of the contained characters cannot be represented. Failure to do so would not produce well-formed XML.One potential solution in the serialization process is to end the CDATA section before the character, output the character using a character reference or entity reference, and open a new CDATA section for any further characters in the text node. Note, however, that some code conversion libraries at the time of writing do not return an error or exception when a character is missing from the encoding, making the task of ensuring that data is not corrupted on serialization more difficult. See also the Document Object Model (DOM) Level 2 Core Specification.
	CharacterData	The CharacterData interface extends Node with a set of attributes and methods for accessing character data in the DOM. For clarity this set is defined here rather than on each object that uses these attributes and methods. No DOM objects correspond directly to CharacterData , though Text and others do inherit the interface from it. All offsets in this interface start from 0 . As explained in the DOMString interface, text strings in the DOM are represented in UTF-16, i.e. as a sequence of 16-bit units. In the following, the term 16-bit units is used whenever necessary to indicate that indexing on CharacterData is done in 16-bit units. See also the Document Object Model (DOM) Level 2 Core Specification.
	CharacterDataEditVAL
	ClientRect
	ClientRectList
	CloseEvent
	Comment	This interface inherits from CharacterData and represents the content of a comment, i.e., all the characters between the starting ' <!-- ' and ending ' --> '. Note that this is the definition of a comment in XML, and, in practice, HTML, although some HTML tools may implement the full SGML comment structure. See also the Document Object Model (DOM) Level 2 Core Specification.
	CompositionEvent
	Coordinates
	Counter	The Counter interface is used to represent any counter or counters function value. This interface reflects the values in the underlying style property. See also the Document Object Model (DOM) Level 2 Style Specification. @since DOM Level 2
	CSS2Properties	The CSS2Properties interface represents a convenience mechanism for retrieving and setting properties within a CSSStyleDeclaration . The attributes of this interface correspond to all the properties specified in CSS2. Getting an attribute of this interface is equivalent to calling the getPropertyValue method of the CSSStyleDeclaration interface. Setting an attribute of this interface is equivalent to calling the setProperty method of the CSSStyleDeclaration interface. A conformant implementation of the CSS module is not required to implement the CSS2Properties interface. If an implementation does implement this interface, the expectation is that language-specific methods can be used to cast from an instance of the CSSStyleDeclaration interface to the CSS2Properties interface. If an implementation does implement this interface, it is expected to understand the specific syntax of the shorthand properties, and apply their semantics; when the margin property is set, for example, the marginTop , marginRight , marginBottom and marginLeft properties are actually being set by the underlying implementation. When dealing with CSS "shorthand" properties, the shorthand properties should be decomposed into their component longhand properties as appropriate, and when querying for their value, the form returned should be the shortest form exactly equivalent to the declarations made in the ruleset. However, if there is no shorthand declaration that could be added to the ruleset without changing in any way the rules already declared in the ruleset (i.e., by adding longhand rules that were previously not declared in the ruleset), then the empty string should be returned for the shorthand property. For example, querying for the font property should not return "normal normal normal 14pt/normal Arial, sans-serif", when "14pt Arial, sans-serif" suffices. (The normals are initial values, and are implied by use of the longhand property.) If the values for all the longhand properties that compose a particular string are the initial values, then a string consisting of all the initial values should be returned (e.g. a border-width value of "medium" should be returned as such, not as ""). For some shorthand properties that take missing values from other sides, such as the margin , padding , and border-[width\|style\|color] properties, the minimum number of sides possible should be used; i.e., "0px 10px" will be returned instead of "0px 10px 0px 10px". If the value of a shorthand property can not be decomposed into its component longhand properties, as is the case for the font property with a value of "menu", querying for the values of the component longhand properties should return the empty string. See also the Document Object Model (DOM) Level 2 Style Specification. @since DOM Level 2
	CSSCharsetRule	The CSSCharsetRule interface represents a @charset rule in a CSS style sheet. The value of the encoding attribute does not affect the encoding of text data in the DOM objects; this encoding is always UTF-16. After a stylesheet is loaded, the value of the encoding attribute is the value found in the @charset rule. If there was no @charset in the original document, then no CSSCharsetRule is created. The value of the encoding attribute may also be used as a hint for the encoding used on serialization of the style sheet. The value of the @charset rule (and therefore of the CSSCharsetRule ) may not correspond to the encoding the document actually came in; character encoding information e.g. in an HTTP header, has priority (see CSS document representation) but this is not reflected in the CSSCharsetRule . See also the Document Object Model (DOM) Level 2 Style Specification. @since DOM Level 2
	CSSColorComponentValue
	CSSComponentValue
	CSSFontFaceRule	The CSSFontFaceRule interface represents a @font-face rule in a CSS style sheet. The @font-face rule is used to hold a set of font descriptions. See also the Document Object Model (DOM) Level 2 Style Specification. @since DOM Level 2
	CSSImportRule	The CSSImportRule interface represents a @import rule within a CSS style sheet. The @import rule is used to import style rules from other style sheets. See also the Document Object Model (DOM) Level 2 Style Specification. @since DOM Level 2
	CSSLengthComponentValue
	CSSMediaRule	The CSSMediaRule interface represents a @media rule in a CSS style sheet. A @media rule can be used to delimit style rules for specific media types. See also the Document Object Model (DOM) Level 2 Style Specification. @since DOM Level 2
	CSSNamespaceRule
	CSSPageRule	The CSSPageRule interface represents a @page rule within a CSS style sheet. The @page rule is used to specify the dimensions, orientation, margins, etc. of a page box for paged media. See also the Document Object Model (DOM) Level 2 Style Specification. @since DOM Level 2
	CSSPercentageComponentValue
	CSSPrimitiveValue	The CSSPrimitiveValue interface represents a single CSS value . This interface may be used to determine the value of a specific style property currently set in a block or to set a specific style property explicitly within the block. An instance of this interface might be obtained from the getPropertyCSSValue method of the CSSStyleDeclaration interface. A CSSPrimitiveValue object only occurs in a context of a CSS property. Conversions are allowed between absolute values (from millimeters to centimeters, from degrees to radians, and so on) but not between relative values. (For example, a pixel value cannot be converted to a centimeter value.) Percentage values can't be converted since they are relative to the parent value (or another property value). There is one exception for color percentage values: since a color percentage value is relative to the range 0-255, a color percentage value can be converted to a number; (see also the RGBColor interface). See also the Document Object Model (DOM) Level 2 Style Specification. @since DOM Level 2
	CSSRule	The CSSRule interface is the abstract base interface for any type of CSS statement. This includes both rule sets and at-rules. An implementation is expected to preserve all rules specified in a CSS style sheet, even if the rule is not recognized by the parser. Unrecognized rules are represented using the CSSUnknownRule interface. See also the Document Object Model (DOM) Level 2 Style Specification. @since DOM Level 2
	CSSStyleDeclaration	The CSSStyleDeclaration interface represents a single CSS declaration block. This interface may be used to determine the style properties currently set in a block or to set style properties explicitly within the block. While an implementation may not recognize all CSS properties within a CSS declaration block, it is expected to provide access to all specified properties in the style sheet through the CSSStyleDeclaration interface. Furthermore, implementations that support a specific level of CSS should correctly handle CSS shorthand properties for that level. For a further discussion of shorthand properties, see the CSS2Properties interface. This interface is also used to provide a read-only access to the computed values of an element. See also the ViewCSS interface. The CSS Object Model doesn't provide an access to the specified or actual values of the CSS cascade. See also the Document Object Model (DOM) Level 2 Style Specification. @since DOM Level 2
	CSSStyleDeclarationValue
	CSSStyleRule	The CSSStyleRule interface represents a single rule set in a CSS style sheet. See also the Document Object Model (DOM) Level 2 Style Specification. @since DOM Level 2
	CSSStyleSheet	The CSSStyleSheet interface is a concrete interface used to represent a CSS style sheet i.e., a style sheet whose content type is "text/css". See also the Document Object Model (DOM) Level 2 Style Specification. @since DOM Level 2
	CSSUnknownRule	The CSSUnknownRule interface represents an at-rule not supported by this user agent. See also the Document Object Model (DOM) Level 2 Style Specification. @since DOM Level 2
	CSSURLComponentValue
	CSSValue	The CSSValue interface represents a simple or a complex value. A CSSValue object only occurs in a context of a CSS property. See also the Document Object Model (DOM) Level 2 Style Specification. @since DOM Level 2
	CSSValueList	The CSSValueList interface provides the abstraction of an ordered collection of CSS values. Some properties allow an empty list into their syntax. In that case, these properties take the none identifier. So, an empty list means that the property has the value none . The items in the CSSValueList are accessible via an integral index, starting from 0. See also the Document Object Model (DOM) Level 2 Style Specification. @since DOM Level 2
	CustomEvent
	Database
	DatabaseSync
	DataTransfer
	Document	The Document interface represents the entire HTML or XML document. Conceptually, it is the root of the document tree, and provides the primary access to the document's data. Since elements, text nodes, comments, processing instructions, etc. cannot exist outside the context of a Document , the Document interface also contains the factory methods needed to create these objects. The Node objects created have a ownerDocument attribute which associates them with the Document within whose context they were created. See also the Document Object Model (DOM) Level 2 Core Specification.
	DocumentCSS	This interface represents a document with a CSS view. The getOverrideStyle method provides a mechanism through which a DOM author could effect immediate change to the style of an element without modifying the explicitly linked style sheets of a document or the inline style of elements in the style sheets. This style sheet comes after the author style sheet in the cascade algorithm and is called override style sheet. The override style sheet takes precedence over author style sheets. An "!important" declaration still takes precedence over a normal declaration. Override, author, and user style sheets all may contain "!important" declarations. User "!important" rules take precedence over both override and author "!important" rules, and override "!important" rules take precedence over author "!important" rules. The expectation is that an instance of the DocumentCSS interface can be obtained by using binding-specific casting methods on an instance of the Document interface. See also the Document Object Model (DOM) Level 2 Style Specification. @since DOM Level 2
	DocumentEditVAL
	DocumentEvent	The DocumentEvent interface provides a mechanism by which the user can create an Event of a type supported by the implementation. It is expected that the DocumentEvent interface will be implemented on the same object which implements the Document interface in an implementation which supports the Event model. See also the Document Object Model (DOM) Level 2 Events Specification. @since DOM Level 2
	DocumentFragment	DocumentFragment is a "lightweight" or "minimal" Document object. It is very common to want to be able to extract a portion of a document's tree or to create a new fragment of a document. Imagine implementing a user command like cut or rearranging a document by moving fragments around. It is desirable to have an object which can hold such fragments and it is quite natural to use a Node for this purpose. While it is true that a Document object could fulfill this role, a Document object can potentially be a heavyweight object, depending on the underlying implementation. What is really needed for this is a very lightweight object. DocumentFragment is such an object. Furthermore, various operations -- such as inserting nodes as children of another Node -- may take DocumentFragment objects as arguments; this results in all the child nodes of the DocumentFragment being moved to the child list of this node. The children of a DocumentFragment node are zero or more nodes representing the tops of any sub-trees defining the structure of the document. DocumentFragment nodes do not need to be well-formed XML documents (although they do need to follow the rules imposed upon well-formed XML parsed entities, which can have multiple top nodes). For example, a DocumentFragment might have only one child and that child node could be a Text node. Such a structure model represents neither an HTML document nor a well-formed XML document. When a DocumentFragment is inserted into a Document (or indeed any other Node that may take children) the children of the DocumentFragment and not the DocumentFragment itself are inserted into the Node . This makes the DocumentFragment very useful when the user wishes to create nodes that are siblings; the DocumentFragment acts as the parent of these nodes so that the user can use the standard methods from the Node interface, such as insertBefore and appendChild . See also the Document Object Model (DOM) Level 2 Core Specification.
	DocumentRange	See also the Document Object Model (DOM) Level 2 Traversal and Range Specification. @since DOM Level 2
	DocumentTraversal	DocumentTraversal contains methods that create iterators and tree-walkers to traverse a node and its children in document order (depth first, pre-order traversal, which is equivalent to the order in which the start tags occur in the text representation of the document). In DOMs which support the Traversal feature, DocumentTraversal will be implemented by the same objects that implement the Document interface. See also the Document Object Model (DOM) Level 2 Traversal and Range Specification. @since DOM Level 2
	DocumentType	Each Document has a doctype attribute whose value is either null or a DocumentType object. The DocumentType interface in the DOM Core provides an interface to the list of entities that are defined for the document, and little else because the effect of namespaces and the various XML schema efforts on DTD representation are not clearly understood as of this writing. The DOM Level 2 doesn't support editing DocumentType nodes. See also the Document Object Model (DOM) Level 2 Core Specification.
	DocumentView	The DocumentView interface is implemented by Document objects in DOM implementations supporting DOM Views. It provides an attribute to retrieve the default view of a document. See also the Document Object Model (DOM) Level 2 Views Specification. @since DOM Level 2
	DOMConfiguration
	DOMError
	DOMErrorHandler
	DOMEvent
	DOMException	DOM operations only raise exceptions in "exceptional" circumstances, i.e., when an operation is impossible to perform (either for logical reasons, because data is lost, or because the implementation has become unstable). In general, DOM methods return specific error values in ordinary processing situations, such as out-of-bound errors when using NodeList . Implementations should raise other exceptions under other circumstances. For example, implementations should raise an implementation-dependent exception if a null argument is passed. Some languages and object systems do not support the concept of exceptions. For such systems, error conditions may be indicated using native error reporting mechanisms. For some bindings, for example, methods may return error codes similar to those listed in the corresponding method descriptions. See also the Document Object Model (DOM) Level 2 Core Specification.
	DOMImplementation	The DOMImplementation interface provides a number of methods for performing operations that are independent of any particular instance of the document object model. See also the Document Object Model (DOM) Level 2 Core Specification.
	DOMImplementationCSS	This interface allows the DOM user to create a CSSStyleSheet outside the context of a document. There is no way to associate the new CSSStyleSheet with a document in DOM Level 2. See also the Document Object Model (DOM) Level 2 Style Specification. @since DOM Level 2
	DOMImplementationList
	DOMImplementationLS
	DOMImplementationSource
	DOMLocator
	DOMSettableTokenList
	DOMStringList
	DOMStringMap
	DOMTokenList
	DoubleArray
	DragEvent
	Element	The Element interface represents an element in an HTML or XML document. Elements may have attributes associated with them; since the Element interface inherits from Node , the generic Node interface attribute attributes may be used to retrieve the set of all attributes for an element. There are methods on the Element interface to retrieve either an Attr object by name or an attribute value by name. In XML, where an attribute value may contain entity references, an Attr object should be retrieved to examine the possibly fairly complex sub-tree representing the attribute value. On the other hand, in HTML, where all attributes have simple string values, methods to directly access an attribute value can safely be used as a convenience.In DOM Level 2, the method normalize is inherited from the Node interface where it was moved. See also the Document Object Model (DOM) Level 2 Core Specification.
	ElementCSSInlineStyle	Inline style information attached to elements is exposed through the style attribute. This represents the contents of the STYLE attribute for HTML elements (or elements in other schemas or DTDs which use the STYLE attribute in the same way). The expectation is that an instance of the ElementCSSInlineStyle interface can be obtained by using binding-specific casting methods on an instance of the Element interface when the element supports inline CSS style informations. See also the Document Object Model (DOM) Level 2 Style Specification. @since DOM Level 2
	ElementEditVAL
	ElementTimeControl	SMILAnimation supports several methods for controlling the behavior of animation: beginElement() and endElement() , et al. These methods are used to begin and end an animation that has declared the timing to respond to the DOM, using the following syntax: <animate begin="indefinite" end="indefinite" .../> Note that only one of begin or end need be specified - either or both can be used. The beginElement() and beginElementAt() methods must do nothing if the animation is not explicitly set with the begin="indefinite" syntax above. The endElement() and endElementAt() methods must do nothing if the animation is not explicitly set with the end ="indefinite" syntax above. Calling beginElement() causes the animation to begin in much the same way that an animation with event-based begin timing begins. The effective begin time is the current presentation time at the time of the DOM method call. Note that beginElement() is subject to the restart attribute in the same manner that event-based begin timing is. If an animation is specified to disallow restarting at a given point, beginElement() methods calls must fail. Refer also to the section Restarting animations. Calling beginElementAt() has the same effect as beginElement() , except that the effective begin time is offset from the current presentation time by an amount specified as a parameter. Passing a negative value for the offset causes the element to begin as for beginElement() , but has the effect that the element begins at the specified offset into its active duration. The beginElementAt() method must also respect the restart attribute. The restart semantics for a beginElementAt() method call are evaluated at the time of the method call, and not at the effective begin time specified by the offset parameter. Calling endElement() causes an animation to end the active duration, just as end does. Depending upon the value of the fill attribute, the animation effect may no longer be applied, or it may be frozen at the current effect. Refer also to the section Freezing animations. If an animation is not currently active (i.e. if it has not yet begun or if it is frozen), the endElement() method will fail. Calling endElementAt() causes an animation to end the active duration, just as endElement() does, but allows the caller to specify a positive offset, to cause the element to end at a point in the future. Other than delaying when the end actually happens, the semantics are identical to those for endElement() . If endElementAt() is called more than once while an element is active, the end time specified by the last method call will determine the end behavior. The expectation of the following interface is that an instance of the ElementTimeControl interface can be obtained by using binding-specific casting methods on an instance of an animate element. A DOM application can use the hasFeature method of the DOMImplementation interface to determine whether the ElementTimeControl interface is supported or not. The feature string for this interface is "TimeControl" .
	ElementTraversal
	Entity	This interface represents an entity, either parsed or unparsed, in an XML document. Note that this models the entity itself not the entity declaration. Entity declaration modeling has been left for a later Level of the DOM specification. The nodeName attribute that is inherited from Node contains the name of the entity. An XML processor may choose to completely expand entities before the structure model is passed to the DOM; in this case there will be no EntityReference nodes in the document tree. XML does not mandate that a non-validating XML processor read and process entity declarations made in the external subset or declared in external parameter entities. This means that parsed entities declared in the external subset need not be expanded by some classes of applications, and that the replacement value of the entity may not be available. When the replacement value is available, the corresponding Entity node's child list represents the structure of that replacement text. Otherwise, the child list is empty. The DOM Level 2 does not support editing Entity nodes; if a user wants to make changes to the contents of an Entity , every related EntityReference node has to be replaced in the structure model by a clone of the Entity 's contents, and then the desired changes must be made to each of those clones instead. Entity nodes and all their descendants are readonly. An Entity node does not have any parent.If the entity contains an unbound namespace prefix, the namespaceURI of the corresponding node in the Entity node subtree is null . The same is true for EntityReference nodes that refer to this entity, when they are created using the createEntityReference method of the Document interface. The DOM Level 2 does not support any mechanism to resolve namespace prefixes. See also the Document Object Model (DOM) Level 2 Core Specification.
	EntityReference	EntityReference objects may be inserted into the structure model when an entity reference is in the source document, or when the user wishes to insert an entity reference. Note that character references and references to predefined entities are considered to be expanded by the HTML or XML processor so that characters are represented by their Unicode equivalent rather than by an entity reference. Moreover, the XML processor may completely expand references to entities while building the structure model, instead of providing EntityReference objects. If it does provide such objects, then for a given EntityReference node, it may be that there is no Entity node representing the referenced entity. If such an Entity exists, then the subtree of the EntityReference node is in general a copy of the Entity node subtree. However, this may not be true when an entity contains an unbound namespace prefix. In such a case, because the namespace prefix resolution depends on where the entity reference is, the descendants of the EntityReference node may be bound to different namespace URIs. As for Entity nodes, EntityReference nodes and all their descendants are readonly. See also the Document Object Model (DOM) Level 2 Core Specification.
	ErrorEvent
	EventException	Event operations may throw an EventException as specified in their method descriptions. See also the Document Object Model (DOM) Level 2 Events Specification. @since DOM Level 2
	EventSource
	EventTarget	The EventTarget interface is implemented by all Nodes in an implementation which supports the DOM Event Model. Therefore, this interface can be obtained by using binding-specific casting methods on an instance of the Node interface. The interface allows registration and removal of EventListeners on an EventTarget and dispatch of events to that EventTarget . See also the Document Object Model (DOM) Level 2 Events Specification. @since DOM Level 2
	ExceptionVAL
	File
	FileError
	FileException
	FileReader
	FileReaderSync
	FloatArray
	FocusEvent
	FormData
	Geolocation
	GetSVGDocument
	HashChangeEvent
	History
	HtmlAllCollection
	HtmlAnchorElement
	HtmlAppletElement
	HtmlAreaElement
	HtmlAudioElement
	HtmlBaseElement
	HtmlBaseFontElement
	HtmlBodyElement
	HtmlBRElement
	HtmlButtonElement
	HtmlCanvasElement
	HtmlCollection
	HtmlCommandElement
	HtmlContext
	HtmlContextBase
	HtmlDataListElement
	HtmlDetailsElement
	HtmlDirectoryElement
	HtmlDivElement
	HtmlDListElement
	HtmlDocument
	HtmlElement
	HtmlEmbedElement
	HtmlFieldSetElement
	HtmlFontElement
	HtmlFormControlsCollection
	HtmlFormElement
	HtmlFrameElement
	HtmlFrameSetElement
	HtmlHeadElement
	HtmlHeadingElement
	HtmlHRElement
	HtmlHtmlElement
	HtmlIFrameElement
	HtmlImageElement
	HtmlInputElement
	HtmlKeygenElement
	HtmlLabelElement
	HtmlLegendElement
	HtmlLIElement
	HtmlLinkElement
	HtmlMapElement
	HtmlMarqueeElement
	HtmlMediaElement
	HtmlMenuElement
	HtmlMetaElement
	HtmlMeterElement
	HtmlModElement
	HtmlObjectElement
	HtmlOListElement
	HtmlOptGroupElement
	HtmlOptionElement
	HtmlOptionsCollection
	HtmlOutputElement
	HtmlParagraphElement
	HtmlParamElement
	HtmlPreElement
	HtmlProgressElement
	HtmlPropertiesCollection
	HtmlQuoteElement
	HtmlScriptElement
	HtmlSelectElement
	HtmlSourceElement
	HtmlSpanElement
	HtmlStyleElement
	HtmlTableCaptionElement
	HtmlTableCellElement
	HtmlTableColElement
	HtmlTableDataCellElement
	HtmlTableElement
	HtmlTableHeaderCellElement
	HtmlTableRowElement
	HtmlTableSectionElement
	HtmlTextAreaElement
	HtmlTimeElement
	HtmlTitleElement
	HtmlUListElement
	HtmlUnknownElement
	HtmlVideoElement
	IDBCursor
	IDBCursorRequest
	IDBCursorSync
	IDBDatabase
	IDBDatabaseError
	IDBDatabaseException
	IDBDatabaseRequest
	IDBDatabaseSync
	IDBEnvironment
	IDBEnvironmentSync
	IDBIndex
	IDBIndexRequest
	IDBIndexSync
	IDBKeyRange
	IDBObjectStore
	IDBObjectStoreRequest
	IDBObjectStoreSync
	IDBRequest
	IDBTransaction
	IDBTransactionRequest
	IDBTransactionSync
	ImageData
	IndexedDatabase
	IndexedDatabaseRequest
	KeyboardEvent
	LinkStyle	The LinkStyle interface provides a mechanism by which a style sheet can be retrieved from the node responsible for linking it into a document. An instance of the LinkStyle interface can be obtained using binding-specific casting methods on an instance of a linking node ( HTMLLinkElement , HTMLStyleElement or ProcessingInstruction in DOM Level 2). See also the Document Object Model (DOM) Level 2 Style Specification. @since DOM Level 2
	Location
	LongArray
	LongLongArray
	LSException
	LSInput
	LSLoadEvent
	LSOutput
	LSParser
	LSParserFilter
	LSProgressEvent
	LSResourceResolver
	LSSerializer
	LSSerializerFilter
	MediaError
	MediaList	The MediaList interface provides the abstraction of an ordered collection of media, without defining or constraining how this collection is implemented. An empty list is the same as a list that contains the medium "all" . The items in the MediaList are accessible via an integral index, starting from 0. See also the Document Object Model (DOM) Level 2 Style Specification. @since DOM Level 2
	MessageChannel
	MessageEvent
	MessagePort
	MouseEvent	The MouseEvent interface provides specific contextual information associated with Mouse events. The detail attribute inherited from UIEvent indicates the number of times a mouse button has been pressed and released over the same screen location during a user action. The attribute value is 1 when the user begins this action and increments by 1 for each full sequence of pressing and releasing. If the user moves the mouse between the mousedown and mouseup the value will be set to 0, indicating that no click is occurring. In the case of nested elements mouse events are always targeted at the most deeply nested element. Ancestors of the targeted element may use bubbling to obtain notification of mouse events which occur within its descendent elements. See also the Document Object Model (DOM) Level 2 Events Specification. @since DOM Level 2
	MutationEvent	The MutationEvent interface provides specific contextual information associated with Mutation events. See also the Document Object Model (DOM) Level 2 Events Specification. @since DOM Level 2
	MutationNameEvent
	NamedNodeMap	Objects implementing the NamedNodeMap interface are used to represent collections of nodes that can be accessed by name. Note that NamedNodeMap does not inherit from NodeList ; NamedNodeMaps are not maintained in any particular order. Objects contained in an object implementing NamedNodeMap may also be accessed by an ordinal index, but this is simply to allow convenient enumeration of the contents of a NamedNodeMap , and does not imply that the DOM specifies an order to these Nodes. NamedNodeMap objects in the DOM are live. See also the Document Object Model (DOM) Level 2 Core Specification.
	NameList
	Navigator
	NavigatorGeolocation
	Node	The Node interface is the primary datatype for the entire Document Object Model. It represents a single node in the document tree. While all objects implementing the Node interface expose methods for dealing with children, not all objects implementing the Node interface may have children. For example, Text nodes may not have children, and adding children to such nodes results in a DOMException being raised. The attributes nodeName , nodeValue and attributes are included as a mechanism to get at node information without casting down to the specific derived interface. In cases where there is no obvious mapping of these attributes for a specific nodeType (e.g., nodeValue for an Element or attributes for a Comment ), this returns null . Note that the specialized interfaces may contain additional and more convenient mechanisms to get and set the relevant information. See also the Document Object Model (DOM) Level 2 Core Specification.
	NodeEditVAL
	NodeFilter	Filters are objects that know how to "filter out" nodes. If a NodeIterator or TreeWalker is given a NodeFilter , it applies the filter before it returns the next node. If the filter says to accept the node, the traversal logic returns it; otherwise, traversal looks for the next node and pretends that the node that was rejected was not there. The DOM does not provide any filters. NodeFilter is just an interface that users can implement to provide their own filters. NodeFilters do not need to know how to traverse from node to node, nor do they need to know anything about the data structure that is being traversed. This makes it very easy to write filters, since the only thing they have to know how to do is evaluate a single node. One filter may be used with a number of different kinds of traversals, encouraging code reuse. See also the Document Object Model (DOM) Level 2 Traversal and Range Specification. @since DOM Level 2
	NodeIterator	Iterators are used to step through a set of nodes, e.g. the set of nodes in a NodeList , the document subtree governed by a particular Node , the results of a query, or any other set of nodes. The set of nodes to be iterated is determined by the implementation of the NodeIterator . DOM Level 2 specifies a single NodeIterator implementation for document-order traversal of a document subtree. Instances of these iterators are created by calling DocumentTraversal .createNodeIterator() . See also the Document Object Model (DOM) Level 2 Traversal and Range Specification. @since DOM Level 2
	NodeList	The NodeList interface provides the abstraction of an ordered collection of nodes, without defining or constraining how this collection is implemented. NodeList objects in the DOM are live. The items in the NodeList are accessible via an integral index, starting from 0. See also the Document Object Model (DOM) Level 2 Core Specification.
	Notation	This interface represents a notation declared in the DTD. A notation either declares, by name, the format of an unparsed entity (see section 4.7 of the XML 1.0 specification ), or is used for formal declaration of processing instruction targets (see section 2.6 of the XML 1.0 specification ). The nodeName attribute inherited from Node is set to the declared name of the notation. The DOM Level 1 does not support editing Notation nodes; they are therefore readonly. A Notation node does not have any parent. See also the Document Object Model (DOM) Level 2 Core Specification.
	Notification
	NotificationCenter
	OctetArray
	PageTransitionEvent
	PopStateEvent
	Position
	PositionError
	PositionOptions
	ProcessingInstruction	The ProcessingInstruction interface represents a "processing instruction", used in XML as a way to keep processor-specific information in the text of the document. See also the Document Object Model (DOM) Level 2 Core Specification.
	ProgressEvent
	PropertyNodeList
	RadioNodeList
	Range	See also the Document Object Model (DOM) Level 2 Traversal and Range Specification. @since DOM Level 2
	RangeException	Range operations may throw a RangeException as specified in their method descriptions. See also the Document Object Model (DOM) Level 2 Traversal and Range Specification. @since DOM Level 2
	Rect	The Rect interface is used to represent any rect value. This interface reflects the values in the underlying style property. Hence, modifications made to the CSSPrimitiveValue objects modify the style property. See also the Document Object Model (DOM) Level 2 Style Specification. @since DOM Level 2
	RGBColor	The RGBColor interface is used to represent any RGB color value. This interface reflects the values in the underlying style property. Hence, modifications made to the CSSPrimitiveValue objects modify the style property. A specified RGB color is not clipped (even if the number is outside the range 0-255 or 0%-100%). A computed RGB color is clipped depending on the device. Even if a style sheet can only contain an integer for a color value, the internal storage of this integer is a float, and this can be used as a float in the specified or the computed style. A color percentage value can always be converted to a number and vice versa. See also the Document Object Model (DOM) Level 2 Style Specification. @since DOM Level 2
	Screen
	Selection
	SharedWorker
	ShortArray
	SQLError
	SQLException
	SQLResultSet
	SQLResultSetRowList
	SQLTransaction
	SQLTransactionSync
	Storage
	StorageEvent
	StyleMedia
	StyleSheet	The StyleSheet interface is the abstract base interface for any type of style sheet. It represents a single style sheet associated with a structured document. In HTML, the StyleSheet interface represents either an external style sheet, included via the HTML LINK element, or an inline STYLE element. In XML, this interface represents an external style sheet, included via a style sheet processing instruction. See also the Document Object Model (DOM) Level 2 Style Specification. @since DOM Level 2
	SVGAElement
	SVGAltGlyphDefElement
	SVGAltGlyphElement
	SVGAltGlyphItemElement
	SVGAngle
	SVGAnimateColorElement
	SVGAnimatedAngle
	SVGAnimatedBoolean
	SVGAnimatedEnumeration
	SVGAnimatedInteger
	SVGAnimatedLength
	SVGAnimatedLengthList
	SVGAnimatedNumber
	SVGAnimatedNumberList
	SVGAnimatedPathData
	SVGAnimatedPoints
	SVGAnimatedPreserveAspectRatio
	SVGAnimatedRect
	SVGAnimatedString
	SVGAnimatedTransformList
	SVGAnimateElement
	SVGAnimateMotionElement
	SVGAnimateTransformElement
	SVGAnimationElement
	SVGCircleElement
	SVGClipPathElement
	SVGColor
	SVGColorProfileElement
	SVGColorProfileRule
	SVGComponentTransferFunctionElement
	SVGCSSRule
	SVGCursorElement
	SVGDefinitionSrcElement
	SVGDefsElement
	SVGDescElement
	SVGDocument
	SVGElement
	SVGElementInstance
	SVGElementInstanceList
	SVGEllipseElement
	SVGEvent
	SVGException
	SVGExternalResourcesRequired
	SVGFEBlendElement
	SVGFEColorMatrixElement
	SVGFEComponentTransferElement
	SVGFECompositeElement
	SVGFEConvolveMatrixElement
	SVGFEDiffuseLightingElement
	SVGFEDisplacementMapElement
	SVGFEDistantLightElement
	SVGFEFloodElement
	SVGFEFuncAElement
	SVGFEFuncBElement
	SVGFEFuncGElement
	SVGFEFuncRElement
	SVGFEGaussianBlurElement
	SVGFEImageElement
	SVGFEMergeElement
	SVGFEMergeNodeElement
	SVGFEMorphologyElement
	SVGFEOffsetElement
	SVGFEPointLightElement
	SVGFESpecularLightingElement
	SVGFESpotLightElement
	SVGFETileElement
	SVGFETurbulenceElement
	SVGFilterElement
	SVGFilterPrimitiveStandardAttributes
	SVGFitToViewBox
	SVGFontElement
	SVGFontFaceElement
	SVGFontFaceFormatElement
	SVGFontFaceNameElement
	SVGFontFaceSrcElement
	SVGFontFaceUriElement
	SVGForeignObjectElement
	SVGGElement
	SVGGlyphElement
	SVGGlyphRefElement
	SVGGradientElement
	SVGHKernElement
	SVGICCColor
	SVGImageElement
	SVGLangSpace
	SVGLength
	SVGLengthList
	SVGLinearGradientElement
	SVGLineElement
	SVGLocatable
	SVGMarkerElement
	SVGMaskElement
	SVGMatrix
	SVGMetadataElement
	SVGMissingGlyphElement
	SVGMPathElement
	SVGNumber
	SVGNumberList
	SVGPaint
	SVGPathElement
	SVGPathSeg
	SVGPathSegArcAbs
	SVGPathSegArcRel
	SVGPathSegClosePath
	SVGPathSegCurvetoCubicAbs
	SVGPathSegCurvetoCubicRel
	SVGPathSegCurvetoCubicSmoothAbs
	SVGPathSegCurvetoCubicSmoothRel
	SVGPathSegCurvetoQuadraticAbs
	SVGPathSegCurvetoQuadraticRel
	SVGPathSegCurvetoQuadraticSmoothAbs
	SVGPathSegCurvetoQuadraticSmoothRel
	SVGPathSegLinetoAbs
	SVGPathSegLinetoHorizontalAbs
	SVGPathSegLinetoHorizontalRel
	SVGPathSegLinetoRel
	SVGPathSegLinetoVerticalAbs
	SVGPathSegLinetoVerticalRel
	SVGPathSegList
	SVGPathSegMovetoAbs
	SVGPathSegMovetoRel
	SVGPatternElement
	SVGPoint
	SVGPointList
	SVGPolygonElement
	SVGPolylineElement
	SVGPreserveAspectRatio
	SVGRadialGradientElement
	SVGRect
	SVGRectElement
	SVGRenderingIntent
	SVGScriptElement
	SVGSetElement
	SVGStopElement
	SVGStringList
	SVGStylable
	SVGStyleElement
	SVGSVGElement
	SVGSwitchElement
	SVGSymbolElement
	SVGTests
	SVGTextContentElement
	SVGTextElement
	SVGTextPathElement
	SVGTextPositioningElement
	SVGTitleElement
	SVGTransform
	SVGTransformable
	SVGTransformList
	SVGTRefElement
	SVGTSpanElement
	SVGUnitTypes
	SVGURIReference
	SVGUseElement
	SVGViewElement
	SVGViewSpec
	SVGVKernElement
	SVGZoomAndPan
	SVGZoomEvent
	Text	The Text interface inherits from CharacterData and represents the textual content (termed character data in XML) of an Element or Attr . If there is no markup inside an element's content, the text is contained in a single object implementing the Text interface that is the only child of the element. If there is markup, it is parsed into the information items (elements, comments, etc.) and Text nodes that form the list of children of the element. When a document is first made available via the DOM, there is only one Text node for each block of text. Users may create adjacent Text nodes that represent the contents of a given element without any intervening markup, but should be aware that there is no way to represent the separations between these nodes in XML or HTML, so they will not (in general) persist between DOM editing sessions. The normalize() method on Node merges any such adjacent Text objects into a single node for each block of text. See also the Document Object Model (DOM) Level 2 Core Specification.
	TextEvent
	TextMetrics
	TimeEvent	The TimeEvent interface provides specific contextual information associated with Time events.
	TimeRanges
	TreeWalker	TreeWalker objects are used to navigate a document tree or subtree using the view of the document defined by their whatToShow flags and filter (if any). Any function which performs navigation using a TreeWalker will automatically support any view defined by a TreeWalker . Omitting nodes from the logical view of a subtree can result in a structure that is substantially different from the same subtree in the complete, unfiltered document. Nodes that are siblings in the TreeWalker view may be children of different, widely separated nodes in the original view. For instance, consider a NodeFilter that skips all nodes except for Text nodes and the root node of a document. In the logical view that results, all text nodes will be siblings and appear as direct children of the root node, no matter how deeply nested the structure of the original document. See also the Document Object Model (DOM) Level 2 Traversal and Range Specification. @since DOM Level 2
	TypeInfo
	UIEvent	The UIEvent interface provides specific contextual information associated with User Interface events. See also the Document Object Model (DOM) Level 2 Events Specification. @since DOM Level 2
	UndoManager
	UndoManagerEvent
	UnsignedByteArray
	UnsignedLongArray
	UnsignedLongLongArray
	UnsignedShortArray
	UserDataHandler
	ValidityState
	ViewCSS	This interface represents a CSS view. The getComputedStyle method provides a read only access to the computed values of an element. The expectation is that an instance of the ViewCSS interface can be obtained by using binding-specific casting methods on an instance of the AbstractView interface. Since a computed style is related to an Element node, if this element is removed from the document, the associated CSSStyleDeclaration and CSSValue related to this declaration are no longer valid. See also the Document Object Model (DOM) Level 2 Style Specification. @since DOM Level 2
	WebGLActiveInfo
	WebGLArray
	WebGLArrayBuffer
	WebGLBuffer
	WebGLByteArray
	WebGLContextAttributes
	WebGLContextLostEvent
	WebGLFloatArray
	WebGLFramebuffer
	WebGLIntArray
	WebGLObject
	WebGLObjectArray
	WebGLProgram
	WebGLRenderbuffer
	WebGLRenderingContext
	WebGLShader
	WebGLShortArray
	WebGLTexture
	WebGLUniformLocation
	WebGLUnsignedByteArray
	WebGLUnsignedIntArray
	WebGLUnsignedShortArray
	WebSocket
	WheelEvent
	Window
	Worker
	WorkerGlobalScope
	WorkerLocation
	WorkerNavigator
	XMLHttpRequest
	XMLHttpRequestEventTarget
	XMLHttpRequestUpload
	XPathEvaluator
	XPathException
	XPathExpression
	XPathNamespace
	XPathNSResolver
	XPathResult

SharpKit.Html Namespace

Classes

Delegates

Interfaces