There are two use cases for Localizable, however. Consider, one might want to have:

dictionary MyThing extends Localizable {
   DOMString message;
   unsigned long someNumber;
}

Which, in JS would be:

const thing = {
   someNumber : 5,
   message: "hello",
   lang: "en",
}

Having the value member predefined denies the MyObject from having a better named dictionary member message.

As opposed to:

dictionary MyThing {
   Localizable message;
}

Which results in the somewhat more verbose:

const thing = {
   someNumber : 5
   message: { value: "hello", lang: "en" },
   lang: "en",
}

So, it's nice to have the generic Localizable to utilize when there is a generic value member, but it's also nicer to the flatter structured resulting form extending Localizable. The tradeoff being clarity to what dir, lang apply to, which is unambiguous in the case of the current Localizable.

An alternative I guess is:

typedef (Localizable or DOMString) BidiText;

dictionary MyThing {
    BidiText message;
}

Which provides flexibility to use either.

Localizable structure #26

Description

No activity

Activity

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

`Localizable` structure #26