All CSS parsers must implement this basic interface: it allows applications to register handlers for different types of events and to initiate a parse from a URI, or a character stream.
All CSS parsers must also implement a zero-argument constructor (though other constructors are also allowed).
CSS parsers are reusable but not re-entrant: the application may reuse a parser object (possibly with a different input source) once the first parse has completed successfully, but it may not invoke the parse() methods recursively within a parse.
$
- Revision: 477010 $Philippe
- Le HegaretMethod from org.w3c.css.sac.Parser Summary: |
---|
getParserVersion, parsePriority, parsePropertyValue, parseRule, parseSelectors, parseStyleDeclaration, parseStyleSheet, parseStyleSheet, setConditionFactory, setDocumentHandler, setErrorHandler, setLocale, setSelectorFactory |
Method from org.w3c.css.sac.Parser Detail: |
---|
|
|
|
|
|
|
The application can use this method to instruct the CSS parser to begin parsing an CSS document from any valid input source (a character stream, a byte stream, or a URI). Applications may not invoke this method while a parse is in progress (they should create a new Parser instead for each additional CSS document). Once a parse is complete, an application may reuse the same Parser object, possibly with a different input source. |
This method is a shortcut for the common case of reading a document from a URI. It is the exact equivalent of the following: parse(new InputSource(uri)); The URI must be fully resolved by the application before it is passed to the parser. |
|
If the application does not register a document handler, all document events reported by the CSS parser will be silently ignored (this is the default behaviour implemented by HandlerBase). Applications may register a new or different handler in the middle of a parse, and the CSS parser must begin using the new handler immediately. |
If the application does not register an error event handler, all error events reported by the CSS parser will be silently ignored, except for fatalError, which will throw a CSSException (this is the default behaviour implemented by HandlerBase). Applications may register a new or different handler in the middle of a parse, and the CSS parser must begin using the new handler immediately. |
CSS parsers are not required to provide localisation for errors and warnings; if they cannot support the requested locale, however, they must throw a CSS exception. Applications may not request a locale change in the middle of a parse. |
|