Stanisław Małolepszy

I'd prefer to put this on the back burner for now and find a different way to migrate the Firefox string in question to Fluent. I suspect that we'll eventually...

We do. Step 1: Remove the following line: https://github.com/projectfluent/fluent.js/blob/de35e58b9e8499119decbce6415c46599ed81ac0/fluent-dom/src/overlay.js#L197 Step 2: Write _a lot_ of tests. I don't have time for Step 2 right now.

Step 2 is also about understanding the consequences of keeping the identity. For instance, can developers rely on elements passed into translations if translations can remove them? Etc. I'd say...

The same applies to `fluent-react`: https://github.com/projectfluent/fluent.js/blob/5786bf93cf5f51cd6eee0654750238f117cf8a13/fluent-react/src/localization.js#L55-L60

For `n` elements to localize, we're talking `O(2n)` vs. `O(xn)` for `x < 10`. I don't think this is where we should look for performance improvements. (I think it's IO,...

I added it in `Pattern` to make this possible: ```properties open-foo = Open foo .accesskey = O .tooltip = Press {open-foo.accesskey} to open a Foo. ```

#254 has the proposed implementation for this.

Yes, I agree that we should allow this somehow. I also see how this would be useful in `fluent-react`. Even if the exact API will end up being different I...

`data-l10n-attrsonly` would also be useful when defined on elements with `data-l10n-id`: ```xul ``` ```properties window = .title = Window Title ```

We should extend `data-l10n-attrs` to allow protecting attributes.