| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
This conforms to what Pango does and to the CSS4 spec. And it makes the
parsing code easier. So let's go for it.
|
| |
|
|
|
|
|
|
| |
This is just lots of renaming.
The interface remains private, so the public API does not change, apart
from removing the definition of the Interface object to avoid
subclassing.
|
| |
|
|
|
|
|
|
| |
As Benjamin says, ident should only be used if any value
is valid, which is not the case here. So use enums instead,
which should also be more efficient. To handle the more
complicated cases like font-variant-ligatures, we have to
introduce flags-like values.
|
| |
|
|
|
|
|
|
|
| |
Drop the current css2-style font-variant property and
replace it with a shorthand as specified in the css3 fonts
module. Currently, we fully support the font-variant-ligatures,
font-variant-position, font-variant-caps, font-variant-numeric
and font-variant-east-asian subproperties. font-variant-alternatives
is only partially supported.
|
| |
|
|
| |
-gtk-icon-filter replaces this now.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
CSS supports blend modes, in which a series of layers are
merged together according to the given operation or set of
operations.
Support for blend modes landed on Cairo, which exposes all
the commons and also the exquisites blend modes available.
Adding support for blend modes, then, is just a matter of
using the available Cairo operations.
This patch adds the background-blend-mode CSS enum property,
and adapts the background rendering code to blend the backgrounds
using the available blend modes when they're set.
https://bugzilla.gnome.org/show_bug.cgi?id=768305
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes a couple bugs...
- Pixel font sizes in css would render as point sizes.
- For em font sizes, where the parent size was set and not default, we would
incorrectly convert a pixel value from points to pixels.
We'll always grab the default font size in pixels so we don't keep confusing
things.
Worth noting that gtk css font-size will still behave differently than the
web. Pango interprets font-size differently.
|
| | |
|
| |
|
|
| |
This is a property for icons, so we should name it as such.
|
| |
|
|
|
| |
The support is limited to underline single, double and wavy, which
is what pango has today.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The font-stretch CSS property is defined in the Level 3 CSS Fonts
module, available at:
http://dev.w3.org/csswg/css-fonts/#propdef-font-stretch
It allows defining a normal, condensed, or expanded face to the font
description. Pango already supports it, so this is literally just the
CSS parser machinery needed to bridge our CSS to the FontDescription
API.
https://bugzilla.gnome.org/show_bug.cgi?id=735593
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The values can be:
"requested" - the style as requested
"regular" - use a regular full-color icon
"symbolic" - use a symbolic icon
The property defaults to "requested", so no changes should be seen
unless CSS overrides it.
It is also inherited, so that using this CSS
.toolbar { -gtk-icon-style: symbolic; }
is enough to force the whole toolbar to use symbolic icons.
|
| |
|
|
|
|
|
| |
This will allow us to use the CSS machinery to apply a highlight or dim
effect when images are prelit or insensitive.
https://bugzilla.gnome.org/show_bug.cgi?id=705443
|
| |
|
|
|
| |
As the last CSS property, font-size now is a proper number (when it's
not a keyword).
|
| |
|
|
|
|
|
|
| |
We now support the keywords (like xx-small, medium, larger, smaller...)
and I've changed the default value to be "medium".
This required some shuffling of the "get default font size" code. But
all is well now.
|
| | |
|
| |
|
|
|
|
|
| |
... and get rid of its GType.
This makes it non-queryable using gtk_style_context_get() but it used to
be a private struct anyway.
|
| |
|
|
| |
And fix the parser to conform to the CSS spec while at it.
|
|
|
... and add them via gtkcssenumvalue.[ch] which will be used for all
enums.
|
