| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
| |
This is probably the last thing we will ship (if ever) since it needs the most
spec and implementation work for arbitrary use that is pretty far into a corner.
|
|
|
|
|
|
|
|
| |
This feature should not be shipped until the various definitions of addition for
each additive property are properly specified and then implemented accordingly.
Unlike other patches in this series, compositing is not frequently used
internally so there is no need to enable this by default for chrome callers.
|
|
|
|
|
|
|
|
|
| |
This preference controls whether authors are allowed to specify animations
without a 0% or 100% keyframe.
We intend to ship this but it isn't implemented yet (needs a follow-up) but this
preference acts as a safeguard in case we discover we need to disable it once
it's implemented.
|
|
|
|
| |
Default false, no intent to ship for web content. Always enabled for Chrome.
|
|
|
|
|
|
|
|
|
|
|
| |
ScrollbarStyles contains values of overflow, (over)scroll-behavior, etc.
The only one which is marginally related to scroll _bars_ is overflow, which can
be used to hide scrollbar (by making an element not scrollable) or enforce the
scrollbar to display.
It makes more sense to be called ScrollStyles as it's mainly concerning behavior
of scrolling, not scrollbars. Also, with the addition of scrollbar width
properties, the current name can be confusing.
|
|
|
|
| |
There were a few typos in the previous patch and this patch also makes tab-size animatable which didn't really require much of a change at all.
|
| |
|
| |
|
|
|
|
|
|
| |
Since these are just interpreted comments, there's 0 impact on actual code.
This removes all lines that match /* vim: set(.*)tw=80: */ with S&R -- there are
a few others scattered around which will be removed manually in a second part.
|
|
|
|
|
| |
This excludes DOMProxy handlers in dom bindings because that's intertwined with
codegen and js that needs to be handled together.
|
|
|
|
| |
Linux filesystems tend to be case sensitive
|
|
|
|
|
|
| |
KeyFrameEffect and KeyFrameEffectReadOnly are still built unified as
buddies because they have some complex interdependency that couldn't
easily be resolved without linking failures.
|
|
|
|
|
|
|
|
|
| |
* Add a node property to access the ::before and ::after pseudo-elements
* Look for the frame for ::before and ::after pseudos
* Clean up pseudo-element props
* Simplify nsLayoutUtils callers, and make child iterators notice display: contents pseudos
Tag #1375
|
| |
|
| |
|
|
|
|
|
|
| |
(added tests + style clean up)
Issue #55
|
|
|
|
|
|
| |
tests)
Issue #55
|
|
|
|
| |
Issue #55
|
|
|
|
| |
Issue #55
|
|
|
|
|
|
| |
Script
Issue #55
|
|
|
|
|
|
| |
on Aurora 52
Issue #55
|
|
|
|
|
|
|
|
|
| |
part 1 (in the description)
Issue #55
part 1 - Add transitioncancel event handler
part 2 - Add ontransitioncancel EventHandler to WebIDL
part 3 - Add member of active time to ComputedTiming
|
|
|