.TH "Eliom_content.Xml" 3o 2014-07-10 OCamldoc ""
.SH NAME
Eliom_content.Xml \- Low-level XML manipulation.
.SH Module
Module   Eliom_content.Xml
.SH Documentation
.sp
Module
.BI "Xml"
 : 
.B sig  end

.sp
Low\-level XML manipulation\&.
.sp

.sp

.sp
.sp
.I include Xml_sigs.Iterable
.sp

.B Base functions
See \&.
.sp

.sp

.PP

.B === 
.B Unique nodes 
.B  ===

.PP

.PP

.B === Unique nodes are XML nodes that are manipulated \&'by reference\&'
.B       when sent to the client part of an Eliom\-application: the
.B       created element is allocated only one time in each instance of
.B       an application\&. See {% <<a_manual chapter="clientserver\-html"
.B       fragment="unique" |the eliom manual>> %} for more
.B       details\&. ===

.PP

.PP

.B === 
.B Event handlers 
.B  ===

.PP
.I type 
.B -#Dom_html.event
.I caml_event_handler 

.sp
Values of type 
.B \&'a caml_event_handler
represents event handler
build with the 
.B {{ \&.\&.\&. }}
syntax (see the Eliom manual for more
information on )\&. Such values are expected
by functions like 
.B Eliom_service\&.onload
or
.B Eliom_content\&.Html5\&.a_onclick
\&. The type parameter is the
type of the javascript event expected by the handler, for
example  or \&.
.sp

.sp

.I val wrap 
: 
.B elt -> 'a -> 'a Eliom_wrap.wrapped_value
.sp

.B Eliom_content\&.Xml\&.wrap page v
is like 
.B Eliom_wrap\&.wrap v
but
it makes sure that all 
.B elt
s in 
.B v
which are included in
.B page
are sent with empty content\&. This is safe because such
elements will be taken from the DOM on the client either
ways\&.
.sp

.sp