Shaw
Shaw
I have files within a `/vendor/` path containing a lot of git submodules that I want CodeKit ignore overall since there are a lot of extra files in those repositories,...
Snap.svg's `getBBox()` refuses to work on `use` elements. However, if you call `getBBox()` on the element's `node`, it does work, at least in Chrome. Firefox does get the correct values...
Need to think through collapsing whitespace. 99% of the time, whitespace in the DOM _should_ be collapsed/ignored, but perhaps with `whitespace: true`, ` `’s could be treated like characters & preserved...
With `Splitting.html`, it would be fantastic to offer server side rendering support so pre-compiled pages could have elements pre-split so that Splitting wouldn't even need to be delivered to or...
Currently, some advanced effects for Splitting require using psuedo elements with the `data-word` and `data-char` attributes populating them. Unfortunately, screen readers read the psuedo elements populated with `content: attr(data-word)`, effectively...
Along the discussion for #20 and longer term planning for 2.0: - DOM-independent API methods ( `splitText`, `childNodes`, etc. ) - `Splitting.jsx` return method that takes a framework's `createElement` function...
Related to #32: Need to clarify in the documentation the `force: true` option and its purpose.
https://codepen.io/shshaw/pen/PQbQgE Tested in 11.1.2; not sure what the issue is. For reference: here's the CSS that sets up the grid. https://github.com/shshaw/Splitting/blob/master/dist/splitting-cells.css
Noticed on [this pen](https://codepen.io/shshaw/pen/KxpqBo) that the ``s were receiving a `--char-index` when using `whitespace: true`. Definitely something off with that.