Rob Wu

@paulguz I have added another commit to #70, assuming that you're loading additional localization files using `loadLocale`. If that does not solve your issue, could you share a minimal project...

Try stepping through with a debugger to see what goes wrong. I suggest to put a breakpoint at the start of `gMacros.plural`.

@Phyks I guess that it's just not implemented due to the lack of need / time. @fabi1cazenave can give a more authorative answer to why that line of code is...

I don't see any immediate issues with allowing plurals for non-textContent properties. If @fabi1cazenave has no objections, I would accept a PR.

I think that you'd better shoot him a mail if you want feedback from @fabi1cazenave .

Patches are welcome. The proper fix is not to unconditionally call `getPluralRules`, but call `getPluralRules` again in `setLanguage` if the language changed.

@gazal-k I'd not take such a PR because it would hurt performance in large applications. FWIW, there are some implementation flaws in your snippet: - In the first snippet, infinite...

> The profiling results seemed to indicate that MutationObservers are pretty fast. Using documents of which complexity? What is "pretty fast"? My experience with permanent MOs and looking for elements...

You don't have to duplicate the IDs in `locales.ini` (which does not even have to be called `locales.ini`, by the way. You can also use `locale.properties`, `foo.bar`, etc, as long...

> `{{ _('Welcome to our homepage') }}` > `Welcome to our homepage` What if later you change this to `"Welcome to our home page"`? Then you'd have to change the...