[i18n-activity] Short_but_informative_title_here (#2034)

aphillips has just created a new issue for https://github.com/w3c/i18n-activity:

== Short_but_informative_title_here ==
## Proposed comment

'message' Attribute
https://www.w3.org/TR/geolocation/#message-attribute

> The message attribute is a developer-friendly textual description of the [code](https://www.w3.org/TR/geolocation/#dom-geolocationpositionerror-code) attribute.
>> Note: Don't show .message to users!
>> The purpose of [GeolocationPositionError](https://www.w3.org/TR/geolocation/#dom-geolocationpositionerror)'s [message](https://www.w3.org/TR/geolocation/#dom-geolocationpositionerror-message) attribute is to assist developers with debugging. For legacy reasons, this attribute does not supply language or base direction metadata and is only localized into English. Developers are advised to use [GeolocationPositionError](https://www.w3.org/TR/geolocation/#dom-geolocationpositionerror)'s [code](https://www.w3.org/TR/geolocation/#dom-geolocationpositionerror-code) attribute to create a localized experience.

@jsahleen asks:

Note that in section 10.3 there is a paragraph stating that the `message` attribute on the `GeolocationPositionError` interface is not localized and only available in English. It specifies the message is not to be used for user-facing communication and developers should implement their own localization based off the `code` attribute. This needs to be clearly spelled out in any developer documentation. Otherwise, it seems likely that the `message` attribute will end up being exposed to users. @aphillips are we ok with the `message` attribute not being localized?




## Instructions: 

This follows the process at https://w3c.github.io/i18n-activity/guidelines/review-instructions.html

1. Create the review comment you want to propose by replacing the prompts above these instructions, but **LEAVE ALL THE INSTRUCTIONS INTACT** 

2. **Add one or more t:... labels. These should use ids from [specdev](https://w3c.github.io/bp-i18n-specdev/) establish a link to that doc.**

2. Set a label to identify the spec: this starts with s: followed by the spec's short name. If you are unable to do that, ask a W3C staff contact to help.

3. Ask the i18n WG to review your comment.

4. After discussion with the i18n WG, raise an issue in the repository of the WG that owns the spec. Use the text above these instructions as the starting point for that comment, but add any suggestions that arose from the i18n WG. In the other WG's repo, add an 'i18n-needs-resolution' label to the new issue. If you think any of the participants in layout requirements task force groups would be interested in following the discussion, add also the appropriate i18n-\*lreq label(s).

5. Delete the text below that says 'url_for_the_issue_raised', then add in its place the URL for the issue you raised in the other WG's repository. Do NOT remove the initial '§ '. Do NOT use \[...](...) notation – you need to delete the placeholder, then paste the URL.

6. Remove the 'pending' label, and add a 'needs-resolution' tag to this tracker issue. 

7. If you added an \*lreq label, add the label 'spec-type-issue', add the corresponding language label, and a label to indicate the relevant typographic feature(s), eg. 'i:line_breaking'. The latter represent categories related to the Language Enablement Index, and all start with i:.

8. Edit this issue to **REMOVE ALL THE INSTRUCTIONS & THE PROPOSED COMMENT**, ie. the line below that is '---' and all the text before it to the very start of the issue.

---


**This is a tracker issue.** Only discuss things here if they are i18n WG internal meta-discussions about the issue. **Contribute to the actual discussion at the following link:**


§ url_for_the_issue_raised


Please view or discuss this issue at https://github.com/w3c/i18n-activity/issues/2034 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 25 September 2025 13:56:29 UTC