[w3c/IndexedDB] Add health warning for opaque string comparison (#178)

https://www.w3.org/TR/IndexedDB-2/#object-store-construct

> Object store names are always compared in a case-sensitive manner, as opaque sequences of 16-bit code units.

The object store name comparison is fine, so long as "comparison" means "for identity/equality". Case-sensitivity is _recommended_ by the I18N WG and [Charmod-Norm](http://w3c.github.io/charmod-norm/). However, a health warning may be warranted here, since it is more than just case-sensitive: it is sensitive to the exact encoding sequence. For example, normalization form affects this. Charmod-Norm provides a somewhat exhaustive list of this kind of variation ;-).

A health warning might be:

> Object store names are always compared as opaque sequences of 16-bit code units. As a result, name comparison is sensitive to variations in case as well as other minor variations such as normalization form, the inclusion or omission of controls, and other variations in Unicode text. [[Charmod-Norm]]

This is I18N comment https://github.com/w3c/i18n-activity/issues/363. Please add the i18n-comment label.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/issues/178