- From: Marcos Cáceres via GitHub <sysbot+gh@w3.org>
- Date: Thu, 08 Apr 2021 01:34:45 +0000
- To: public-geolocation@w3.org
@aphillips, I fundamentally agree with the logic and rationale - and I too have done work localizing DOM exceptions, so know exactly where you are coming from. However, **at this moment**, we are treating Geolocation as a "revised recommendation" to get it to retroactively match what is currently shipping in browsers and not adding new spec features. We hope to add enhancements in future versions, once we get this spec to become a "living standard" under the Process 2020. I think at that point, we should add: > "User agents SHOULD localize the `.message` attribute to match the document's language.". Or something similar. But adding that now would be deceptive, as no user agent localizes the error message and there is **currently** no plan from any implementer to localize these error messages. Thus, I'd prefer we work with implementers to get them to commit to localizing error messages, rather than put aspirational conformance requirements that we know are just going to be ignored. This is why, in the note, I explicitly call out the terrible situation at the moment: > To make matters worse, the text of these error messages is not localized. So, yes, we will come back to this... and we should probably do this in WebIDL too, as that's the source of most DOM Exceptions. But we will opt not to do it now. -- GitHub Notification of comment by marcoscaceres Please view or discuss this issue at https://github.com/w3c/geolocation-api/issues/50#issuecomment-815382346 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 8 April 2021 01:34:47 UTC