Ronald Treur
Ronald Treur
First things first: this is a **breaking change**! ## What is this about? It is about making sure the polyfill also works nicely with the CSS Multi-column Layout Module (Level...
This fixes the issue in my tests. Instead of some, we now test all elements for the presence of break-before/break-always properties (though not all children, but I guess that is...
### What goes wrong If there is an element with a CSS property `break-before` or `break-after` that also contains children, whose content ends up being split by the `extractOverflowingContent`-method, the...
### What goes wrong Having an element with a CSS property `break-before` set to `region`, `always` or `all` breaks the polyfill in most cases. What happens is that `extractOverflowingContent` will...
*Note:* **This was only tested on Chrome v86** ## Some background After adding content into a region, the polyfill's `extractOverflowingContent` method is being invoked if the content overflows the region....
So today I reinstalled grunt-protractor-webdriver and I immediately ran into a very weird problem: Grunt is being shut down prematurely. I'm not 100% sure as to what causes this, but...
By making sure the common path ends with a path separator, we know we end up with an actual valid base path.
Passing along files: `src/styles/main` `src/styles/modules` yields the following (incorrect) basePath: `/absolute/path/src/styles/m` Suffice to say this is not correct and breaks the execution right away on `fs.statSync(options.basePath)`
Using Grunt's _expand_ option in my config, results in the generated files ending up in the wrong place. Take this example: ``` files: [{ expand: true, cwd: 'src/www/', src: [...