Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

multiple natural language text fields share language/direction [I18N] #1376

Closed
w3cbot opened this issue Apr 5, 2021 · 5 comments
Closed

multiple natural language text fields share language/direction [I18N] #1376

w3cbot opened this issue Apr 5, 2021 · 5 comments
Labels
close? The related issue was closed by the Group but open here needs-resolution i18n expects this item to be resolved to their satisfaction. s:appmanifest https://w3c.github.io/manifest/ t:lang_negotiation 10.1 Providing for content negotiation based on language wg:webapps https://www.w3.org/groups/wg/webapps

Comments

@w3cbot
Copy link

w3cbot commented Apr 5, 2021 •
edited by xfq
Loading

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

§ w3c/manifest#968
@w3cbot w3cbot added pending Issue not yet sent to WG, or raised by tracker tool & needing labels. s:appmanifest https://w3c.github.io/manifest/ tracker i18n is following a discussion, but doesn't require resolution. labels Apr 5, 2021
@xfq xfq removed the pending Issue not yet sent to WG, or raised by tracker tool & needing labels. label Apr 6, 2021
@r12a
Copy link
Contributor

r12a commented Apr 6, 2021

@xfq should the label for this and the issue raised not be needs-resolution ?

@xfq
Copy link
Member

xfq commented Apr 6, 2021 •
edited
Loading

I think this should be needs-resolution, but the i18n WG has not reviewed the Web Application Manifest spec (we only reviewed Publication Manifest and MiniApp Manifest), so this is currently only an issue I personally raised, and that's why I added the tracker label.

@xfq xfq added needs-resolution i18n expects this item to be resolved to their satisfaction. and removed tracker i18n is following a discussion, but doesn't require resolution. labels Nov 19, 2021
@w3cbot w3cbot added the close? The related issue was closed by the Group but open here label May 26, 2022
@r12a r12a added the t:lang_negotiation 10.1 Providing for content negotiation based on language label Jul 15, 2022
@plehegar
Copy link
Member

Also relates to

@aphillips
Copy link
Contributor

This issue probably should be escalated/investigated further. I find that I don't tend to agree with the comment at the end of the thread.

@aphillips aphillips added the needs-review Needs attention but not urgent label Aug 15, 2023
@w3cbot w3cbot added the wg:webapps https://www.w3.org/groups/wg/webapps label Feb 9, 2024
@aphillips aphillips added needs-attention The i18n WG should urgently review the status of this item. and removed needs-review Needs attention but not urgent labels Apr 11, 2024
@aphillips aphillips removed the needs-attention The i18n WG should urgently review the status of this item. label May 23, 2024
@aphillips
Copy link
Contributor

We do not agree with the resolution of their manifest#968 but feel this is now tracked by manifest#1045 (call of 2024-05-23)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
close? The related issue was closed by the Group but open here needs-resolution i18n expects this item to be resolved to their satisfaction. s:appmanifest https://w3c.github.io/manifest/ t:lang_negotiation 10.1 Providing for content negotiation based on language wg:webapps https://www.w3.org/groups/wg/webapps
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@aphillips @plehegar @xfq @r12a @w3cbot