ISSUE-518: Need to explain name matching rules for cache names

Need to explain name matching rules for cache names

State:

CLOSED

Product:

service-workers

Raised by:

Steven Atkin

Opened on:

2016-02-15

Description:

THREAD: http://www.w3.org/Mail/flatten/index?subject=i18n-ISSUE-518&list=service-workers


5.5.2 has(cacheName), 5.5.3 open(cacheName), and 5.5.4 delete(cacheName)

https://slightlyoff.github.io/ServiceWorker/spec/service_worker_1/#cache-storage-has
https://slightlyoff.github.io/ServiceWorker/spec/service_worker_1/#cache-storage-open
https://slightlyoff.github.io/ServiceWorker/spec/service_worker_1/#cache-storage-delete

In each of these methods there should be an explanation of what are the name matching rules for the cacheName argument. For example, are cache names case sensitive or case insensitive? Additionally, are the names normalized to either Unicode Normal Form NFC or NFD before testing for equality?

Please see Character Model for the World Wide Web: String Matching and Searching https://www.w3.org/TR/charmod-norm/

Specifically, see section 3 https://www.w3.org/TR/charmod-norm/#identityMatching

Related Actions Items:

No related actions

Related emails:

1. Daily github digest (WG INTERNAL review issues) (from sysbot+gh@w3.org on 2019-09-08)
2. Daily github digest (WG INTERNAL review issues) (from sysbot+gh@w3.org on 2019-09-07)
3. i18n-ISSUE-518: Need to explain name matching rules for cache names (from atkin@us.ibm.com on 2016-02-15)
4. I18N-ISSUE-518: Need to explain name matching rules for cache names [service-workers] (from sysbot+tracker@w3.org on 2016-02-15)

Related notes:

Display change log