Oh crap. Just realized saving index won’t work if context node’s previous
siblings are passed as arguments. Looks like inserting transient node is still
the best way.
> On Jan 18, 2015, at 11:40 AM, Glen Huang wrote:
>
> To generalize the use case, when you have a bunch of nodes, some of which
To generalize the use case, when you have a bunch of nodes, some of which need
to be inserted before a node, and some of which after it, you are likely to
want `replaceWith` could accept the context node as an argument.
I just realized another algorithm: Before running the macro, save the contex
I'd be interested in hearing more about what didn't work with that API by
both devs who tried to make use of it and the implementors too.
For the record: web developers don't usually take advantage of additional
functionality that is provided by only one browser, or implemented in
differing unpoli
I just said it in the other thread, but just to clarify in this thread
too: I think non-contiguous selections are a great feature. I think
exposing them to authors as multiple Ranges in a Selection has proven
to be not a good way to do it, because authors basically without
exception just ignore an
On Mon, Jan 12, 2015 at 9:59 PM, Ben Peters wrote:
> Multiple selection is an important feature in the future. Table columns are
> important, but we also need to think about BIDI. Depending on who you talk
> to, BIDI should support selection in document order or layout order. Layout
> order is not
On Jan 16, 2015, at 4:07 PM, Dimitri Glazkov wrote:
> On Fri, Jan 16, 2015 at 1:14 PM, Ryosuke Niwa wrote:
>
>> On Jan 15, 2015, at 7:25 PM, Dimitri Glazkov wrote:
>> On Thu, Jan 15, 2015 at 6:43 PM, Ryosuke Niwa wrote:
>> When an author imports a ES6 module, we don't create a fake object whic
