ELinks 0.18.0
css.h File Reference
This graph shows which files directly or indirectly include this file:

Functions

void import_css (struct css_stylesheet *css, struct uri *uri)
 This function will try to import the given url from the cache.
int supports_css_media_type (const char *optstr, const char *token, size_t token_length)
 Check whether ELinks claims to support a specific CSS media type.

Variables

struct css_stylesheet default_stylesheet
struct module css_module

Function Documentation

◆ import_css()

void import_css ( struct css_stylesheet * css,
struct uri * uri )

This function will try to import the given url from the cache.

◆ supports_css_media_type()

int supports_css_media_type ( const char * optstr,
const char * token,
size_t token_length )

Check whether ELinks claims to support a specific CSS media type.

Parameters
optstrNull-terminated value of the document.css.media option.
tokenA name parsed from a CSS file or from an HTML media attribute. Need not be null-terminated.
token_lengthLength of token, in bytes.

Both strings should be in the ASCII charset.

Returns
nonzero if the media type is supported, 0 if not.

Variable Documentation

◆ css_module

struct module css_module
extern

◆ default_stylesheet

struct css_stylesheet default_stylesheet
extern
Todo
TODO: Basicly we need two default stylesheets. One that ELinks controls (which is defined by the defaults of every property, they could however also be loadable at startup time, e.g. when/if we will have a very generalised renderer it would be possible to bypass the HTML renderer but would simply use an HTML stylesheet like the one in CSS2 Appendix A. "A sample style sheet for HTML 4.0") and one that the user controls. They should be remerged when ever the user reloads the user stylesheet but else they should be pretty static. Together they defines the basic layouting should be done when rendering the document.