- From: guest271314 <notifications@github.com>
- Date: Sat, 16 May 2020 06:43:08 -0700
- To: heycam/webidl <webidl@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Saturday, 16 May 2020 13:43:20 UTC
@TimothyGu > That being said, the API design looks pretty odd. In particular, forcing users to modify the `ssml` and `text` attributes separately could contribute to a temporary state of inconsistency between `ssml` and `text`, which IMO would be poor design. (E.g., `text` has been set to SSML text while `ssml` is still false.) This is what we have. From the specification > This may be either plain text or a complete, well-formed SSML document. No language discloses how to disambiguate between the two potential inputs. > In response to this, I'd propose making `ssml` settable through the constructor but immutable otherwise. In fact, if I were to design the API, I'd make all of these properties (`text`, `volume`, etc.) readonly; but if that's no longer possible, making `ssml` immutable and only settable through the constructor is the next best thing. How does that look in "Web IDL" verbage? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/heycam/webidl/issues/880#issuecomment-629647812
Received on Saturday, 16 May 2020 13:43:20 UTC